This is the talk page for discussing improvements to the Lang template.

Add new text under old text. New to Wikipedia? Welcome! Learn to edit; get help. Start a new topic Assume good faith Be polite and avoid personal attacks Be welcoming to newcomers Seek dispute resolution if needed

Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16Auto-archiving period: 4 months

	This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:
Languages This template is within the scope of WikiProject Languages, a collaborative effort to improve the coverage of languages on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.LanguagesWikipedia:WikiProject LanguagesTemplate:WikiProject Languageslanguage

Template:Lang is indefinitely 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. 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 centralize discussions and keep related topics together, the talk pages for all help pages, categories, MediaWiki messages and templates related to Template:Lang redirect here. Centralised discussions Template talk:Langx Template talk:Lang-x2 Module talk:Lang Module talk:In lang Module talk:Lang/ISO 639 synonyms Category talk:Lang and lang-xx template errors

At Wikipedia:Templates for discussion/Log/2025 April 17#Template:Lang-rus it was proposed to replace {{Lang-rus}} with {{lang}} and {{langx}} templates. The discussion ended with the result of merging the features of {{Lang-rus}}, which mostly means enabling {{lang}} to have access to the additional features {{langx}} has leaving the only difference between the two templates the language name appearance vs tooltip. The only parameter left that both don't use is an IPA parameter, but since both don't use it, this could probably either be handled as we do now, or added as a new feature. Gonnym (talk) 08:30, 15 May 2025 (UTC)[reply]

Agreed. Gommeh ➡️ Talk to me 19:52, 15 May 2025 (UTC)[reply]

@Trappist the monk: is this something you could look into? Been over a year since this TFD was closed as merge. Would be great to get some forward progress if you have time! Zackmann (^{Talk to me}/_{What I been doing}) 05:50, 20 May 2026 (UTC)[reply]

{{lang-rus}} is just a wrapper template around {{language with name}} (which wraps {{lang}}), {{transliteration}}, and {{IPA}}. {{lang-rus}} could be simplified somewhat by replacing:

{{Language with name|ru|Russian|links={{{links|no}}}|{{{1|}}}|italic={{{italic|unset}}}}}{{#if:{{{r|{{{2|}}}}}}|, <small>[[Romanization of Russian|romanized]]:</small> {{Transliteration|ru|{{{r|{{{2}}}}}}}}}}

with:

{{langx|code=ru|links={{{links|no}}}|italic={{{italic|}}}|text={{{1}}}|translit={{{r|{{{2|}}}}}}}}

—Trappist the monk (talk) 16:51, 26 May 2026 (UTC)[reply]

The TfD resulted in deletion of that template, not turning it into a wrapper. Also, Russian isn't the only language that is doing hacks to get langx capabilties when using lang. Gonnym (talk) 18:02, 26 May 2026 (UTC)[reply]

From this November 2009 version, {{lang-rus}} has always been a wrapper template. Simplifying as I described above is not turning it into a wrapper.

—Trappist the monk (talk) 11:29, 27 May 2026 (UTC)[reply]

The wrapper discussion while interesting is irrelevant to the TfD result and the above request. I've fixed enough usages of lang/langx templates to know that editors want langx options available for lang usages. There really is no reason to have this distinction other than inertia. Gonnym (talk) 19:10, 27 May 2026 (UTC)[reply]

Template:Lang-mnc uses Möllendorff, Hu, and Abkai for its transliteration system. How would one do the same using {{langx}}? And can we add support for it if there isn't currently a way? Gonnym (talk) 16:02, 13 November 2025 (UTC)[reply]

If we are to believe these search results there are fewer than 10 articles that use {{lang-mnc}} with any of the |v= (Möllendorff), |p= (Hu), |a= (Abkai) transliteration parameters. Of those, the search results showed only one that uses multiple transliteration system parameters.

Certainly we can add these transliteration systems to Module:Lang/data so that for single transliterations one might write:

{{langx|mnc|ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ|Manju gisun|translit-std=mdorff}}

which would render summat like this:

[[Manchu language|Manchu]]: <span lang="mnc">ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ</span>, <small>romanized:&nbsp;</small><span title="Möllendorff transliteration"><i lang="mnc-Latn">Manju gisun</i></span

Manchu: ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ, romanized: Manju gisun

Once added, that one {{lang-mnc}} template with multiple transliteration standard parameters could be written with {{langx}} paired with one or more {{transl}} templates.

I guess I don't see much need to add support for multiple simultaneous transliterations in {{langx}} especially if that support has to look and act just like {{lang-mnc}} which is so obviously different from how {{langx}} renders for so many other languages.

—Trappist the monk (talk) 18:02, 13 November 2025 (UTC)[reply]

Fair point. So lets add the transliteration systems to the data module so I can send the template to TfD with a replacement example. Gonnym (talk) 18:37, 15 November 2025 (UTC)[reply]

Done:

{{langx|mnc|ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ|Manju gisun|translit-std=mdorff}} → Manchu: ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ, romanized: Manju gisun

{{langx|mnc|ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ|Manzhu gisun|translit-std=hu}} → Manchu: ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ, romanized: Manzhu gisun

{{langx|mnc|ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ|Manju gisun|translit-std=Abkai}} → Manchu: ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ, romanized: Manju gisun

—Trappist the monk (talk) 19:24, 15 November 2025 (UTC)[reply]

I noticed that the above romanizations are not linked, while for other languages like Hebrew it is (Hebrew: שלום, romanized: shalom). Why is that? Gonnym (talk) 07:50, 22 November 2025 (UTC)[reply]

Linked for Hebrew because there is an article: Romanization of Hebrew; there is no article title in the form Romanization of ... for Manchu. As an experiment, I created a redirect Romanization of Manchu that links to Transliterations of Manchu. Whether or not that was the correct thing to do, I don't know. Alternately, the redirect could go away and 'Transliterations of Manchu' could be moved to 'Romanization of Manchu'.

—Trappist the monk (talk) 14:43, 22 November 2025 (UTC)[reply]

Ah, ok. So it works by finding the link. That helps. I think this link is better than no link as that was also the link used by lang-mnc. Gonnym (talk) 18:48, 22 November 2025 (UTC)[reply]

I've converted most of the usages. Of those, the search results showed only one that uses multiple transliteration system parameters - so there are 50 pages left that use multiple transliteration system parameters. Might be worth reconsidering allowing multiple systems as I'm sure this won't be the only language that can use this. Gonnym (talk) 13:00, 4 January 2026 (UTC)[reply]

Maybe instead of using {{langx|mnc|ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ|Manju gisun|translit-std=mdorff}} we can change it to {{langx|mnc|ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ|mdorff=Manju gisun}} (use the standard as a parameter; if not in the module's list then show an error), which will then allow also {{langx|mnc|ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ|mdorff=Manju gisun|Abkai=Manju gisun}}. Gonnym (talk) 18:12, 5 January 2026 (UTC)[reply]

@Trappist the monk: The name of the romanization system should be explicitly displayed. For example, Möllendorff and Abkai are the two commonly used systems, but the same latin letter can correspond to different Manchu letters in each system: c represents ᠴ᠊ in Möllendorff, but ᡮ᠊ in Abkai. Simply wikilinking to the transliterations page does not allow readers to distinguish between them. (I see that a title attr is added, but it is not helpful for mobile users.) 内存溢出的猫 (talk) 20:55, 7 February 2026 (UTC)[reply]

Please join the discussion at Template talk:Nihongo#sometimes italicizes stuff. There is a question there about CJK Symbols and Punctuation and Module:Lang. —⁠andrybak (talk) 13:18, 21 February 2026 (UTC)[reply]

In "https://bcl.wikipedia.org/wiki/Module:Lang" How do I turn English Language for Example into Language English?

Like I want "English language" ==> "Tataramon na Ingles"? The problem is This results in "Ingles tataramon na" Shimin_Ufesoj (🦜) 15:14, 6 March 2026 (UTC)[reply]

Link to a testcase at bcl.wiki that shows what it is that you mean.

—Trappist the monk (talk) 15:35, 6 March 2026 (UTC)[reply]

There are times when it would be nice to have the language label parenthesized after the text, i.e., especially in lists or infoboxes, where the marked-up text is more visually or alphabetically important than the language label.

For instance, in {{glossary}} Template formatted glossaries, {{Term}} documentation shows the following examples, and prefers the 2nd pattern for alphabetical reasons:

{{term|1=tyre|content={{langx|en-GB|tyre}} }} {{term|1=tire|content={{langx|en-US|tire}}}} {{defn|1=A resilient wheel covering, usually made of vulcanized rubber.}} British English: tyre American English: tire A resilient wheel covering, usually made of vulcanized rubber.

{{term|1=tire|content={{lang|en-US|tire}} {{small|([[American English]])}} }} {{term|1=tyre|content={{lang|en-GB|tyre}} {{small|([[British English]])}} }} {{defn|1=A resilient wheel covering, usually made of vulcanized rubber.}} tire (American English) tyre (British English) A resilient wheel covering, usually made of vulcanized rubber.

For such purposes (and others, mostly infobox or tables, I imagine), I would like to request an additional parameter to {{langx}}, perhaps something like |labelopt= or |labelstyle= that would behave like the following:

Parameter(s)	Result
{{langx}} (default), {{langx|labelstyle=pre}}	American English: tire
{{langx|labelstyle=post}}	tire (American English)
{{langx|labelstyle=post-sm}}	tire (American English)
{{langx|labelstyle=post-sm|link=no}}	tire (American English)

Personally, I'm really only interested in the small-text post-parenthetical style, but I imagine more people might find the regular-sized post-parenthetical style useful, so I included it here.

I'm not wedded to the exact names of the |labelstyle= parameter or the option names; they are merely suggestions to describe the feature I am requesting.  — sbb (talk) 15:00, 14 March 2026 (UTC)[reply]

{{native name}} or perhaps its redirect {{llang}} already does what you want:

Tire (American English) ← {{native name|en-us|Tire|parensize=85%}}

Tyre (British English) ← {{llang|en-gb|Tyre}}

—Trappist the monk (talk) 15:36, 14 March 2026 (UTC)[reply]

You're kidding me. I honestly had no idea that template existed. Thanks!  — sbb (talk) 23:55, 14 March 2026 (UTC)[reply]

It would be nice if there were a way to format foreign text, transliteration and translation under a single template with the language going only into the metadata. Adding |translit= and |translation= to {{lang}} is a viable aternative to adding a |suppress-language=yes parameter to {{langx}}. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 16:04, 15 March 2026 (UTC)[reply]

When entering the code tfn, this template produces a link to the Tanaina language -- but that's not the common spelling. I'm a bit clueless with templates, so I'm not sure where that's coming from, but the common term and modern spelling[1] is Dena'ina, as reflected in the article Dena'ina language. Is it even possible to change that on this page? GreenLipstickLesbian💌🧸 16:45, 2 April 2026 (UTC)[reply]

{{lang}} gets its language tags and names from the IANA language-subtag-registry file. IANA gets its tags and names (in part) from the ISO 639-3 custodian which defines tfn as 'Tanaina'.

I have added an override to cause Module:Lang to use Denaʼina.

{{lang|tfn|fn=name_from_tag|link=yes}} → Denaʼina

Category:Articles containing Tanaina-language text must be moved to Category:Articles containing Denaʼina-language text; I leave that to you.

—Trappist the monk (talk) 17:12, 2 April 2026 (UTC)[reply]

Ah, thank you for both the explanation and adding the override! And yeah, I'll happily take over the category work. GreenLipstickLesbian💌🧸 21:05, 2 April 2026 (UTC)[reply]

This edit request to Module:Lang has been answered. Set the |answered= parameter to no to reactivate your request.

The values ca and us for the {{{engvar}}} parameter are redundant, as they do not change the spelling of “romanized.” I suggest we remove them. 2600 etc (talk) 01:17, 23 April 2026 (UTC)[reply]

Not done. As a convenience to editors, the value assigned to |envar= should match the article's {{use <country> English}} template.

—Trappist the monk (talk) 12:38, 26 April 2026 (UTC)[reply]

Why does this output the heading "Ancient Greek" in a weird serif font? ~2026-26990-82 (talk) 02:28, 10 May 2026 (UTC)[reply]

Can't read your mind. When you encounter an issue, always say where you are seeing it; always.

For me, this:

{{langx|grc|Κλεοπάτρα}} → Ancient Greek: Κλεοπάτρα

renders correctly.

—Trappist the monk (talk) 02:40, 10 May 2026 (UTC)[reply]

This may exist as a separate template, but I don't know of a way to tag conlanguage text in this manner (and if it isn't and this feature isn't possible/practical, I'd be happy to create and upkeep that new template if I could get some advice!). —It's Okkirae.temp ^('Sup?)! 01:41, 22 May 2026 (UTC)[reply]

Long-form CLCR language tag support is available though, at the moment, only art-x-uropi is defined:

{{lang|fn=name_from_tag|art-x-uropi|link=yes}} → Uropi

{{lang|fn=category_from_tag|art-x-uropi|link=yes}} → Category:Articles containing Uropi-language text

—Trappist the monk (talk) 17:00, 26 May 2026 (UTC)[reply]

Is it possible/proper to define the rest of them? Okkirae∤(䆿±䋚) 18:31, 26 May 2026 (UTC)[reply]

Possible? Yes. Proper? Probably not. If you have a need for a CLCR language tag, it can be added.

—Trappist the monk (talk) 11:33, 27 May 2026 (UTC)[reply]

Is there a way for myself to create a fork of the Lang template for this purpose? I'm new to template coding but determined. Okkirae∤(䆿±䋚) 14:16, 27 May 2026 (UTC)[reply]

At en.wiki, template forking is discouraged. If you need CLCR language tags, they can be added.

—Trappist the monk (talk) 14:29, 27 May 2026 (UTC)[reply]

Alright, thanks anyway. Okkirae∤(䆿±䋚) 01:51, 30 May 2026 (UTC)[reply]

This edit request has been answered. Set the |answered= parameter to no to reactivate your request.

Change Patani Malay > Kelantan–Pattani Malay coz the former redirects to Patani Malays. Ahri Boy (talk) 09:47, 30 May 2026 (UTC)[reply]

Module:Lang does not recognize 'Patani Malay':

{{lang|Patani Malay|fn=tag_from_name}} → Error: language: Patani Malay not found

Perhaps you meant to write 'Pattani Malay'. Module:Lang recognizes that name but it does not create links to Patani Malays:

{{lang|Pattani Malay|fn=tag_from_name}} → mfa → {{lang|mfa|fn=name_from_tag|link=yes}} → Pattani Malay ← [[Pattani Malay language|Pattani Malay]] (a redirect to Kelantan–Pattani Malay)

At this edit, Editor The Bangsawan changed the redirect target from Kelantan–Pattani Malay to Patani Malays. For most of its existence, the Patani Malay redirect has pointed to the language article, not the ethic group article. If there is an issue with the Patani Malay redirect, you should take up that issue with Editor The Bangsawan.

—Trappist the monk (talk) 13:10, 30 May 2026 (UTC)[reply]

Thank you for adding the header on the article Ahri Boy. د بڠساون (talk) 04:46, 5 June 2026 (UTC)[reply]