![]() |
Template:Transliteration is permanently
protected from editing because it is a
heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by
consensus, editors may use {{
edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's
documentation to add usage notes or
categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
![]() | This template was considered for deletion on 6 September 2013. The result of the discussion was "no consensus". |
![]() | Text and/or other creative content from this version of Template:Transl was copied or moved into incubator:Template:Wp/nod/transl with this edit. The former page's history now serves to provide attribution for that content in the latter page, and it must not be deleted as long as the latter page exists. |
![]() | This template does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||
|
![]() | This page has previously been nominated to be moved.
Discussions:
|
|
|
This page has archives. Sections older than 1000 days may be automatically archived by Lowercase sigmabot III when more than 3 sections are present. |
The result of the move request was: moved. Noting that there is not a consensus to delete the redirect created as a result of the move. That would require an additional discussion at WP:RfD. ( closed by non-admin page mover) Elli ( talk | contribs) 20:47, 14 March 2022 (UTC)
Template:Transl → Template:Transliteration – This template "transliterates" the input text. So, the new title is more proper and complete than simply transl. Also, the part transl is common for both the words translation and transliteration. As such, this template should be moved to Template:Transliteration to provide natural disambiguation against Template:Translation. --- CX Zoom(he/him) ( let's talk| contribs) 19:37, 22 February 2022 (UTC)
there's less need to have good wikicodeI completely disagree with this. Our non-mainspace templates should be as clear as our mainspace templates, for easy use and clarity. If we go down the path of considering mainspace templates being superior, then we would lose many editors that work in non-mainspace. 🐶 EpicPupper (he/him | talk) 21:12, 1 March 2022 (UTC)
subst
or otherwise correct templates, so the
WP:BAG should be able to quickly approve the task if necessary. —
Jkudlick ⚓
(talk) 17:00, 3 March 2022 (UTC)
{{translation}}
produces
transl., which is exactly what the name of this completely different Template is. But I also agree with Asukite that it has 44,000 transclusions (via other redirects or not), so we'd have to change all of them. Yes there are bots but I'm not very sure if we need to do so much here. ---
CX Zoom(he/him) (
let's talk|
contribs) 17:54, 3 March 2022 (UTC)
At this edit, Editor Ineffablebookkeeper added this to the documentation:
{{lang|xx-Latn|...}}
can cause discrepancies in font display when used for transliteration; as such, {{transl|xx|...}}
is preferred for transliterations.@Editor Ineffablebookkeeper: do you have any examples that show that what you wrote is true?
— Trappist the monk ( talk) 13:18, 22 March 2022 (UTC)
{{lang|ja-Latn|Hana}}
{{transl|ja|Hana}}
Might be me being stupid here. The point of the FOREIGNITALIC stuff is to make sure it's not jarring when you're using casual foreign terms, but it seems like the lang templates in certain browsers deliberately sets off the text (which is the only reason I noticed it in the first place)—so the text was weirdly a different typeface and looked bizarre in the plot summary... but it doesn't seem to do it on all the browsers and OS configurations I've tried, so I guess it's a specific setting. So I dunno. I hate it aesthetically because it looks like someone mad-libbed the text, but at the same times that's the point of the templates. I guess disregard. Der Wohltemperierte Fuchs talk 18:11, 29 January 2021 (UTC)
- Aha, don't worry! I think on my other (very dead at the minute) laptop, it does display differently. It's not a problem! It does look like a ransom note cut out of a newspaper at times, lmao. --Ineffablebookkeeper (talk) 21:10, 29 January 2021 (UTC)
<span title="Japanese-language text"><i lang="ja-Latn">Hana</i></span>
← {{lang|ja-Latn|Hana}}
<span title="Japanese-language romanization"><i lang="ja-Latn">Hana</i></span>
← {{transl|ja|Hana}}
<i lang="ja-Latn">Hana</i>
which is the same for both {{
lang}}
and {{
transl}}
.I may be mistaken, but unlike the Lang template, it doesn't look like the Transliteration template adds the category "Articles containing x-language text" to articles using it. Some articles contain only transliterated foreign-language text, not the original script, and won't have the category applied to them. Why are the two templates different in this regard? flod logic ( talk) 08:32, 18 January 2023 (UTC)
{{
transl}}
accepts both language and script tags, it seems to me that this template should not share the categories:
{{
Non-English-language text category}}
does for the language categories.Can the Transliteration template be modified to support Private-use language tags? I have been expanding Wikipedia's coverage of ancient history, and I am finding myself needing for the transliteration template to render Private-use language tags, but it seems that it does not currently do so.
Seeing as the expansion of Wikipedia's ancient history coverage would inevitably make it a necessity, can I request for the Transliteration template to be modified so that it can render Private-use language tags? Antiquistik ( talk) 12:01, 19 January 2023 (UTC)
Hi @ Jonesey95, why did you revert me? [1] “Source text to be transliterated,” foreign-script text like барахло, is never to be entered into this template. Only its corresponding Latin-alphabet target transliteration, like barakhlo. — Michael Z. 02:05, 6 June 2023 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change: Hi. I want to change the Proto-cuneiform listing to point to the main article ie "Proto-cuneiform" from the current "Proto-cuneiform numerals", which is a sub-article. Thanks. Ploversegg ( talk) 02:44, 15 January 2024 (UTC) Diff:
− | + | CHANGED_TEXT |
Ploversegg ( talk) 02:44, 15 January 2024 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change: Lets see if I can do better this time. I would like to request that in "Template:ISO 15924 script codes and related Unicode data" in the line "Pcun" that "Proto-cuneiform numerals" be changed to "Proto-cuneiform" corresponding to the article Proto-cuneiform. Thanks. Ploversegg ( talk) 19:53, 15 January 2024 (UTC)
Diff:
− | + | CHANGED_TEXT |
Ploversegg ( talk) 19:53, 15 January 2024 (UTC)
{{
ISO 15924 script codes and related Unicode data}}
is not part of {{
transliteration}}
per se. It is its own template. It calls {{
ISO 15924 script codes and related Unicode data/row}}
which has this:
[[{{ISO 15924/wp-article|1={{{alpha4|}}}}}|{{ISO 15924 name|1={{{alpha4|}}}}}]]
{{{alpha4|}}}
is the ISO 15924 tag (in this case pcun
). {{
ISO 15924/wp-article}}
defines pcun
as Proto-cuneiform numerals
but {{
ISO 15924 name}}
defines pcun
as Proto-Cuneiform
.{{ISO 15924/wp-article}}
yourself.The inclusion of the equal sign (=) in texts results in an error message instead of the text being displayed. This causes serious issues for the transliteration of languages like Hurrian, Urartian, Ancient Egyptian, and Luwian, whose transliteration requires the use of the equal sign.
For example:
Can this issue be fixed? Antiquistik ( talk) 14:02, 23 March 2024 (UTC)
{{
transl}}
and has been ever thus for all templates that use positional parameters. So, in |pašš-ēt-i=t=ān
, pašš-ēt-i
is interpreted as the parameter name and t=ān
is that parameter's value. Because pašš-ēt-i
is not a parameter name that {{transl}}
recognizes, it is ignored. The no text error message occurs because {{transl}}
did not get a valid second (text) parameter. The commonly used work-around for this is to number the second positional parameter:
{{transl|xhu|2=pašš-ēt-i=t=ān}}
→ pašš-ēt-i=t=ānThe result of the move request was: not moved. Withdrawn; primary given reason for a preference mooted by ensuring AWB doesn't autoreplace transl
with transliteration
. Thanks, everyone! (
non-admin closure)
Remsense
诉 06:54, 7 April 2024 (UTC)
Template:Transliteration →
Template:Translit – The extra eration really contributes to a readability issue when there are lists, tables, or any preponderance of this template in an article—I get that {{
transl}}
is undesirably ambiguous, but frankly: the shorter the better. I would even prefer {{
tlit}}
if other people will let me get away with it.
No one in the 2022 move discussion mentioned an explicit issue with {{
translit}}
, so hopefully folks would be okay with it now.
Remsense
诉 18:25, 5 April 2024 (UTC)
{{
transl}}
et al with {{
transliteration}}
, roughly in line with other substitutions, which I agree with in principle because consistency between articles is nice. I did specifically poke around the tool talk page asking whether such an replacement could be removed, but no one seemed interested, so I guess I'm just realizing this is a bit of forum shopping to that effect, whoops.{{
transliteration}}
is better solely for reasons of clarity is largely theoretical, as I haven't seen anyone say its meaning is actually unclear or confusing I hope you see how the flexibility in that guideline allows for us to disagree on this point.
Remsense
诉 01:13, 6 April 2024 (UTC)
Before adding a rule here, you must ensure that there is consensus in favour of the template renaming.Those two redirects were added by Mclay1 in February 2023; that editor might be able to link to a relevant discussion. – Jonesey95 ( talk) 14:03, 6 April 2024 (UTC)
Are there style guidelines for the use of both {{ translation}} and {{ transliteration}} in conjunction with {{ lang}}? E.g., "להד״מ (lahada"m), לא היו דברים מעולם (lo hayu dvarim meolam) - transl. such things never were, no way" -- Shmuel (Seymour J.) Metz Username:Chatul ( talk) 13:46, 14 April 2024 (UTC)
![]() |
Template:Transliteration is permanently
protected from editing because it is a
heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by
consensus, editors may use {{
edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's
documentation to add usage notes or
categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
![]() | This template was considered for deletion on 6 September 2013. The result of the discussion was "no consensus". |
![]() | Text and/or other creative content from this version of Template:Transl was copied or moved into incubator:Template:Wp/nod/transl with this edit. The former page's history now serves to provide attribution for that content in the latter page, and it must not be deleted as long as the latter page exists. |
![]() | This template does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||
|
![]() | This page has previously been nominated to be moved.
Discussions:
|
|
|
This page has archives. Sections older than 1000 days may be automatically archived by Lowercase sigmabot III when more than 3 sections are present. |
The result of the move request was: moved. Noting that there is not a consensus to delete the redirect created as a result of the move. That would require an additional discussion at WP:RfD. ( closed by non-admin page mover) Elli ( talk | contribs) 20:47, 14 March 2022 (UTC)
Template:Transl → Template:Transliteration – This template "transliterates" the input text. So, the new title is more proper and complete than simply transl. Also, the part transl is common for both the words translation and transliteration. As such, this template should be moved to Template:Transliteration to provide natural disambiguation against Template:Translation. --- CX Zoom(he/him) ( let's talk| contribs) 19:37, 22 February 2022 (UTC)
there's less need to have good wikicodeI completely disagree with this. Our non-mainspace templates should be as clear as our mainspace templates, for easy use and clarity. If we go down the path of considering mainspace templates being superior, then we would lose many editors that work in non-mainspace. 🐶 EpicPupper (he/him | talk) 21:12, 1 March 2022 (UTC)
subst
or otherwise correct templates, so the
WP:BAG should be able to quickly approve the task if necessary. —
Jkudlick ⚓
(talk) 17:00, 3 March 2022 (UTC)
{{translation}}
produces
transl., which is exactly what the name of this completely different Template is. But I also agree with Asukite that it has 44,000 transclusions (via other redirects or not), so we'd have to change all of them. Yes there are bots but I'm not very sure if we need to do so much here. ---
CX Zoom(he/him) (
let's talk|
contribs) 17:54, 3 March 2022 (UTC)
At this edit, Editor Ineffablebookkeeper added this to the documentation:
{{lang|xx-Latn|...}}
can cause discrepancies in font display when used for transliteration; as such, {{transl|xx|...}}
is preferred for transliterations.@Editor Ineffablebookkeeper: do you have any examples that show that what you wrote is true?
— Trappist the monk ( talk) 13:18, 22 March 2022 (UTC)
{{lang|ja-Latn|Hana}}
{{transl|ja|Hana}}
Might be me being stupid here. The point of the FOREIGNITALIC stuff is to make sure it's not jarring when you're using casual foreign terms, but it seems like the lang templates in certain browsers deliberately sets off the text (which is the only reason I noticed it in the first place)—so the text was weirdly a different typeface and looked bizarre in the plot summary... but it doesn't seem to do it on all the browsers and OS configurations I've tried, so I guess it's a specific setting. So I dunno. I hate it aesthetically because it looks like someone mad-libbed the text, but at the same times that's the point of the templates. I guess disregard. Der Wohltemperierte Fuchs talk 18:11, 29 January 2021 (UTC)
- Aha, don't worry! I think on my other (very dead at the minute) laptop, it does display differently. It's not a problem! It does look like a ransom note cut out of a newspaper at times, lmao. --Ineffablebookkeeper (talk) 21:10, 29 January 2021 (UTC)
<span title="Japanese-language text"><i lang="ja-Latn">Hana</i></span>
← {{lang|ja-Latn|Hana}}
<span title="Japanese-language romanization"><i lang="ja-Latn">Hana</i></span>
← {{transl|ja|Hana}}
<i lang="ja-Latn">Hana</i>
which is the same for both {{
lang}}
and {{
transl}}
.I may be mistaken, but unlike the Lang template, it doesn't look like the Transliteration template adds the category "Articles containing x-language text" to articles using it. Some articles contain only transliterated foreign-language text, not the original script, and won't have the category applied to them. Why are the two templates different in this regard? flod logic ( talk) 08:32, 18 January 2023 (UTC)
{{
transl}}
accepts both language and script tags, it seems to me that this template should not share the categories:
{{
Non-English-language text category}}
does for the language categories.Can the Transliteration template be modified to support Private-use language tags? I have been expanding Wikipedia's coverage of ancient history, and I am finding myself needing for the transliteration template to render Private-use language tags, but it seems that it does not currently do so.
Seeing as the expansion of Wikipedia's ancient history coverage would inevitably make it a necessity, can I request for the Transliteration template to be modified so that it can render Private-use language tags? Antiquistik ( talk) 12:01, 19 January 2023 (UTC)
Hi @ Jonesey95, why did you revert me? [1] “Source text to be transliterated,” foreign-script text like барахло, is never to be entered into this template. Only its corresponding Latin-alphabet target transliteration, like barakhlo. — Michael Z. 02:05, 6 June 2023 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change: Hi. I want to change the Proto-cuneiform listing to point to the main article ie "Proto-cuneiform" from the current "Proto-cuneiform numerals", which is a sub-article. Thanks. Ploversegg ( talk) 02:44, 15 January 2024 (UTC) Diff:
− | + | CHANGED_TEXT |
Ploversegg ( talk) 02:44, 15 January 2024 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Description of suggested change: Lets see if I can do better this time. I would like to request that in "Template:ISO 15924 script codes and related Unicode data" in the line "Pcun" that "Proto-cuneiform numerals" be changed to "Proto-cuneiform" corresponding to the article Proto-cuneiform. Thanks. Ploversegg ( talk) 19:53, 15 January 2024 (UTC)
Diff:
− | + | CHANGED_TEXT |
Ploversegg ( talk) 19:53, 15 January 2024 (UTC)
{{
ISO 15924 script codes and related Unicode data}}
is not part of {{
transliteration}}
per se. It is its own template. It calls {{
ISO 15924 script codes and related Unicode data/row}}
which has this:
[[{{ISO 15924/wp-article|1={{{alpha4|}}}}}|{{ISO 15924 name|1={{{alpha4|}}}}}]]
{{{alpha4|}}}
is the ISO 15924 tag (in this case pcun
). {{
ISO 15924/wp-article}}
defines pcun
as Proto-cuneiform numerals
but {{
ISO 15924 name}}
defines pcun
as Proto-Cuneiform
.{{ISO 15924/wp-article}}
yourself.The inclusion of the equal sign (=) in texts results in an error message instead of the text being displayed. This causes serious issues for the transliteration of languages like Hurrian, Urartian, Ancient Egyptian, and Luwian, whose transliteration requires the use of the equal sign.
For example:
Can this issue be fixed? Antiquistik ( talk) 14:02, 23 March 2024 (UTC)
{{
transl}}
and has been ever thus for all templates that use positional parameters. So, in |pašš-ēt-i=t=ān
, pašš-ēt-i
is interpreted as the parameter name and t=ān
is that parameter's value. Because pašš-ēt-i
is not a parameter name that {{transl}}
recognizes, it is ignored. The no text error message occurs because {{transl}}
did not get a valid second (text) parameter. The commonly used work-around for this is to number the second positional parameter:
{{transl|xhu|2=pašš-ēt-i=t=ān}}
→ pašš-ēt-i=t=ānThe result of the move request was: not moved. Withdrawn; primary given reason for a preference mooted by ensuring AWB doesn't autoreplace transl
with transliteration
. Thanks, everyone! (
non-admin closure)
Remsense
诉 06:54, 7 April 2024 (UTC)
Template:Transliteration →
Template:Translit – The extra eration really contributes to a readability issue when there are lists, tables, or any preponderance of this template in an article—I get that {{
transl}}
is undesirably ambiguous, but frankly: the shorter the better. I would even prefer {{
tlit}}
if other people will let me get away with it.
No one in the 2022 move discussion mentioned an explicit issue with {{
translit}}
, so hopefully folks would be okay with it now.
Remsense
诉 18:25, 5 April 2024 (UTC)
{{
transl}}
et al with {{
transliteration}}
, roughly in line with other substitutions, which I agree with in principle because consistency between articles is nice. I did specifically poke around the tool talk page asking whether such an replacement could be removed, but no one seemed interested, so I guess I'm just realizing this is a bit of forum shopping to that effect, whoops.{{
transliteration}}
is better solely for reasons of clarity is largely theoretical, as I haven't seen anyone say its meaning is actually unclear or confusing I hope you see how the flexibility in that guideline allows for us to disagree on this point.
Remsense
诉 01:13, 6 April 2024 (UTC)
Before adding a rule here, you must ensure that there is consensus in favour of the template renaming.Those two redirects were added by Mclay1 in February 2023; that editor might be able to link to a relevant discussion. – Jonesey95 ( talk) 14:03, 6 April 2024 (UTC)
Are there style guidelines for the use of both {{ translation}} and {{ transliteration}} in conjunction with {{ lang}}? E.g., "להד״מ (lahada"m), לא היו דברים מעולם (lo hayu dvarim meolam) - transl. such things never were, no way" -- Shmuel (Seymour J.) Metz Username:Chatul ( talk) 13:46, 14 April 2024 (UTC)