Template talk:Lang
This is the talk page for discussing improvements to the Lang template. |
|
Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13Auto-archiving period: 120 days ![]() |
![]() | This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||
|
![]() | Template:Lang 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 2006 February 20. The result of the discussion was "keep". |
![]() | To help centralise discussions and keep related topics together, the talk pages for all help pages, categories, MediaWiki messages and templates related to cite errors redirect here. |
|
|||||||||||||
This page has archives. Sections older than 120 days may be automatically archived by Lowercase sigmabot III. |
Foreign-language article titles
[edit]archived to Wikipedia_talk:Manual_of_Style/Text_formatting/Archive_7#Foreign-language_article_titles
31 August 2021 (UTC)
Forced prefixing of *
[edit]I've just noticed that use of codes for protolanguages, as in {{lang|cel-x-proto|...}}
, forces a prepended * (indicating a construction unattested in surviving materials). This is undesirable, since in the vast majority of cases what we're going to be doing is replacing existing in-article strings with bare italics and no lang markup, like *''kal-''
, with templated replacements, e.g. *{{lang|cel-x-proto|kal-}}
, but this produces a double ** which has to be manually fixed. And there are apt to be tabular-data cases (interlinear glosses, etc.) in which an entire row of cells is prefixed with * and specific words or morphemes in particular cells follow this and should not each individually have * but should still have language markup. At bare minimum we need a way to suppress this "auto-*" behavior, but ideally it would be off by default and turned on only by a parameter switch, since it is unexpected, inconsistent, completely undocumented, and almost always editorially unhelpful. PS: If this does get changed, please ping me, since I will need to go fix Caledonians#Etymology and some other things to have non-templated * again. — SMcCandlish ☏ ¢ 😼 07:35, 2 March 2024 (UTC)
- Two thoughts: there is some value to the asterisk symbol as unattested (especially if we tooltip the first occurrence à la {{c.}}), so could we use {{asterisk}}, or perhaps (new) {{unattested}} and have that resolve to {{asterisk}}? Alternatively, what about just using one of the many star-shaped thingies that look like asterisk, but aren't, e.g.,
- ❋ (U+274B HEAVY EIGHT TEARDROP-SPOKED PROPELLER ASTERISK) (my favorite, but several more hidden in the wikicode).
- Thanks, Mathglot (talk) 11:17, 2 March 2024 (UTC)
- Using an alternative character would be WP making up a "fake style" out of nowhere. The standard across all linguistics writing since at least the Victorian era is the * symbol (asterisk). — SMcCandlish ☏ ¢ 😼 05:07, 10 June 2024 (UTC)
- Already exists but, alas, not documented:
{{lang|cel-x-proto|kal-}}
→ *kal-{{lang|cel-x-proto|kal-|proto=no}}
→ kal-{{lang-cel-x-proto|kal-}}
→ Proto-Celtic: *kal-{{lang-cel-x-proto|kal-|proto=no}}
→ Proto-Celtic: kal-
- —Trappist the monk (talk) 15:02, 2 March 2024 (UTC)
Testing bullet-asterisk interaction with proto asterisk:
- one asterisk, to make a bullet item
- *kal- one asterisk, followed immediately by
{{lang|cel-x-proto|kal-}}
- one asterisk to make another bullet item
Looks good. We should document Module code starting at line 791 of the Module in a new, level-4 subsection 'Proto' at Template:Lang, probably to live under section § Formatting. Mathglot (talk) 20:05, 2 March 2024 (UTC)
- But wait—you said in sentence 2, but this produces a double ** which has to be manually fixed, so what was your example that produced a double asterisk? It seems to be the identical code that works just above. Can you reproduce your error case below? Mathglot (talk) 20:14, 2 March 2024 (UTC)
- To repeat from the OP:
in the vast majority of cases what we're going to be doing is replacing existing in-article strings with bare italics and no lang markup, like
If the solution is changing*''kal-''
, with templated replacements, e.g.*{{lang|cel-x-proto|kal-}}
, but this produces a double ** which has to be manually fixed.*''kal-''
to*{{lang|cel-x-proto|kal-|proto=no}}
or to{{lang|cel-x-proto|kal-}}
, I guess I can live with that, but I still think it would be preferable for the template to not force the * by default. — SMcCandlish ☏ ¢ 😼 05:07, 10 June 2024 (UTC)
- To repeat from the OP:
Interslavic has recently received an ISO 639-3 code: isv
. Latin and Cyrillic are equal in status in Interslavic, just like in Serbo-Croatian. –Vipz (talk) 09:34, 27 April 2024 (UTC)
isv
not listed in the current (2024-03-07) version of the IANA language-subtag-registry file so nothing to be done yet.- —Trappist the monk (talk) 11:42, 27 April 2024 (UTC)
- It is now. "Added: 2024-05-15" -- --Error (talk) 11:43, 22 May 2024 (UTC)
Quoting multiple alternative translations
[edit]How does one correctly quote multiple translations using this template? I am trying to fix an issue on German Air Force, which includes in its lede the problematic lang-de template
German: Luftwaffe, lit. 'air weapon or air arm'
from the source code
{{lang-de|'''Luftwaffe'''|lit=air weapon or air arm}}
which is not quoted correctly. I can fix this by doing
{{lang-de|'''Luftwaffe'''|lit=air weapon' or 'air arm}}
leading to
German: Luftwaffe, lit. 'air weapon' or 'air arm'
but this is a rather inelegant hack. Is there a better way to quote multiple lit values?
I have searched the talk archives here but couldn't find anything if this had been asked before. Thanks, Ainlina(box)? 15:30, 29 April 2024 (UTC)
- In context, it would seem to me that
|lit=air force
is a better choice for the lead. If you wish to delve into the etymology of the word, perhaps a footnote linking the Wiktionary German entry for Luftwaffe is appropriate. - Recently, there has been discussion at Wikipedia talk:WikiProject Military history § Luftwaffe, lang template/italics or not? that you might find interesting.
- —Trappist the monk (talk) 15:51, 29 April 2024 (UTC)
Question about Category:Articles containing Dogrib-language text
[edit]For some reason, Category:Articles containing Dogrib-language text has started showing an error message (Error: Dogrib is not a valid ISO 639 or IETF language name. Please see Template talk:Lang for assistance.), is empty, and has been tagged for speedy deletion. We still have an article at Dogrib language, and the ISO 639 code is still dgr. It appears that articles that should be placed into that category are now being placed into the new (as of 22 May 2024) Category:Articles containing Tlicho-language text. I don't know what happened behind the scenes (maybe this change?), but we have an inconsistency between our article name and our category naming, which is undesirable. – Jonesey95 (talk) 23:41, 27 May 2024 (UTC)
- The 2024-04-15 update to the ISO 639-3
dgr
name list is the result of this change request. That update is reflected in this update to Module:Language/data/ISO 639-3. Subsequently, IANA incorporated that change (in reverse name-order in the 2024-05-16 update to their language-subtag-registry file which is reflected in this update to Module:Language/data/iana languages. - When multiple names are provided by IANA, Module:Lang takes the first name in the list – in this case 'Tlicho'. This may be overridden in Module:Lang/data when there is consensus to do so.
- —Trappist the monk (talk) 18:01, 28 May 2024 (UTC)
- I believe that the stable title (for the last eight years or so) of our Dogrib language article constitutes sufficient consensus to override. I poked around the sources, and they seem to be split somewhat evenly among "Dogrib", "Tlicho", and "Tłı̨chǫ Yatıì", the latter of which would be a challenging article name for the English Wikipedia. If the article is moved, the override can easily be removed. – Jonesey95 (talk) 00:27, 29 May 2024 (UTC)
Limitations possibly requiring template modification
[edit]Given that I edit ancient history articles, I have to use this template extensively for a large range of languages, and I'm finding some lacks in it that limit my ability to edit:
- the
{{lang-
form of the template should also display a label for the name of the language used similar to when using the{{lang|
form; - the
{{lang|
form needs a|translit=
option that works just like it does with the{{lang-...
form; - the
|translit=
needs an option where there is a comma instead of the romanized: label usually preceding the transcription in addition to the already existing format with the romanized: label; - there needs to be an option for adding multiple spellings and multiple transliterations; for example:
- the name Tuwaddis was recorded as 𔕬𔗬𔑣𔓯𔗔 and 𔕬𔓬𔑣𔕣, and presenting them in an article currently requires me to write
- the code
{{lang-hlu|𔕬𔗬𔑣𔓯𔗔}} <small>and</small> {{lang|hlu|𔕬𔓬𔑣𔕣}}, <small>romanized</small> {{transl|akk-x-neobabyl|Tuwaddis}}
- to obtain Hieroglyphic Luwian: 𔕬𔗬𔑣𔓯𔗔 and 𔕬𔓬𔑣𔕣, romanized Tuwaddis;
- the code
- similarly, if I want to make a list of the various forms of the Hieroglyphic Luwian name Ḫartapus in an article, I would need to write it
- as
{{lang-hlu|𔓟𔖱𔐞𔕯𔗔}}, {{lang|hlu|𔓟𔖱𔐞𔗣𔗔}} and {{lang|hlu|𔗖𔐞𔕯𔗔}}, <small>romanized:</small> {{transl|hlu|Ḫartapus}}
- to obtain Hieroglyphic Luwian: 𔓟𔖱𔐞𔕯𔗔, 𔓟𔖱𔐞𔗣𔗔 and 𔗖𔐞𔕯𔗔, romanized: Ḫartapus;
- as
- meanwhile, the name 𒁹𒌇𒁮𒈨𒄿 is interpreted as either Tugdammî and Dugdammî, and presenting them in an article currently requires me to write
- the code
{{lang-akk-x-neoassyr|𒁹𒌇𒁮𒈨𒄿|translit=Tugdammî}} <small>or</small> {{transl|akk-x-neoassyr|Dugdammî}}
- to obtain Neo-Assyrian Akkadian: 𒁹𒌇𒁮𒈨𒄿, romanized: Tugdammî or Dugdammî;
- the code
- and the name 𒁹𒄖𒊌𒄖 is interpreted as both Gugu and Guggu, but presenting it in an article would require that I write
- the code
{{lang-akk-x-neoassyr|𒁹𒄖𒊌𒄖|translit=Gugu}} <small>and</small> {{transl|akk-x-neoassyr|Guggu}}
- to obtain Neo-Assyrian Akkadian: 𒁹𒄖𒊌𒄖, romanized: Gugu and Guggu
- the code
- if I need to make a list of the various spellings of the name māt Tabali, for example, I need to write
- the code
{{transl|akk-x-neoassyr|māt Tabali}} ({{lang|akk-x-neoassyr|𒆳𒋫𒁀𒇷}}, {{lang|akk-x-neoassyr|𒆳𒋫𒁀𒀀𒇷}}, {{lang|akk-x-neoassyr|𒆳𒋫𒁄𒇷}}, {{lang|akk-x-neoassyr|𒆳𒋰𒀀𒇷}})
- to obtain māt Tabali (𒆳𒋫𒁀𒇷, 𒆳𒋫𒁀𒀀𒇷, 𒆳𒋫𒁄𒇷, 𒆳𒋰𒀀𒇷);
- the code
- and if I want to make a list of the various forms of the name Qedar, I need to write
- the code Neo-Assyrian Akkadian: 𒆳𒆤𒊑, Qidri; 𒆳𒆤𒊏𒀀𒀀, Qidrāya; 𒆳𒆥𒁕𒀀𒊑, Qidāri; 𒆳𒋡𒁕𒊑, Qadari; 𒆳𒋡𒀜𒊑, Qadri; 𒇽𒆤𒊏𒀀𒀀, Qidrāya; 𒇽𒆥𒁯𒊏𒀀𒀀, Qidarāya; 𒌷𒆥𒁕𒊑, Qidari; and 𒇽𒄣𒁕𒊑, Qudari
- the name Tuwaddis was recorded as 𔕬𔗬𔑣𔓯𔗔 and 𔕬𔓬𔑣𔕣, and presenting them in an article currently requires me to write
- I would also require a transcription parameter because some scripts are not transcribed in the exact same was as their reconstructed pronunciation, and this sometimes needs to be shown in the text.
- For example, Mycenaean Greek kʰalkós was written as 𐀏𐀒 in Linear B script, which is transcribed as ka-ko, but the template as it now exists only allows me to add the Linear B text and the word as it was pronounced, but not the transcription of the text;
- Integrating the functions of
{{script}}
into the{{lang}}
template would also be useful because sometimes the coding takes too much space in the article or using it makes the article unnecessarily big so that it would be preferable to shift this onto the templates instead.- For example,
{{lang-ae|}}
and{{lang|ae|}}
should have a parameter that functions in the same way as if{{lang-ae|{{script|Avst|}}}}
and{{lang|ae|{{script|Avst|}}}}
were used.- Some scripts, like cuneiform, however use multiple variants due to how widespread and long-lived their use was, and, if creating such a parameter is possible, it would need to be able to render the various fonts used in Template:Script/Cuneiform.
- This parameter should be optional, however, because some of the script templates, like
{{script|Grek|}}
and{{script|Latn|}}
render the text in a font that is difficult to read and are therefore already discouraged.
- For example,
- There also needs an option where interting
-
in the text parameter followed by the transliteration in the template displays the language followed by the transliteration.- For example,
{{lang-sa|-|bharu}}
should give something that displays like Sanskrit: bharu.
- For example,
Would it be feasible to modify the template so as to remove any or some or even all of these current limitations? Antiquistik (talk) 15:01, 28 May 2024 (UTC)
- @Trappist the monk: can any of these issues be resolved? Antiquistik (talk) 08:13, 3 June 2024 (UTC)
- I numbered your list to make it easier to answer.
- 1. because
{{lang-??}}
already has a wikilinked language label, using thelabel=
html attribute is considered redundant or superfluous - 2. might be done but probably not necessary because
{{transliteration}}
exists to serve that purpose - 3. see 4
- 4. if you do a lot of these custom lists, you might be better served to create one or more templates to do the grunt work
- 5. a new template,
{{transcript}}
might be created; you will need to work out details of its implementation - 6. nesting templates in
{{lang}}
may take more space, but space in a Wikipedia article is not an issue; this is not a dead tree encyclopedia - 7.
{{transliteration-??}}
templates might be created; you will need to work out the implementation details
- 1. because
- In general, Module:Lang works well for the vast majority of its uses; mucking about with that for a small number of articles seems to me to be counterproductive.
- —Trappist the monk (talk) 14:22, 3 June 2024 (UTC)
- @Trappist the monk: For #6, I've faced problems with pages I rewrote becoming too big per WP:TOOBIG before, so space is unfortunately an issue.
- For #2, editing using both
{{transliteration}}
and{{lang|}}
for this purpose is too cumbersome and unwieldy. Adding a|translit=
parameter to{{lang|}}
would be the best option. - For #3, I am not sure I understand how #4 relates to this issue. You might need to spell it out for me.
- For #4, yes, a separate template for lists would be ideal. It should work like Wiktionary's
{{desc|
template, minus creating a link for the term. However, the options for the first four sub-issues should be integrated into{{lang|}}
/{{lang-}}
. - For #5, an additional transcript template would definitely be a very useful addition. However, I also have no choice in needing the transcription option to be part of
{{lang}}
as well. There are articles in some scripts that really do need a Name in script, followed by a transliteration, followed by a transcription, option. This is especially important because the present|translit=
parameter is presently used for transcription instead than transliteration but otherwise still require both transcription and transliterations, including in articles that are not part of the topics that I cover. - For #7, what would be ideal would be both a
{{transliteration}}
template and the option to insert a nil parameter in the present template as well. - As for #1, well, I can do without it for now. But I would still support adding a label if the question arises again in the future. In my (personal) opinion, the label in fact makes it more easily to read the pages.
- Additionally, could you modify the private-use tag
akk-x-latbabyl
to render as "Late Babylonian Akkadian" rather than simply as "Late Babylonian" as it now does? - Antiquistik (talk) 19:31, 7 June 2024 (UTC)
- @Trappist the monk: Can you have a look at my response and see what can be done please? Antiquistik (talk) 06:26, 25 June 2024 (UTC)
- I numbered your list to make it easier to answer.
Mild performance improvement
[edit]I have been looking at Kashmiri language and wondering why it takes a long time to build the page.
In the timing stats on the page, the lua function gcodepoint_init is high on the list. Looking at the wikitext of the page, templates of the form {{#invoke:lang|lang|ks|{{uninastaliq... (of which there are over 900) are responsible for this timing. For each of these calls, gcodepoint_init is called three times.
The call to gcodepoint_init actually comes from Module:Unicode_data is_Latin
Now to the point, Module:Lang calls is_Latin from line 988 and is_rtl (which calls is_Latin) from lines 549 and 551.
The call to is_rtl could be made once and then used in the two succeeding if statements - hence saving a call Desb42 (talk) 08:16, 7 June 2024 (UTC)
Renaming a template per ISO 639 changes?
[edit]At Template talk:Lang-sh#HBS?, we've had a question whether to use "sh" or "hbs" as the template name/code. Is this a doable change, is there something to think about? The first thing that occurs to me is that the TFD notice would clutter a lot of lead sections... --Joy (talk) 15:05, 8 June 2024 (UTC)
- Anything is possible. What is the end goal? Change instances that use {{Lang-sh}} to {{Lang-hbs}} or just switch between the current template and the "hbs" redirect? If the first and there is consensus on the page, a bot operator could help with the 800s transclusions, if just rename, then anyone that can rename pages can do that or WP:RM/T. Also a small edit to the template to change the code parameter. Gonnym (talk) 15:16, 8 June 2024 (UTC)
- So if I get this right, you wouldn't use a TFD tagging procedure? --Joy (talk) 19:15, 8 June 2024 (UTC)
sh
is the IETF BCP 47 language subtag utilized for Serbo-Croatian, and these are the basis for Wikipedia's lang templates and by extent subdomains (which is the reason sh.wikipedia.org does not need to move to hbs.wikipedia.org). –Vipz (talk) 16:37, 8 June 2024 (UTC)- @Vipz well, that's actually making things a tad more confusing because there it says for "sh":
Registry comment: sr, hr, bs are preferred for most modern uses
sh is a macrolanguage that encompasses the following more specific primary language subtags: bs hr sr cnr. If it doesn't break legacy usage for your application, you should use one of these more specific language subtags instead. On the other hand, sh is often preferred by legacy applications rather than sr (Serbian).
- We're not just using it for legacy applications. --Joy (talk) 19:14, 8 June 2024 (UTC)
- Interestingly, that quoted material doesn't mention "hbs". — SMcCandlish ☏ ¢ 😼 04:38, 10 June 2024 (UTC)
Side question on Proto-[Foo]
[edit]Why are we at en.wp using, e.g., gem-x-proto while en.wikt is using gem-pro? Is one site or other making a grave mistake? — SMcCandlish ☏ ¢ 😼 04:39, 10 June 2024 (UTC)
Early Modern English?
[edit]Not sure of the process here, but is it possible to make the template accept Early Modern English as a language? There are some long quotations on Elinor Fettiplace which, while definitely not in Middle English, must be extremely confusing to a screen reader. ISO 639-6 proposed emen
as a code for it, but as I gather was not accepted. UndercoverClassicist T·C 08:40, 22 June 2024 (UTC)
{{lang|en-emodeng|text}}
→ text{{lang-en-emodeng|text}}
→ Early Modern English: text- —Trappist the monk (talk) 11:39, 22 June 2024 (UTC)
- Wonderful: thank you! UndercoverClassicist T·C 15:11, 22 June 2024 (UTC)
lang-xx missing tooltip?
[edit]Didn't {{lang-xx}} use to add a tooltip, the same as {{lang}}, or am I mistaken? For example:
{{lang|fr|bonjour}}
bonjour
French-language text
{{lang-fr|bonjour}}
French: bonjour
— W.andrea (talk) 00:01, 3 July 2024 (UTC)
- Perhaps for a short time. In the olden days before Module:Lang,
{{lang-fr}}
called{{language with name}}
which called{{lang}}
. This wikitext form did not have a tooltip. During the transition to Module:Lang,{{lang}}
was the first to be converted. The new{{lang}}
has a tooltip. Before{{lang-fr}}
was converted to directly call Module:Lang, it continued to call the new{{lang}}
so did have a tooltip. When{{lang-fr}}
was converted to directly call Module:Lang, the tooltip went away because it is redundant to the language label link that precedes the French language text. - If you must have the redundant tooltip, you can use
{{language with name}}
:{{language with name|fr|French|bonjour}}
→ French: bonjour – has a tooltip because this template calls{{lang}}
.
- —Trappist the monk (talk) 01:03, 3 July 2024 (UTC)
the tooltip went away because it is redundant to the language label
- Oh, of course! I don't know how I didn't realize that. Thanks! — W.andrea (talk) 01:10, 3 July 2024 (UTC)
Schrödinger's language template
[edit]The latest run of Special:WantedCategories featured a redlink for Category:Articles containing no linguistic content-language text, autogenerated by an invocation of {{Lang-zxx}} in emoji.
Now, I grok the context of what it would be for — the template was used in the emoji article to reify a short series of non-linguistic colour-code boxes into "language", because of a technical glitch that was bleeding into the rest of the paragraph when the colour codes were just sitting as raw "text" not wrapped in a lang template, so basically it's a wrapper for non-linguistic content (symbols, colour codes, etc.) that has to be treated as para-linguistic for some technical reason or other. But its name is weird and illogical on its face — "no linguistic content language"? — and it's a category that has existed in the past but was deleted. I was able to make it go away by wrapping the lang-zxx template in the {{suppress categories}} wrapper, but since it's template-generated it may recur again in the future.
So is this a category that we want, at either that seemingly oxymoronic name or another more logical alternative? Obviously it can be created if it's desired and its name is considered fine — but if an alternative name would be more desirable, then the lang-zxx template needs to be modified to generate that alternative name instead, and if it's undesirable at any name then the lang-zxx template needs to be prevented from generating it at all. But those are both things that would require a higher level of template-coding expertise than I've got, so I'm bringing it to the project's attention so that I don't break stuff. Thanks. Bearcat (talk) 15:26, 31 July 2024 (UTC)
- The category was nominated for CSD G8 deletion 22 September 2020 by Editor Gonnym without explanation and deleted the same day by Editor Maile66 using an automated process; also without explanation. Seems to me that the category should not have been deleted because the category was marked with
{{Possibly empty category}}
. Perhaps this was an oversight because at the time we were shifting the category documentation templates from{{Category articles containing non-English-language text}}
which required parameters to{{Non-English-language text category}}
which does not require parameters. - I am wholly indifferent to the category name. If it is really important, it can be changed but I see no pressing need.
- A benefit of template documentation is that it lists available parameters. For
{{lang}}
(and its{{lang-xx}}
counterparts) the documentation lists both|nocat=
(accepting a variety of positive values) and|cat=
accepting a variety of negative values). Both parameters accomplish the same thing: when set appropriately, the template will not emit categories. - —Trappist the monk (talk) 16:41, 31 July 2024 (UTC)
- I don't remember why I nominated it. If it is only created by usages of Template:Lang-zxx and that template did not exist at the time, then that probably was a likely reason, as those categories shouldn't be manually populated and at the time there was no automatic template handling this. Gonnym (talk) 18:27, 31 July 2024 (UTC)
- The OP erred; there is no
{{lang-zxx}}
in Emoji and that template did not exist at the time of the category's deletion. But,{{lang|zxx|...}}
was/is a legitimate use (Emoji has{{lang|zxx-Zsye|🏻 🏼 🏽 🏾 🏿}}
). Use of{{lang|zxx|...}}
would have emitted Category:Articles containing no linguistic content-language text then as it does now; see line 548 et seq. (19 September 2020 permalink) in Module:Lang. - —Trappist the monk (talk) 18:56, 31 July 2024 (UTC)
- The OP erred; there is no
- I don't remember why I nominated it. If it is only created by usages of Template:Lang-zxx and that template did not exist at the time, then that probably was a likely reason, as those categories shouldn't be manually populated and at the time there was no automatic template handling this. Gonnym (talk) 18:27, 31 July 2024 (UTC)
Rut
[edit]Hello!
Please change in the (1) Module:Lang/data/iana languages: ["rut"] = {"Rutul"} to ["rut"] = {"Rutulian"}. (and also in these modules: (2) Module:ISO_639_name/ISO_639-3, (3) Module:ISO_639_name/ISO_639_name_to_code)
Thank you. Digitalberry (talk) 08:36, 5 August 2024 (UTC)
- Not what it's called in the ISO 639 specification. Remsense诉 08:38, 5 August 2024 (UTC)
- Thanks for your reply. Could you give me the source (link) you are referring to? Digitalberry (talk) 08:46, 5 August 2024 (UTC)
- I didn't find the source. Can you provide me with the source? Digitalberry (talk) 09:34, 5 August 2024 (UTC)
- Well, the source is ISO 639. You can see a corresponding table we have at ISO 639:r Remsense诉 10:15, 5 August 2024 (UTC)
- Also, you could've followed the ISO 639 link on the Rutul language page itself. Remsense诉 10:16, 5 August 2024 (UTC)
- Thanks for the answer. Still, the data indicated there is erroneous and needs to be clarified. Digitalberry (talk) 10:22, 5 August 2024 (UTC)
- That's unfortunate; this tool and many other second-order tools use the ISO-assigned name, so there's not much to do here I'm afraid. Remsense诉 10:50, 5 August 2024 (UTC)
- Well, the source is ISO 639. You can see a corresponding table we have at ISO 639:r Remsense诉 10:15, 5 August 2024 (UTC)
- We can override some language names used by
{{lang}}
which are taken from the IANA language subtag registry which draws tags/names from all of the ISO 639 standards. The override is accomplished in Module:Lang/data when there is evidence of sufficient consensus to do so. That consensus often takes the form of an en.wiki article under the desired name. That is not the case here. - —Trappist the monk (talk) 11:10, 5 August 2024 (UTC)
- I think the right way is to change the information via a request to ISO-639. Digitalberry (talk) 11:48, 5 August 2024 (UTC)
Spelling of "Romanization"
[edit]Any way to allow the BrE spelling of "Romanisation" when using e.g. Template:lang-grc? An optional parameter like |-ise=y
(similar to how date templates have |df=y
) would seem like a possible solution. UndercoverClassicist T·C 21:48, 28 August 2024 (UTC)
- Perhaps, I have not looked in the the details. There has to be a better parameter name;
|engvar=gb
? Module:lang currently supports eight regional variants of English:["en-au"] = "Australian English", ["en-ca"] = "Canadian English", ["en-gb"] = "British English", ["en-ie"] = "Irish English", ["en-in"] = "Indian English", ["en-nz"] = "New Zealand English", ["en-us"] = "American English", ["en-za"] = "South African English"
- If we do this, the default will remain as it is:
|engvar=us
. - Your task is to research these variants and group them by suffix: ~ise or ~ize (or other?). Report back with the results.
- —Trappist the monk (talk) 22:26, 28 August 2024 (UTC)
- I am honoured -- let's see if I can do this with a nice table. Data source for the moment is our respective articles on the dialects, except for South African English, which luckily has plenty of results on Google to say that it follows the British system.
EngVar | Suffix |
---|---|
en-au | -ise |
en-ca | -ize |
en-gb | -ise |
en-ie | -ise |
en-in | -ise |
en-nz | -ise |
en-us | -ize |
en-za | -ise |
It might be worth clarifying in the documentation that if people want to use e.g. Oxford English (which uses -ize but otherwise follows regular BrE), they can just set the parameter to en-us and it won't affect anything except that single word? UndercoverClassicist T·C 22:39, 28 August 2024 (UTC)
lang-my outputs tofu on my browser (FF)
[edit]I've been removing lang-my where I come across it because it turns burmese script into tofu. Not sure what the problem is, but assume it's forcing a script to display that I don't have installed. I have a number of burmese scripts, though, including generic ones like Noto, so display shouldn't be a problem. — kwami (talk) 09:26, 31 August 2024 (UTC)
- Don't do that without evidence that
{{lang-my}}
is at fault. Here are examples of differently written Burmese text:- မြန်မာအက္ခရာ ← plain text; no markup
- မြန်မာအက္ခရာ ←
<span>မြန်မာအက္ခရာ</span>
- မြန်မာအက္ခရာ ←
<span lang="my">မြန်မာအက္ခရာ</span>
- Burmese: မြန်မာအက္ခရာ ←
{{lang-my|မြန်မာအက္ခရာ}}
[[Burmese language|Burmese]]: <span lang="my">မြန်မာအက္ခရာ</span>
- For me, all of the above render correctly (win 10, chrome). Do any of the above render correctly for you?
- We have had discussions with you about fonts in the past:
- None of those discussions revealed a problem with
{{lang}}
, the various{{lang-xx}}
, or Module:Lang. - —Trappist the monk (talk) 13:54, 31 August 2024 (UTC)
- The results of 1 and 2 display correctly (as well as the code of all 5). lang="my" appears to be the problem, and lang-my appears to inherit that problem. — kwami (talk) 14:16, 31 August 2024 (UTC)
- It is your browser that interprets the
lang="my"
attribute. If it does not interpret the attribute correctly, you will get rubbish for a rendering. Here I have switched the language tags (don't do this in mainspace):- မြန်မာအက္ခရာ ←
<span lang="ja">မြန်မာအက္ခရာ</span>
–lang="my"
switched tolang="ja"
- မြန်မာအက္ခရာ ←
<span lang="ru">မြန်မာအက္ခရာ</span>
–lang="ru"
switched tolang="ru"
- မြန်မာအက္ခရာ ←
- For me, they both render correctly.
- —Trappist the monk (talk) 14:40, 31 August 2024 (UTC)
- Okay, it's my browser then. Bizarre that FF doesn't render 'my' by default. I'll look for overrides. Thanks. — kwami (talk) 15:13, 31 August 2024 (UTC)
- It is your browser that interprets the
- The results of 1 and 2 display correctly (as well as the code of all 5). lang="my" appears to be the problem, and lang-my appears to inherit that problem. — kwami (talk) 14:16, 31 August 2024 (UTC)