Module talk:Lang/data/Archive 1

Please partially revert the last edit to this module, in order to restore the entry for mla: the entry was here so that the language label emitted by {{lang-mla}} matches the title of the article about the language: Tamambo language (ISO 639:mla). The removal of this entry had reinstated the obsolete label "Malo". – Uanfala (talk) 15:35, 1 February 2018 (UTC)

I despair sometimes, I really do. You and I had an edit conflict (you marked your post as such) so I know that you were aware of what I had just written yet you said nothing that suggested opposition to what I described as the solution to the mla issue. In your post you did not use the word 'Malo'.

It is not clear to me that the mla associated name is obsolete; Malo is associated with mla at the IANA language-subtag-registry file and at SIL International which are the go-to international standards from which the {{lang-??}} templates draw their label names.

Our Tamambo language article appears to suggest that Malo is a synonym for Tamambo and/or that Malo language is a redirect to Tamambo language (in fact, Malo language started out as a redirect to Tamambo language).

So, instead of voicing your concerns as you should have, you remained mute until after the changes that I suggested had been made and then reverted everything. Sigh.

—Trappist the monk (talk) 17:13, 1 February 2018 (UTC)

Sorry, I thought it was obvious from my comment that it would be a bad idea to make these changes. I didn't imagine you would proceed to make them. – Uanfala (talk) 19:51, 1 February 2018 (UTC)

I request grk-x-proto for Proto-Greek and sla-x-proto for Proto-Slavic, from grk and sla, the codes for the Hellenic and Slavic language families. I've already used these codes in Epenthesis despite the error messages because they are consistent with the other private-use proto-language codes. — Eru·tuon 19:55, 5 July 2018 (UTC)

done

—Trappist the monk (talk) 09:56, 6 July 2018 (UTC)

ira-x-proto (Proto-Indo-Iranian) needed in Assimilation (phonology). itc-x-proto (Proto-Italic), iir-x-proto (Proto-Iranian), inc-x-proto (Proto-Indo-Aryan) might come up at some point too. I wonder if there are any established irregular codes for these. — Eru·tuon 00:42, 8 July 2018 (UTC)

Added ira-x-proto. Let us not clutter the data set with unused codes merely on the speculation that someday they might be needed.

—Trappist the monk (talk) 10:47, 8 July 2018 (UTC)

Well, okay. But I can spot Proto-Italic text in the wild (see Proto-Italic language), so please add it. — Eru·tuon 16:42, 8 July 2018 (UTC)

There're also a few bits of Proto-Iranian in Proto-Indo-Iranian language. — Eru·tuon 16:46, 8 July 2018 (UTC)

Gah. I got the codes for the Indo-Iranian (iir) and Iranian (ira) families reversed. So Proto-Indo-Iranian should be iir-x-proto and Proto-Iranian ira-x-proto. — Eru·tuon 16:58, 8 July 2018 (UTC)

ira-x-proto → iir-x-proto fixed; added itc-x-proto.

—Trappist the monk (talk) 17:17, 8 July 2018 (UTC)

Thanks. ira-x-proto (Proto-Iranian) is needed, because it's used in Proto-Indo-Iranian language. — Eru·tuon 17:30, 8 July 2018 (UTC)

Is there a way to have lij point to Ligurian (Romance language) instead than to the disambiguation page Ligurian language?   イヴァンスクルージ九十八_（会話）  19:59, 12 December 2018 (UTC)

Discussion about that topic started here and migrated to here. Please don't start yet another conversation about that same topic on yet another page.

—Trappist the monk (talk) 20:12, 12 December 2018 (UTC)

@Trappist the monk: I am sorry, I had no idea.   イヴァンスクルージ九十八_（会話）  21:31, 12 December 2018 (UTC)

Please add the code en-IN for Indian English; per our article on that dialect, the IETF language tag should be "en-in"

Add

	["en-in"] = {"Indian English"},

-- 65.94.170.207 (talk) 22:51, 29 April 2020 (UTC)

  Done. P.I. Ellsworth  ed. ^put'r there 00:08, 30 April 2020 (UTC)

In the documentation of Template:Lang-de-CH, "{{langx|de-CH}} identifies Swiss German text" should read "{{langx|de-CH}} identifies Swiss Standard German text", but editing is locked on the templates and modules that generate this output. To clarify, Swiss German is a variety of Alemannic (gsw), whereas Swiss Standard German is German (de) as spoken in Switzerland. Iketsi (talk) 03:14, 22 June 2020 (UTC)

  Done. – Jonesey95 (talk) 15:40, 22 June 2020 (UTC)

I added ["pfl"] = {"Palatine German"} to Module:Lang/data/sandbox; I'm not sure how to preview it with User:OwenBlacker/sandbox, as it's Module:Lang that's directly transcluded. If I've done something wrong, I'd be grateful if someone could point out how I should test with my sandbox page.

Once the edit is made, then articles such as Zweibrücken can be edited to use {{lang-pfl}}, like with other languages. — OwenBlacker (he/him; Talk; please {{ping}} me in replies) 16:49, 26 March 2020 (UTC)

To demonstrate that a change to Module:Lang/data/sandbox, it needs to be used by something. In this case, the likely candidate is Module:lang/sandbox. As the lang module is organized right now, Module:lang/data (~/sandbox) is loaded pretty-much first-thing. That way of doing things precludes choosing the live v. sandbox data progamatically because the data are loaded before the module can extract the live v. sandbox information from the frame object. For the nonce, I have hard-coded ~lang/sandbox to use ~/data/sandbox so:

{{lang/sandbox|pfl|pfl text via the sandbox}} → pfl text via the sandbox

<span title="Palatine German-language text"><i lang="pfl">pfl text via the sandbox</i></span>

