Template talk:Native name/Archive 1

Substitution
I imagine that every time a page that transcludes this template is rebuilt, it is unnecessary to also call and  again since the output always stays the same. I tried to understand the help page about substitution but it gave me a headache so I didn't quite get it. If anyone knows how to use the substitution function in such a way that every time a page is rebuilt, this template doesn't call those language templates anymore (but only once at the time it is transcluded) I would be grateful. What I do want to prevent is to substitute this whole template directly (i.e. ... ), so just leave this template transcluded on the page as-is (in the source as ). Styath (talk) 19:33, 27 September 2011 (UTC)

Native name in non-Latin script
While using this template in some articles { {native name|sr-Cyrl|A} } I noticed that I get italicized text while according to Wikipedia:Manual of Style/Text formatting recommends that text in non-Latin scripts (such as Greek, Cyrillic or Chinese) should not be italicized at all—even where this is technically feasible; the difference of script suffices to distinguish it on the page. Can someone make necessary changes so that in this form text is not italicized? Please bear in mind that it can not be just turned of completely for Serbian language (the one that I was using) since it is one of the languages with active digraphia where in this concrete case both Serbian Cyrillic alphabet and Gaj's Latin alphabet are used. I need { {native name|sr-Cyrl|A} } and only this one should be changed. Thank you for your time and especially if you can help me with this. Have a nice day.--MirkoS18 (talk) 00:52, 7 August 2015 (UTC)
 * I just realized how to do it.--MirkoS18 (talk) 10:40, 7 August 2015 (UTC)

italics=off/no doesn't work anymore
Just FYI:

Thayts  •••  19:59, 7 January 2018 (UTC)


 * It does now, apparently. DePiep (talk) 08:33, 5 November 2022 (UTC)

A link to a DAB page
In Sardinia, calls the DAB page Ligurian language rather than Ligurian (Romance language). Could someone who knows their way around the innards of this template fix this problem? Thanks in advance. Narky Blert (talk) 12:42, 8 April 2018 (UTC)

Links to a DAB page
In Mangnai, and Muli Tibetan Autonomous County, and Ulan County, the parameter "bo" generates a link to the DAB page Tibetan language instead of to Standard Tibetan. Thanks in advance if you can solve this problem. Narky Blert (talk) 15:10, 21 August 2018 (UTC)

Another link to a DAB page
In Laigueglia, the parameter "lij" generates a link to the DAB page Ligurian language instead of to Ligurian (Romance language). Thanks in advance if you can solve this problem. Narky Blert (talk) 14:50, 22 September 2018 (UTC)

Support for non-Latin scripts
When writing a language in a less common script (e.g. the Arabic script to write Kyrgyz or Chinese Xiao'erjing), I've used lang and specified "-Arab" so that the correct, more legible font would be chosen. Compare &lrm; قىرعىزچا with  &lrm; قىرعىزچا.

Unfortunately, this doesn't work with this template: &lrm;. Is there a way to fix this problem. Specifically, could the template be changed such that it parse "ky-Arab" correctly? Abjiklɐm (tɐlk) 17:06, 4 September 2015 (UTC)

I've made an edit in the sandbox that adds a  parameter. This allows for a specific, less common script to be used. Examples include the Arabic script for Kyrgyz. This parameter is necessary for the right default font to be chosen. For example,   is more legible and consistent with other Arabic script languages than.

Can the edit be updated on the actual template? Thanks. Abjiklɐm (tɐlk) 15:40, 5 September 2015 (UTC)
 * Yes check.svg Done Mdann52 (talk) 06:46, 6 September 2015 (UTC)

Tracking down a hard-coded name for categories
This template is used eg in the expandable list at the top of the infobox on Indian rupee with the code dgo for Dogri language. However, it somehow generates the category. Now Dogri (individual language) is a redirect to Dogri language but it's obviously not ideal to use it in a category like that. I've looked round but can't figure out where this is hard-coded, as it's obviously separate to the main dgo->Dogri language conversion. The only place I've found with the redirect is User:SyntaxTerror/sandbox but that doesn't seem to lead anywhere. Can anyone help? Le Deluge (talk) 02:25, 24 July 2018 (UTC)

using Module:ISO 639 name
Module:ISO 639 name consolidates all of the ISO 639-1, -2, -3, -5 codes and names into a single data set extracted from the 639 custodians. It has the additional goal of making all of the various templates obsolete. In future, will call this module. In the meantime, I am replacing calls to that template with calls to the module in select templates as a mechanism for evaluating the performance of the module and have done so.

Module:ISO 639 name emits a variety of error messages and when it does, adds the article to which I monitor.

As I think about this, it occurs to me that or its module replacement might not be the best fit for this template. This template already uses which uses Module:Lang. That module has support for IETF language tags which Module ISO 639 name does not (IETF tags are not ISO 639 codes) and has support for those non-standard names that en.wiki has determined to be preferable to the names defined in the ISO and IANA standards.

—Trappist the monk (talk) 13:18, 19 October 2018 (UTC)
 * More than a day later, has accumulated an additional 180ish articles which all use  with an ietf tag.  So, following up on my comment that Module:lang might be a better fit for this template, I tweaked Module:lang/sandbox and have replaced the calls to Module:ISO 639 name with calls into Module:lang/sandbox.  The results being positive, I shall update the live module and this template.
 * Further, this change would remove the need for this template to support script.
 * —Trappist the monk (talk) 12:35, 21 October 2018 (UTC)
 * Done and switched to the live lang module. I have deprecated script in the documentation and will hunt about to fix its uses before removing support from the template.
 * —Trappist the monk (talk) 10:26, 22 October 2018 (UTC)
 * —Trappist the monk (talk) 10:26, 22 October 2018 (UTC)

requested change
See Talk:Alaska. Currently, the Alaska article displays several native names using this template, with the code "ems" rendering as "Pacific Gulf Yupik." Except nobody calls it that, and we have no article by that name, the term redirects to the much more common term for it, the Alutiiq language. Looking at the template code, there is certainly no obvious way to change this, so I guess I'm asking if there is a non-obvious way, and if so, can we go ahead and make this change? Thanks. Beeblebrox (talk) 21:35, 11 February 2021 (UTC)


 * it's in Module:Language/data/iana_languages (ctrl-f for "Pacific Gulf Yupik"). Not really sure on what the content thing is about, or what you wanmt to change it to, but you can just edit that to change it. ProcrastinatingReader (talk) 21:36, 14 February 2021 (UTC)


 * That made me very nervous, but I've made the change, thanks! Beeblebrox (talk) 22:13, 14 February 2021 (UTC)
 * I guess I should ping in to double check if there's not another way he prefers to set the "Preferred-Value" (docs indicate there may be another way, but at a skim it's not clear what that way is), so it doesn't get overriden on next update. ProcrastinatingReader (talk) 22:50, 14 February 2021 (UTC)
 * done.
 * —Trappist the monk (talk) 23:26, 14 February 2021 (UTC)