Template talk:ISO 639 name
| Template:ISO 639 name is permanently protected from editing as 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. This template does not have a testcases subpage. You can create the testcases subpage here. |
| This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||
| |||||||||||||||
Customize documentation for Template:ISO 639 name link
[edit]Template:ISO 639 name link transcludes the documentation for Template:ISO 639 name, however, it functions differently in that it automatically adds a link. Is there an easy way to resolve this? I mean, can we tailor the documentation to the link template without having to copy-paste the documentation entirely? — W.andrea (talk) 23:39, 29 March 2025 (UTC)
- You might consider doing something like
{{sfn}}does. That template shares its documentation with several Harvard-style short-form reference templates. The common documentation template is{{Harvard citation documentation}}. - So for
{{ISO 639 name}}and{{ISO 639 name link}}, perhaps{{ISO 639 name documentation}}. That template would be called from Template:ISO 639 name link/doc with{{ISO 639 name documentation|link}}. In{{ISO 639 name documentation}}you might have under usage:* {{tnull | ISO 639 name {{{1|}}} | ''ISO code''}}
- which would render:
{{ISO 639 name|ISO code}}– for the unlinked form{{ISO 639 name link|ISO code}}– for the linked form
- Similarly, this would not want to be part of the
{{ISO 639 name link}}documentation:* {{tnull | ISO 639 name | fn{{=}}iso_639 | ''ISO code or language name'' | link{{=}}yes| hide-err{{=}}yes }}
- You might want to write something like:
*{{#if:{{{1|}}}||{{tnull | ISO 639 name | fn{{=}}iso_639 | ''ISO code or language name'' | link{{=}}yes| hide-err{{=}}yes }}}}- (might want to put that at the end of the §Usage section in order to mind the list gap)
- In a like fashion,
{{ISO 639 name documentation}}would be called from Template:ISO 639 name/doc with{{ISO 639 name documentation}}(no positional parameter set). - —Trappist the monk (talk) 00:11, 30 March 2025 (UTC)
bh is deprecated as per Bihari languages, List of ISO 639 language codes and SIL, but still valid as per IANA language-subtag-registry file. --Namoroka (talk) 14:06, 5 October 2025 (UTC)
- Until IANA deprecates
bhand recognizesbihin the subtag registry, there's naught much to be done because browsers and whatnot will still recognizebhbut won't recognizebihso Module:Lang must still recognizebh. - MediaWiki still mislabels
bh:{{#language:bh|en}}→ Bhojpuri
- and does not recognize
bih:{{#language:bih|en}}→ bih
- so cs1|2 must continue to workaround those two tags.
- We might remove
bhfrom Module:ISO 639 name/ISO 639-1 but the data in the module come from the IANA subtag registry sobhwill be removed when IANA deprecates it. - —Trappist the monk (talk) 15:14, 5 October 2025 (UTC)
- Okay, thanks for your reply.--Namoroka (talk) 15:19, 5 October 2025 (UTC)
update request
[edit]Please update Module:ISO 639 name/ISO 639-3 (dep) as per iso-639-3_Retirements.tab.
-- File-Date: 2025-10-15
["dek"] = {"Dek"},
["nte"] = {"Nathembo"},
["yol"] = {"Yola"},
dek Dek D sqm 2024-10-15 nte Nathembo M eko 2024-10-15 yol Yola M enm 2025-10-15
--Namoroka (talk) 08:45, 26 November 2025 (UTC)
{{ISO 639 name|dek}}→ Dek{{ISO 639 name|nte}}→ Nathembo{{ISO 639 name|yol}}→ Yola- —Trappist the monk (talk) 19:51, 26 November 2025 (UTC)
- Thank you!--Namoroka (talk) 06:27, 27 November 2025 (UTC)