To test that with {{lang-pfl}}, that template must {{#invoke:}} lang/sandbox

—Trappist the monk (talk) 17:36, 26 March 2020 (UTC)

  Not done for now: Please feel free to reactivate when testing etc. are complete. Izno (talk) 22:31, 22 April 2020 (UTC)

Reactivating this request and adding to it. User:OwenBlacker/sandbox currently contains examples showing "before" (Module:Lang/data) and "after" (Module:Lang/data/sandbox) versions to demonstrate the addition of ["pfl"] = {"Palatine German"}, (diff, currently line 57) and ["xgf"] = {"Tongva"}, (diff, currently line 69) to Module:Lang/data/sandbox.

Could those 2 changes please be integrated into Module:Lang/data? Thanks, and sorry for the delay!

Edited to add: Please note that my 2 edits are not the only edits currently in the sandbox. If you want to take only my edits, that could currently be achieved by copy/pasting from my added line 57 to the blank line 70 — OwenBlacker (he/him; Talk; please {{ping}} me in replies) 18:46, 21 July 2020 (UTC)

done

—Trappist the monk (talk) 19:38, 21 July 2020 (UTC)

The Hunterian transliteration scheme is the most widely-used scheme in the Indian subcontinent to transliterate Indic texts, so it should be added as an option. Perhaps have the code be Hunt? Cheers. Getsnoopy (talk) 17:46, 13 August 2020 (UTC)

{{Transliteration|hi|hunterian|maiṅ apne saṃbaṅdhī se kārk͟hāne meṅ milā aur usne mujhe chāy pilāī}}.

maiṅ apne saṃbaṅdhī se kārk͟hāne meṅ milā aur usne mujhe chāy pilāī.

—Trappist the monk (talk) 18:53, 13 August 2020 (UTC)

The full list of languages and scripts in ISO 15919 are not listed in this file. Add the following to the list of "ISO 15919 Indic" titles in translit_title_table to complete it:

Languages: awa, bho, bra, doi, gon, kok, ks, mag, mai, ne, new, or, pa, raj, sat, sd, si, tcy

Scripts: Gujr, Guru, Knda, Mlym, Orya, Sinh, Taml, Telu

Getsnoopy (talk) 13:07, 27 March 2019 (UTC)

  Not done: please make your requested changes to the module's sandbox first; see WP:TESTCASES. -- /Alex/₂₁ 12:12, 29 March 2019 (UTC)

@Alex 21: Done. Could you check now? Thanks. Getsnoopy (talk) 00:18, 7 September 2020 (UTC)

Getsnoopy,   Done (Better late than never, ey?) -- /Alex/₂₁ 00:25, 7 September 2020 (UTC)

For Ukrainian in en.Wikipedia we use the Ukrainian National system of romanization (see WP:UKR and Romanization of Ukrainian). This system has been adopted by both BGN/PCGN and UNGEGN, however those names are often associated with superseded standards, i.e., BGN/PCGN’s own 1965 system.

We also use the variously-named international, scientific, scholarly, academic, or linguistic transliteration system for linguistics articles, for Russian, Ukrainian, Old Church Slavonic, and other languages (see scientific transliteration of Cyrillic). I’d like to call this translit-std="linguistic", or translit-std="ling-cyr", as a reminder to Wikipedia editors of its application.

I would add the following codes to the translit_title_table. I am glad to do it myself, but I’d like to get opinions first since I’m not familiar with the code.

	['ukrainian'] = {
		['default'] = 'Ukrainian National system of romanization',
		},

	['scientific'] = {
		['default'] = 'scientific transliteration',
		},

 —Michael Z. 22:00, 5 January 2021 (UTC)

having thought it over, I’ve modified the proposal above. Scientific transliteration is the most common name, and it refers to romanizations for other scripts than only Cyrillic. —Michael Z. 01:17, 10 January 2021 (UTC)

  Done —Michael Z. 23:11, 20 January 2021 (UTC)

Please, add Medieval Latin (lat-med) and Early Modern English (emen). Est. 2021 (talk · contribs) 03:00, 7 February 2021 (UTC)

No. lat-med is not a valid IETF language tag. For Latin, the proper code is la. med is not an IANA registered extlang. You might want to instead create a private-use IETF tag la-x-medieval for Medieval Latin.

emen is an ISO 639-6 code. ISO 639-6 has been withdrawn so none of its codes are reflected in the IANA language-subtag-registry file. Module:Lang/data has en-emodeng for Early Modern English.

—Trappist the monk (talk) 12:29, 7 February 2021 (UTC)

@Trappist the monk: I would like to standardise the {{lang-lat-med}} template, adding the same code/parameters we can use in {{lang-la}}, {{lang-it}}, etc. Est. 2021 (talk · contribs) 15:43, 7 February 2021 (UTC)

I'm not really clear on what it is that you want. Even though it uses {{lang}}, {{lang-lat-med}} is not a {{lang-??}} template because lat-med is not a valid IETF language tag. You might create {{lang-la-x-medieval}} as a replacement. Or, just continue to use {{lang-lat-med}} if it does what it is that you want done.

—Trappist the monk (talk) 16:34, 7 February 2021 (UTC)

Couldn't we just shorten it to la-med and make it work like en-emodeng etc.? Est. 2021 (talk · contribs) 16:09, 7 February 2021 (UTC)

No. med is not a valid IETF extlang subtag. emodeng is a valid IETF variant subtag and as such is listed in the IANA language-subtag-registry file.

—Trappist the monk (talk) 16:34, 7 February 2021 (UTC)

@Trappist the monk: I need the template to show the lit parameter from {{lang-??}} templates. If I create {{lang-la-x-medieval}} using this code, will it work? Could I redirect {{lang-lat-med}} there? Est. 2021 (talk · contribs) 17:44, 7 February 2021 (UTC)

If you create that template we can add la-x-medieval to the module after which the template should work.

—Trappist the monk (talk) 19:10, 7 February 2021 (UTC)

@Trappist the monk: Yes, add it please. Est. 2021 (talk · contribs) 20:18, 7 February 2021 (UTC)

PS. Should I add the following text to the {{lang-la-x-medieval}} template documentation?

It links by default to the Medieval Latin language article, but in the HTML metadata classifies the content simply as Latin (i.e., Classic Latin) because there is no ISO language code for Medieval Latin

Est. 2021 (talk · contribs) 20:25, 7 February 2021 (UTC)

Please map luo → Dholuo language to fix Template:Lang-luo, per sandbox. Certes (talk) 13:33, 7 April 2021 (UTC)

done

—Trappist the monk (talk) 14:02, 7 April 2021 (UTC)

Trappist the monk: Thanks. Since my request, you updated Module:Language/data/iana languages which may make this edit unnecessary, but it should do no harm. Certes (talk) 14:31, 7 April 2021 (UTC)

• For the name: Central Bicolano → Central Bikol
• For the link: Central Bikol → Central Bikol language

—hueman1 (talk • contributions) 12:13, 11 May 2021 (UTC)

{{lang|fn=name_from_tag|bcl}} → Central Bikol

{{lang|fn=lang_xx_italic|code=bcl|text=text}} → Central Bikol: text

{{lang|bcl|text}} → text

—Trappist the monk (talk) 13:34, 11 May 2021 (UTC)

@Trappist the monk: Thank you! Following this change, Category:Articles containing Central Bicolano-language text needs to be moved to Category:Articles containing Central Bikol-language text, should I start a CfD? —hueman1 (talk • contributions) 14:02, 11 May 2021 (UTC)

Luxembourgish language → Luxembourgish. —hueman1 (talk • contributions) 14:01, 20 June 2021 (UTC)

  Not done

No reason given for this request. Neither 'Luxembourgish language' nor 'Luxembourgish' appear in Module:Lang/data so nothing to change.

—Trappist the monk (talk) 14:08, 20 June 2021 (UTC)

@Trappist the monk: Weird. Typing {{native name|lb|...}} gives you a link to the Luxembourgish language (like this one: ... (Luxembourgish)). Where on Wikipedia could that link be? —hueman1 (talk • contributions) 14:33, 20 June 2021 (UTC)

{{Native name}} is a wrapper template around {{lang}}. {{lang}} {{#invoke:}}s Module:Lang. Module:lang creates the link to Luxembourgish language from the lb definition in Module:Language/data/iana languages. Module:Lang almost always creates [[<language name> language|<language name>]] links; see lines 1143–1149. Many upon many language articles are named <language name> language. Not so many are simply named <language name>. Redirects are free; Module:Lang avoids the need to test each link by consistently using the same form for most links so the Luxembourgish language redirect-link is to be expected.

Collective languages always include the 'languages' text in their name; for example alg:

{{lang|fn=lang_xx_italic|code=alg|text=text}}

[[Algonquian languages]]: <i lang="alg">text</i>[[Category:Pages using Lang-xx templates]]

Algonquian languages: text

There are a few en.wiki articles that doe not fit into the above link styles. Those article titles are listed at Module:Lang/data at lines 267–281; for example xlg:

{{lang|fn=lang_xx_italic|code=xlg|text=text}}

[[Ligurian language (ancient)|Ligurian]]: <i lang="xlg">text</i>[[Category:Pages using Lang-xx templates]]

Ligurian: text

—Trappist the monk (talk) 15:37, 20 June 2021 (UTC)

Please add before line 248:

	["alg-x-proto"] = "Proto-Algonquian",						-- alg in IANA is Algonquian languages

I've not added it to the sandbox, as there are pending changes (which appear to revert Trappist the monk's changes from 1 January 2022), but the format is identical to the current line 248, so the risk is minimal. I've already made an edit to Tomahawk#Etymology using this code, given it is consistent with our other proto-language IETF private use tags. — OwenBlacker (he/him; Talk; please {{ping}} me in replies) 11:31, 6 January 2022 (UTC)

Not for me, apparently. So, do I request the private-use tags here, or is there some other method of doing this?  Tewdar  (talk) 17:39, 19 January 2022 (UTC)

Okay, so how about, for starters, kw-x-swfcor for the Standard Written Form?  Tewdar  (talk) 18:12, 19 January 2022 (UTC)

And, kw-x-latecor for the Cornish of 1600-1800ish?  Tewdar  (talk) 18:13, 19 January 2022 (UTC)

And finally, kw-x-modcor for revived late Cornish? Thanks! 😁  Tewdar  (talk) 18:15, 19 January 2022 (UTC)

Please note that the Standard Written Form and Kernowek Standard are definitely not the same thing and should not be confused, even though they both have the word 'standard' in their names.  Tewdar  (talk) 18:37, 19 January 2022 (UTC)

Any action with regard to the above should be deferred until the discussion at Talk:Cornish phonology § lang tags discussion is concluded.

—Trappist the monk (talk) 22:26, 19 January 2022 (UTC)

Good idea. In the meantime, I'm merging traditional middle and late Cornish into the 'cnx' tag, tagging the various revivalist orthographies with the available subtags, and tagging stuff that doesn't have a tag yet with 'kw'. You really think there's going to be a discussion? 🤔  Tewdar  (talk) 11:17, 20 January 2022 (UTC)

Perhaps "bry-x-proto"?They use "cel-bry-pro" over at Wiktionary I believe. Tewdar (talk) 15:37, 5 December 2021 (UTC)

Not by that private-use tag. bry is an ISO 639-3 tag assigned to Burui language which is not one of the Celtic languages.

We might do something like cel-x-britpro or cel-x-bryproto or some-such. The trailing subtag of a private-use tag is one-to-eight characters long; Module:Lang will only accept one such subtag. If there is a wikiproject associated with Common Brittonic you might wish to discuss with them before making a determination about a private-use tag here.

—Trappist the monk (talk) 16:09, 5 December 2021 (UTC)

cel-x-bryproto would be fine. There is no Common Brittonic Wikiproject as far as I know, and WikiProject Celts is inactive. I could ask at WikiProject Languages if you like, but I think cel-x-bryproto would be fine... Tewdar (talk) 18:13, 5 December 2021 (UTC)

I made the proposal over at WikiProject Languages and linked to the discussion here. Thanks. Tewdar (talk) 18:20, 5 December 2021 (UTC)

link to that discussion

—Trappist the monk (talk) 18:26, 5 December 2021 (UTC)

(edit conflict)

The first subtag must be a valid ISO 639 language tag. None of bryth, britt, britcel, brycel are valid ISO 639 language tags.

I think that you should ask. Likely you won't get much of an answer, but better to ask than to squabble later.

—Trappist the monk (talk) 18:23, 5 December 2021 (UTC)

Yes, sorry, I realized my mistake there. Tewdar (talk) 18:29, 5 December 2021 (UTC)

Also posted on the Common Brittonic talk page. Tewdar (talk) 18:26, 5 December 2021 (UTC)

link to that discussion — Preceding unsigned comment added by Tewdar (talk • contribs) 18:29, 5 December 2021 (UTC)

• Hello again! 😁 Nobody gives a tuppenny, erm, chew! Can I have a tag now please, I promise to use it almost immediately... cel-x-bryproto is fine with me, if we can't have cel-bry-pro...  Tewdar (talk) 20:58, 26 January 2022 (UTC)

Using {{langx|lut|something}} results in a link to "Lushootseed language", which is a redirect to "Lushootseed". To fix this, seems like the article_name dictionary should be augmented to include this exception. Shall I make the change? -- Mikeblas (talk) 01:44, 30 January 2022 (UTC)

Fixed your html markup.

No fix needed. All language links created by Module:Lang have the form [[<language-name> language|<language-name]] except for collective language links which are [[<language-name> languages]]. The articles listed in the article_name table are special cases. Were all language articles named as Lushootseed is named, then we wouldn't need piped links through redirects but many upon many are named like French language is named. And redirects are free.

—Trappist the monk (talk) 02:14, 30 January 2022 (UTC)

It seems like en-GB-oxendict does not have an alias at the moment, so the tooltip just shows as "English-language text". Could someone please add "Oxford English" as the override for that code? Thanks. Getsnoopy (talk) 23:52, 21 March 2022 (UTC)

Replace line 177

["arc"] = "Aramaic", -- Official Aramaic (700-300 BCE), Imperial Aramaic (700-300 BCE);

with

["arc"] = "Imperial Aramaic", -- Official Aramaic (700-300 BCE), Imperial Aramaic (700-300 BCE);

since as the comment says, the meaning of the ISO 639-3 code arc is Imperial Aramaic and not the whole language family. S.K. (talk) 08:09, 25 September 2022 (UTC)

Is there a consensus discussion somewhere that supports this change? Approximately 200 articles use {{lang-arc}} and {{lang|arc|...}}; see Category:Articles containing Aramaic-language text (which will need to be moved via WP:CFD).

—Trappist the monk (talk) 11:27, 25 September 2022 (UTC)

Where should this discussion happen? I′d thought here. The ISO 639-3 standard is rather clear, it disambiguated the name of the code in 2007 from Aramaic to the current name(s), as can be seen in the ISO link above. --S.K. (talk) 13:05, 25 September 2022 (UTC)

Started a discussion at Template talk:Lang-arc#Change language link to Imperial Aramaic. S.K. (talk) 13:46, 25 September 2022 (UTC)

Any of the language or linguistics projects? I don't know. This module has only 15 watchers, {{lang-arc}} has 3 watchers; neither are a great place to establish a broad consensus.

Alas, there are editors who do not believe that en.wiki should always use the standardized language names from IANA or ISO 639-1, -2, -3; that belief is the raison d'être for this module.

The ISO 639-3 custodian seems a bit schizophrenic about the 'proper' name for arc. The title of their definition page is: Official Aramaic (700-300 BCE) [arc]. Under the Language Name(s) header, they have: Imperial Aramaic (700-300 BCE), Official Aramaic (700-300 BCE). Under Code Change History: New Value they have Official Aramaic (700 - 300 BCE); Imperial Aramaic (700 - 300 BCE).

Module:Lang uses the IANA language-subtag-registry file as the source language tags and language names. The IANA record for arc is:

%%
Type: language
Subtag: arc
Description: Official Aramaic (700-300 BCE)
Description: Imperial Aramaic (700-300 BCE)
Added: 2005-10-16
%%

When two or more names are defined for a language tag in the IANA data as is the case here, Module:Lang uses the first name unless overridden by a tag/name pair in Module:Lang/data.

MediaWiki, on the other hand, may be where the arc → Aramaic definition in Module:Lang/data comes from: {{#language:arc|en}} → Aramaic. Changing MediaWiki is likely an uphill struggle.

If you are needing to get the language name from the ISO 639-3 language tag, you can use

{{ISO 639 name|fn=iso_639_code_3_to_name|arc}} → Imperial Aramaic

ISO 639-2 reverses the name order:

{{ISO 639 name|fn=iso_639_code_2_to_name|arc}} → Official Aramaic

—Trappist the monk (talk) 14:35, 25 September 2022 (UTC)

My understanding is that linguist are not decided on which of the two names they prefer. This is probably why ISO lists both. I'd be happy with either, the main point for me is that the link in {{lang-arc}} should go to the "correct" article, and this would be true with either name. I suggested Imperial Aramaic only because that’s how the Wikipedia article is named. But with Aramaic it goes to the "wrong" article, which is about the whole language group. S.K. (talk) 15:24, 25 September 2022 (UTC)

You still ought to at least notify WP:LING and WP:LANG, which have 325 and 279 watchers. You can hold the discussion here if you'd like or at one of the project pages. Multiple discussions in multiple venues is discouraged per WP:MULTI.

—Trappist the monk (talk) 16:56, 25 September 2022 (UTC)

Notified both. S.K. (talk) 22:16, 25 September 2022 (UTC)

Since there was no reaction, neither at Template talk:Lang-arc#Change language link to Imperial Aramaic nor here besides the requests for participation both at WP:LING and WP:LANG, I would treat this as "no objection". Therefore I’d like to ask again, if the change can be made or what other alternatives I should explore. --S.K. (talk) 09:02, 5 October 2022 (UTC)

Ok, I've made the change. You are responsible for getting Category:Articles containing Aramaic-language text moved to Category:Articles containing Imperial Aramaic (700-300 BCE)-language text. Someone will likely notice that redlink and create the category in which case need to worry about deletion of Articles containing Aramaic-language text ... You are also responsible for making sure that usage of {{lang|arc|...}} and {{lang-arc|...}} in article space is correct.

—Trappist the monk (talk) 13:11, 5 October 2022 (UTC)

Thank you!

Nominated category for renaming at Wikipedia:Categories for discussion/Log/2022 October 6. S.K. (talk) 03:16, 6 October 2022 (UTC)

I would like to have ISO 15919 Indic used as the default transliteration scheme for pnb, hno, and skr. pnb represents Punjabi (also pa/pnb) in the Shahmukhi script. hno is Hindko, and skr is Siraiki, two very closely related languages. Although their writing systems differ, the reason to include them here is for congruence with pa (Punjabi Gurmukhi), and the fact that ISO 15919 includes provisions for phonemes found in these Indic languages which are not common elsewhere. (Such as ḷ.) عُثمان (talk) 17:55, 10 November 2022 (UTC)

According to our articles, Punjabi (pnb) is written using Shahmukhi script, Northern Hindko (hno) is written with Shahmukhi script, and Saraiki (skr) is written using the Saraiki alphabet. None of these languages and their associated scripts are named in our ISO 15919 article. If these languages and script are not supported by ISO 15919, Module:Lang/data should not assert that they are.

—Trappist the monk (talk) 23:54, 10 November 2022 (UTC)

The Nastaliq column includes the alphabet used for these languages on the ISO 15919 column, naming all the languages that uses these letters would take up too much space. عُثمان (talk) 19:15, 14 November 2022 (UTC)

@Trappist the monk (for example) ݨ is a letter used in Saraiki, Hindko, and Punjabi which appears in the Nastaliq column. ڃ is used in Sindhi. ࣇ is used in Punjabi. Besides these, all the other letters there are used in all of those languages in addition to Urdu.

The main thing missing is the transcriptions for plosive consonants: ݙ ڄ ٻ ڳ. Of these, ݙ is Saraiki only, and the other three are shared by Saraiki and Sindhi. The separate page Wikipedia:Indic transliteration does include a section for these, but I want to verify the ISO transcription when I have time before merging those details to the other table. عُثمان (talk) 19:25, 14 November 2022 (UTC)

I have added hno, pnb, and skr as language tags associated with ISO 15919.

—Trappist the monk (talk) 20:05, 14 November 2022 (UTC)

Thank you! عُثمان (talk) 12:43, 29 November 2022 (UTC)

The currrent overrides for pa and pnb should also be changed to Punjabi (Gurmukhi) and Punjabi (Shahmukhi) respectively. The current labels are misleading, as the first has no qualifier to say what is different from pnb, and both codes may be used to transcribe western and eastern dialects alike. (In fact, I am currently transcribing Pothohari Kosh, a western Punjabi dictionary written entitely in Gurmukhi, the "eastern" script.) -عُثمان (talk) 18:02, 10 November 2022 (UTC)

I seem to recall an extensive conversation with another editor about pa, pan, pnb which, if memory serves, resulted in tag/name assignment: pnb → Punjabi (Western). I was unable to find that discussion in the archives of this talk page nor in the archives of Template talk:Lang. Without a more broad consensus than your request, I am unwilling to change the current assignment.

—Trappist the monk (talk) 23:54, 10 November 2022 (UTC)

I am curious what that editor's reasoning was. For what it's worth you won't find mention of pnb as "Western Punjabi" (لہندی پنجابی) on pnb.wikipedia.org عُثمان (talk) 19:17, 14 November 2022 (UTC)

'Western Panjabi' is the name that the ISO 639-3 custodian uses for pnb; see https://iso639-3.sil.org/code/pnb. There is a 2019 change request pending; see https://iso639-3.sil.org/request/2020-019.

—Trappist the monk (talk) 20:17, 14 November 2022 (UTC)

Could this 2018 thread have been the discussion you had in mind? Still, I agree that the use of the qualifier "Western" is confusing here. – Uanfala (talk) 20:15, 17 November 2022 (UTC)

I don't think it was that discussion but perhaps it was this discussion.

—Trappist the monk (talk) 00:30, 18 November 2022 (UTC)

Yep, the other one. Sorry for the mistake. – Uanfala (talk) 00:50, 18 November 2022 (UTC)

{{Lang-snq}} has been created and links to Sangu language, but that is a dab: the article about the language with code snq is at Sangu language (Gabon). Please add

	["snq"] = "Sangu language (Gabon)",											-- Sangu (Gabon)

into the Lua table article_name at Module:Lang/data#L-337, as done in Module:Lang/data/sandbox. Test case: lead of Gabon. Courtesy ping: Thiscouldbeauser. Thanks, Certes (talk) 11:01, 19 December 2022 (UTC)

Yes it would be good if this was added. Thiscouldbeauser (talk) 11:40, 19 December 2022 (UTC)

I've added a new ISO 639-1 / IETF override for lij-MC = Monégasque dialect, having also created {{lang-lij-MC}}, used for Monaco in Civil union#Europe. —  OwenBlacker (he/him; Talk; please {{ping}} me in replies) 14:23, 31 December 2022 (UTC)

Added as ["lij-mc"] = "Monégasque", so that Module:Lang uses the existing redirect Monégasque language and is otherwise consistent with the rest of the {{lang-??}} templates.

As an aside and for future reference, ISO 639-1 language subtags are always two characters; subtag lij is ISO 639-3 so your addition should have been placed in the < ISO_639-2, -3, -5 > section.

—Trappist the monk (talk) 15:31, 31 December 2022 (UTC)

Please insert a new line after line 171. On the new line that you have created, please insert ["ug"] = "Uyghur", -- Uyghyr. This will bring the name of the language that is linked to in this template in sync with the Uyghur language article's title, which is titled with the most common spelling of the language's name. I was spurred to make this request based off a recent series of edits at Uyghurs, and I am pinging the two involved editors (Yue and Comotti) in case they would like to comment. — Red-tailed hawk _(nest) 21:57, 8 March 2023 (UTC)

  Completed. P.I. Ellsworth , ed. ^{put'er there} 14:36, 9 March 2023 (UTC)

@Paine Ellsworth: Don't forget to fix the categorization...

Category:Articles containing Uyghur-language text

—Trappist the monk (talk) 14:43, 9 March 2023 (UTC)

Thank you, Trappist the monk! In process with Cat-a-lot. P.I. Ellsworth , ed. ^{put'er there} 15:16, 9 March 2023 (UTC)

{{Lang-toi}} has been created and links to Tonga language, but that is a dab: the article about the language with code toi is at Tonga language (Zambia and Zimbabwe). Please add

	["toi"] = "Tonga language (Zambia and Zimbabwe)",                           -- dab

into the Lua table override at Module:Lang/data#L-224, as done in Module:Lang/data/sandbox. Test case: lead of Zambia.

Thanks! — OwenBlacker (he/him; Talk) 12:18, 3 October 2023 (UTC)

Done but not that way; please test before suggesting changes that any editor with the necessary permissions can make.

—Trappist the monk (talk) 13:12, 3 October 2023 (UTC)

Language code nl-BE is currently written out as "Flemish". However, the name of that standard language used in northern Belgium, is Dutch (in Dutch, "Nederlands".), exactly the same as the standard language of The Netherlands. Flemish refers to a group of dialects spoken informally, and sometimes is shorthand for "Belgian Dutch", i.e. standard Dutch as spoken in Belgium. But that is incorrect. Source 1 Source 2 I would move to change the description "Flemish" to "Belgian Dutch". Keizers (talk) 14:20, 26 January 2024 (UTC) Keizers (talk) 14:20, 26 January 2024 (UTC)

Module:Lang/data uses Flemish as the definition of nl-BE because that is how MediaWiki defines that language tag:

{{#language:nl-BE|en}} → Flemish

I do not know why MediaWiki have chosen Flemish over Belgian Dutch.

Persuade MediaWiki to change and Module:Lang/data will follow. To do that, create a task at mw:Phabricator. Alternately, develop a consensus at en.wiki to change and Module:Lang/data will follow. This talk page is not the place to develop an en.wiki consensus. That is better done at an appropriate wikiproject; perhaps one of WP:LANGUAGES, WP:LINGUISTICS, WP:BELGIUM.

—Trappist the monk (talk) 15:06, 26 January 2024 (UTC)

Add an article name override for code 'vwa', so it targets Wa language instead of the disambiguation page Awa. Xeroctic (talk) 14:55, 27 January 2024 (UTC)

{{lang|fn=name_from_tag|vwa|link=yes}} → Awa

—Trappist the monk (talk) 15:19, 27 January 2024 (UTC)

Two things:

1. Please add cmn (the specific language code for Mandarin Chinese) to the subtable iso with the value 'ISO 7098 Chinese', since ISO 7098 is designed for the transcription of Mandarin Chinese.
2. Please remove pny (the code for the Pinyin language) from the same table. This refers to a completely unrelated language spoken in Cameroon, and has nothing to do with the Pinyin system used for transcribing Mandarin Chinese.

Thanks. Theknightwho (talk) 19:51, 12 February 2024 (UTC)

Thanks for that. pny as a transliteration tag has been misused since this 15 April 2007 edit to {{transl}} (as it was then known).

Just to be really clear about what it is that you want, you want to change line 512 from:

['pny'] = 'ISO 7098 Chinese',

to:

['cmn'] = 'ISO 7098 Chinese',

Correct?

—Trappist the monk (talk) 20:12, 12 February 2024 (UTC)

This search finds 15 or so articles that use {{lang}} with the pny language tag. I suspect that most or all of these are incorrectly using pny.

The correct IETF language tags to markup pinyon romanized text are zh-latn-pinyin (Chinese) and bo-latn-pinyin (Standard Tibetan). The pinyin variant subtag is not allowed with cmn.

—Trappist the monk (talk) 20:25, 12 February 2024 (UTC)

@Trappist the monk Yes, that change would be ideal. I've replied to your other point on Module talk:Language/data/iana variants. Theknightwho (talk) 23:06, 12 February 2024 (UTC)

the link for the lij-mc code, which is implemented at {{lang-lij-MC}} and displays as “Monégasque”, should be the existing Monégasque dialect article rather than Ligurian (Romance language) as it is now. ~ IvanScrooge98 (talk) 19:10, 25 June 2024 (UTC)

I guess for practical reasons I’ll tag Trappist the monk (talk · contribs) since as I could see they are the usual contributor to this module. :) ~ IvanScrooge98 (talk) 19:15, 25 June 2024 (UTC)

Add Yale romanization of Korean to the translit_title_table; the system is the standard for studying the linguistics of Korean. I'm not sure what a good abbreviation for it is; note that other Yale romanizations exist. Perhaps "yaleko"?

So this code would be placed below the wehr entry:

	['yaleko'] = {
		['default'] = 'Yale romanization of Korean',
		},

Maybe the default value should alternatively be "Yale transliteration of Korean", since other entries seem to use "transliteration"? 104.232.119.107 (talk) 01:26, 7 June 2024 (UTC)

  Done * Pppery * _{it has begun...} 02:07, 9 July 2024 (UTC)

Change the language rendered by the tag akk-x-latbabyl from "Late Babylonian" to "Late Babylonian Akkadian." Antiquistik (talk) 22:52, 7 July 2024 (UTC) Antiquistik (talk) 22:52, 7 July 2024 (UTC)

  Done * Pppery * _{it has begun...} 02:07, 9 July 2024 (UTC)

Description of suggested change: A lot of Hebrew text is transliterated with Society of Biblical Literature Academic scheme. However Lang/data seems to accept for he only ahl (Academy of the Hebrew Language) and iso as parameters. Could you please add Society of Biblical Literature Academic sbl-a and Society of Biblical Literature General sbl-g?

Carnby (talk) 19:19, 16 September 2024 (UTC)

You asked a question of WP:WikiProject Bible only yesterday. I'm not sure that you asked the correct question, but still, I think that you are jumping the gun here. Find out what that project and WP:WikiProject Israel have to say before reopening this request.

this edit request related to this help desk discussion (permalink).

—Trappist the monk (talk) 19:47, 16 September 2024 (UTC) 19:51, 16 September 2024 (UTC)

You're right, I tried to fix the mess I made. Sorry.--Carnby (talk) 21:26, 16 September 2024 (UTC)

Description of suggested change: Render name of bha as Bhariati matching the Wikipedia atticle title Bhariati

عُثمان (talk) 16:50, 27 November 2024 (UTC)

  Completed. P.I. Ellsworth , ed. ^{put'er there} 20:13, 27 November 2024 (UTC)

@Paine Ellsworth: At this edit, you duplicated the language name in both the bha override and in the associated comment. I corrected that with this edit so that the comment lists the language name as specified by the ISO 639 custodian and by the IANA language-subtag-registry file and so that the override entry is more-or-less consistent with other override entries. Please restore my edit.

Also, and I know we've talked about this before, don't forget to update the language categorization when making these kinds of changes to the module.

Category:Articles containing Bhariati-language text

—Trappist the monk (talk) 22:36, 29 November 2024 (UTC)

Oy, so sorry for the error. Corrections have been made, and thank you very much for your patience with me and your civility! P.I. Ellsworth , ed. ^{put'er there} 02:01, 30 November 2024 (UTC)

Description of suggested change:

The following language codes and corresponding should be added as they currently don't appear in many places despite having valid ISO codes: 'bfw' => 'Bonda/Remosam/ବଣ୍ଡା', 'gju' => 'गुज्जरी/Gujari/Gojri', 'hoc' => 'Ho/𑢹𑣉𑣉 𑣎𑣋𑣜', 'kgg' => 'Kusunda/Gemehaq gipan'

Psubhashish (talk) 03:36, 11 December 2024 (UTC)

not done; see Module:Lang/data/iana languages.

Description of suggested change: Ripuarian language is listed as:

["mis-x-ripuar"] = "Ripuarian", -- replaces improper use of ksh in wp_languages

but Ripuarian is not a language isolate. It is a West Germanic language as

["gmw-x-ecg"] = "East Central German".

The family code should be used as a fallback.

Diff:

Error (talk) 19:29, 13 December 2024 (UTC)

Perhaps. The ISO 639-3 custodian has left Ripuarian as an uncoded language so mis (Uncoded languages) is not an appropriate language tag. We use mis in the Ripuarian language article infobox. mis-x-ripuar was the result of a discussion (such as it was) at Talk:Ripuarian language § language naming inconsistencies.

gmw-x-ecg was added as a tweak of the malformed Wiktionary tag gmw-ecg (malformed because ecg is not an IANA registered extlang).

Has there been any discussion about mis-x-ripuar? Probably not. Apparently, mis-x-ripuar only appears in a handful of pages. Do we need to keep it?

—Trappist the monk (talk) 23:16, 13 December 2024 (UTC)

It is uncoded itself, but we know one of the umbrella groupings has a code gmw. So, labelling everything in Ripuarian as gmw is valid and more specific than mis. Just as there is no code for Proto-Indo-European but labelling everything in PIE as ine is valid and more specific than mis, and Lang/data has ine-x-proto for the specific Proto-Indo-European.

All of this, of course, if the private code is going to be used. If not, it is better deleted.

--Error (talk) 01:41, 14 December 2024 (UTC)

That's the question, isn't it? Except for your recent edit, mis-x-ripuar is not in use in mainspace. So: [is] the private code is going to be used?

—Trappist the monk (talk) 14:48, 14 December 2024 (UTC)

Description of suggested change:

Diff:

Northern Moonlight 00:22, 8 January 2025 (UTC)

Why? {{lang-fra-que}} was a wrapper template around this:

{{Language with name|fr-CA|Quebec French|{{{1}}}}}

Replacing {{{1}}} with text:

{{Language with name|fr-CA|Quebec French|text}}

Quebec French: text

When that template was deleted in favor of {{langx}}, ["fr-ca"] = "Quebec French" was added to Module:Lang/data so that there would be no visual changes to articles:

{{langx|fr-CA|text}}

Canadian French: text

Is there discussion somewhere that has achieved consensus to make this change? Link?

—Trappist the monk (talk) 00:43, 8 January 2025 (UTC)

Description of suggested change: Add support for additional proto-languages, under their family's ISO 639-5 codes:

• Proto-Kartvelian: ccs
• Proto-Uralic: urj

I ran into the need to tag these languages while performing language cleanup in Laryngeal theory. I'm certain their articles would benefit from proper tagging, as well.

Diff:

EnronEvolved^{My Talk Page} 22:32, 24 March 2025 (UTC)

{{lang|fn=name_from_tag|link=yes|ccs-x-proto}} → Proto-Kartvelian

{{lang|fn=name_from_tag|link=yes|urj-x-proto}} → Proto-Uralic

—Trappist the monk (talk) 22:57, 24 March 2025 (UTC)

Description of suggested change: Add a language code for a couple more proto-languages, also using their groups' ISO codes:

• Proto-Finno-Ugric: fiu
• Proto-Samic: smi

I hear Proto-Finno-Ugric a debatable proto-language these days, but I'm running into the need to tag it in Laryngeal theory.

Diff:

EnronEvolved^{My Talk Page} 23:32, 24 March 2025 (UTC)

{{lang|fn=name_from_tag|link=yes|fiu-x-proto}} → Proto-Finno-Ugric

{{lang|fn=name_from_tag|link=yes|smi-x-proto}} → Proto-Samic

—Trappist the monk (talk) 00:15, 25 March 2025 (UTC)

@Trappist the monk: I am curious what you think of the Belarusian Latin alphabet AKA "łacinka". The IANA language-subtag-registry for BCP47 does not seem to say much in this regard. For "be", I could only find variants "be-1959acad" and "be-tarask" and that "Cyrl" script should be suppressed with "be" (but not "Latn"). Since some Belarusian seems to actually be/have been originally written in "łacinka" (vs. transliterated for readers of Latn scripted languages) is this better as a variant via something like "be-łacinka" (I am not sure that technically qualifies due to the "ł") or a romanization via something like "be-Latn-łacinka"? And should "łacinka" be added here as a transliteration addition to translit_title_table? What is the best way to markup such text: with a {{lang|be-Latn-łacinka|...}} or {{translit|be|łacinka|...}} or something else? Thank you, —Uzume (talk) 18:23, 31 March 2025 (UTC)

From the point of view Module:Lang, latn script is latn script regardless of alphabet so the general case is {{lang|be-latn|łacinka text}} or {{langx|be-latn|łacinka text}}. When the text is a łacinka-alphabetic romanization of Cyrillic Belarusian, you can use {{transl|be|łacinka}}. So far as I know, łacinka is not a 'romanization standard' so is not supported by {{transl}}.

We do not create variants like 1959acad and tarask because they must first be registered with IANA (there is no external standard from which variant subtags are derived).

If it is important to do so, you might consider creating a separate template like {{lang-sr-Latn}} which hard-codes the language label to link as [[Gaj's Latin alphabet|Serbian]]. I don't think that easter-egging the language label is a good idea so the practice should be discouraged.

Łacinka is a latn script so should be simply marked up as a latn script.

Did I answer your question?

—Trappist the monk (talk) 22:33, 31 March 2025 (UTC)

@Trappist the monk: Yes, pretty much. You seem to be advocating for {{lang|be-Latn|łacinka text}} and {{langx|be-Latn|łacinka text}} and perhaps something like be-Latn-latsinka (where latsinka is BGN/PCGN for лацінка or łacinka) if and when such a beast gets registered with IANA in much the same way as zh-Latn-pinyin is although pinyin seems to also be a romanization here as well. The only downside I see if that there is no real way to differentiate between {{langx|be|лацінка}} (Belarusian: лацінка) and {{langx|be-Latn|łacinka}} (Belarusian: łacinka) except for the fact that the latter is Latin script and thus gets automatically italicized. —Uzume (talk) 03:12, 1 April 2025 (UTC)

More-or-less, though advocating is a bit strong. The purpose of Module:Lang is to provide correct html markup for non-English text in compliance with MOS:FOREIGN. Writing {{langx|be|лацінка}} and {{langx|be-Latn|łacinka}} do that. If ever IANA adopts a latsinka variant subtag, Module:lang will support it.

—Trappist the monk (talk) 13:17, 1 April 2025 (UTC)

Description of suggested change:

Diff:

Introduced in this diff. Northern Moonlight 05:56, 13 April 2025 (UTC)

See also Module_talk:Lang/data/Archive_1#Edit_request_8_January_2025. To address that request for consensus, let me propose that it is pretty self-evident that Quebec French is distinct from Canadian French (whether you call it a subset or a variant), as those articles amply describe. And Canadian French is expressible only as fr-CA in the schema used here. Is there an argument against this change based on a principle that eludes me? I have no objection to a separate question of whether fr-quebec (or something like that) ought to also exist, possibly along with other regional variants. But right now we have the problem that, for instance, Canadian French terms are being indicated as being specifically Quebec French, in error. TheFeds 08:13, 13 April 2025 (UTC)

Pinging Trappist the monk. Firefangledfeathers (talk / contribs) 16:26, 17 April 2025 (UTC)

According to this search, there are about 70 articles that use {{lang}} (~60) / {{langx}} (~10) with fr-CA (also, ~6 templates). If we make this change, someone with sufficient language skills (that person is not me) must go through those articles and make sure that all instances of {{lang(x)|fr-CA|...}} correctly identify the labeled dialect. Because Module:Lang does not have a mechanism to distinguish Québécois from generic Canadian French, we must invent one; perhaps fr-x-quebec → Quebec French.

Volunteers to make sure that the existing {{lang(x)|fr-CA|...}} templates are correctly applied or replaced with {{lang(x)|fr-x-quebec|...}}?

—Trappist the monk (talk) 17:05, 17 April 2025 (UTC)

To probe a little further before selecting a tag, the infobox at Quebec French suggests fr-u-sd-caqc as an IETF tag (added in this edit), though it seems it is not one that happens to correlate directly with ISO 639 & ISO 3166-1 alpha-2. Instead it seems to be using the RFC 6067 extension defined fully in Unicode Technical Standard #35, such that u means use the Unicode extensions, sd means use a geographic subdivision, ca is a semi-redundant way to encode the region information (meaning the same as ISO 639-1 CA), and qc means the subdivision of Quebec.

Conversely, in fr-x-quebec, x is for private use, with quebec being the private use information (i.e. the string that English Wikipedia chooses to use to represent the place where Quebec French is spoken).

For the purposes of this module, how do we feel about either implementing a Unicode extension (u), a private use extension (x), or neither? It looks like Module:Lang/data currently implements a few private use codes and no Unicode codes. TheFeds 19:34, 19 April 2025 (UTC)

I sometimes think of supporting the unicode locale extension for subdivisions. The necessary reference data are available at github. But, do we really need such precision? There are 5400+ defined subdivisions. I would venture to guess that almost none of them are actually required for en.wiki to provide correct html markup for non-English text and to provide appropriate labeling and tooltips for readers. For those languages that do have specific regional needs, like Québécois, private-use tags (with the x singleton) should be sufficient.

I suppose that we could support a very limited subset of the u-sd-xxxx subdivisions on an as-needed basis if it is deemed sufficiently important to do so.

—Trappist the monk (talk) 22:07, 19 April 2025 (UTC)

I'm not really too concerned one way or another about which ought to be preferred (fr-x-quebec vs. fr-u-sd-caqc), but wanted to consider the workflow of an editor attempting to use the {{lang}} and {{langx}} templates, whereby they might consult the mainspace article for guidance as to which tag to use, and find it doesn't work. We could amend the documentation for those templates to indicate that the Unicode extension is not presently supported, and that a private use tag corresponding to the ones at this module page ought to be used instead. Or, we could support some but not all—case-by-case as described. Or we could support them all, but that leads to the question whether a consensus exists to recommend one format or the other when there are now multiple ways of expressing the same concept (e.g. fr-CA = fr-u-sd-ca). Does any one alternative stand out as most elegant and workable? TheFeds 23:05, 20 April 2025 (UTC)

Presently there are 69 private-use tags known to Module:Lang. Most of those appear to refer to archaic (if that's the right word) languages. Some of them don't (lmo-x-berg → Bergamasque, lmo-x-cremish → Cremish, lmo-x-milanese → Milanese; there may be others in that list. Of those three, two have unicode IETF tags in their article infoboxen: Bergamasque: lmo-u-sd-itbg and Milanese: lmo-u-sd-itmi. For Cremish, its unicode tag is likely: lmo-u-sd-itcr.

This search suggests that there are about 140 articles that mention a unicode IETF tag. At a quick glance, most of those are for geographically specific living languages though I did find one (gem-u-sd-ua43 → Crimean Gothic) which is probably not a living language. There may be others; I didn't look closely.

On the other hand, this search finds about 1130 articles that use lang templates with private-use tags which suggests that editors are not too confused. But these are mostly used for dead languages so a unicode IETF tag is less likely to appear in a language article infobox (except for gem-u-sd-ua43 and perhaps others).

I guess all of this suggests to me that if we are to adopt unicode IETF tags (as needed), they should be used for living languages only and only for those that are tied to a specific geographical area within the bounds of the larger area specified by the first to characters of the subdivision subtag (it in itbg). For non-living languages, private-use tags should be used.

—Trappist the monk (talk) 13:19, 21 April 2025 (UTC)

After more reading and thinking about the purpose of the Unicode tags, I'm starting to like them less and less. It seems inelegant to have one schema for when the language and region coincide (en-US), one for when the language use boundary is inside of or coincident with a subdivision (en-u-sd-usca for California English) and one for when the language use boundary traverses subdivisions (en-x-midwesternamerican for Midwestern American English, hypothetically).

So I guess my preference has turned into supporting the private use tags. Since fr-quebec is not in the IANA Subtag Registry as a variant tag, use the private use tag fr-x-quebec for English Wikipedia. Then indicate ["fr-x-quebec"] = "Quebec French", -- Related: "fr-u-sd-caqc" as a text search target within the module page, so a user of the Unicode tag can discover its existence (because our private use tags can't be public-facing in article space). And maybe a template documentation clarification along the lines of preferring the non-Unicode tags in {{lang}} and {{langx}}, and template code to add a hidden category if it finds -u-sd- in a tag?

If this sounds worse, I'm still openminded; just trying to state a proposition that works for everyone. TheFeds 19:51, 23 April 2025 (UTC)

I'm good with supporting private-use tags and not supporting unicode tags. Module:Lang already emits an error message and category link when is sees a unicode subdivision tag:

{{lang|en-u-sd-usca|california text}} → [california text] Error: {{Lang}}: unrecognized language tag: en-u-sd-usca (help) – categorization only in main and template name spaces

updated:

{{lang|fn=name_from_tag|fr-CA|link=yes}} → Canadian French

{{lang|fn=name_from_tag|fr-x-quebec|link=yes}} → Quebec French

—Trappist the monk (talk) 21:36, 23 April 2025 (UTC)

Once we make the switch, I can go through the articles manually. Northern Moonlight 01:25, 22 April 2025 (UTC)

It's on you now.

—Trappist the monk (talk) 21:36, 23 April 2025 (UTC)

  I updated most usages that are distinctly fr-QC. Northern Moonlight 05:27, 28 April 2025 (UTC)

Change "Sorani Kurdish" to "Central Kurdish" per the main article title and standard linguistic usage. "Central Kurdish" is more accurate and consistent. Similarly, If it's possible, change "Kurmanji Kurdish" to "Northern Kurdish".  Zemen  (talk) 22:39, 4 May 2025 (UTC)

Sorani Kurdish is a redirect to Central Kurdish so it makes sense to support that part of the edit request. However, Kurmanji Kurdish is an article in its own right so changing it to point to the redirect Northern Kurdish does not make sense.

—Trappist the monk (talk) 23:54, 4 May 2025 (UTC)

Please, these names are local and dialect names, not language group names. Even Central Kurdish wiki is not called Sorani wiki. We're trying to create a consistent format for this mixed variety of the Kurdish language.  Zemen  (talk) 09:46, 5 May 2025 (UTC)

How ckb.wiki chooses to name itself is not relevant to how this module refers to articles at en.wiki. I did write that there is some sense to retargeting ckb to Central Kurdish so we might proceed with that portion of the request.

We're trying to create a consistent format... Who is 'we'? Where are 'we' acting on that?

—Trappist the monk (talk) 17:16, 5 May 2025 (UTC)

Apologies if my earlier statement was unclear. I mentioned ckb again because Central Kurdish is closely related to both Northern Kurdish and Southern Kurdish, forming the three primary interrelated branches of the Kurdish language. Kurdish language is generally classified into three main groups: Northern, Central, and Southern Kurdish; dialects such as Kurmanji, Sorani, and Laki fall under these categories. Since Sorani was updated to Central Kurdish, it makes sense to align the other names with this classification for consistency. Im also in the process of requesting that Kurmanji be moved to Northern Kurdish. When I say "We" I refer to myself and other Wikipedia contributors who have worked on updating the naming standards on the ckb wikipedia. To ensure consistency across Wikimedia projects, similar updates should be made elsewhere.  Zemen  (talk) 17:50, 5 May 2025 (UTC)