Template talk:langname

Temporary
This should be used in all templates that currently only accept the full language name to allow them to accept language codes as well. This should not be used in place of as it encourages inconsistency - it is only as a temporary measure until all templates that don't use  have been fixed, and the calls to them updated. Conrad.Irwin 09:48, 7 May 2008 (UTC)


 * It is possible that the end result should be the opposite, always using {langname} even though we prefer the code. If something (say, maybe, AF) routinely coverted "|lang=(name)" to the code, it would not be necessary to force a transition or insist that users know the code. (and the internals of langname and language can then be optimized) Robert Ullmann 14:00, 7 May 2008 (UTC)


 * The problem I see is that spellings of language names are less standardized. If someone enters a "bad" spelling and the template breaks, the editor may not know why.  The codes are at least standardized and do not have spelling variants. --EncycloPetey 17:14, 30 June 2008 (UTC)

Proposed modification: use   rather than   
I've suggested modifying this template to use rather than {&#x7B;#if:0|…&#x7D;} in the event that the argument contains one or more uppercase characters (that is, in the event that the argument is the name of a language rather than the code for it). This will not affect entries in any visible way, but it will populate Special:WhatLinksHere/Template:langname/name with the list of pages wherein such arguments occur, allowing for some cleanup to take place. I believe intends to implement that suggestion within the next few days if no one objects or has a better idea, so if you do, please leave a comment at Grease pit. —Ruakh TALK 01:56, 9 September 2010 (UTC)

RFDO discussion: April–June 2014
Probably the last holdover from the language template era. Even from the time before that. But it's orphaned now. 23:51, 7 April 2014 (UTC)
 * Deleted. 18:45, 22 April 2014 (UTC)
 * I think it's orphaned because people substitute it. --kc_kennylau (talk) 18:50, 22 April 2014 (UTC)
 * Nothing seems to indicate there is any usage remaining. Entry struck, declaring this closed. — Keφr 12:52, 8 June 2014 (UTC)

Why does this subst?
I think we need a template like this to generate the language name from the code in place of a complex module invocation. But why does this have a 'safesubst:' in front of it, and the doc say it has to be substituted? Benwing2 (talk) 03:58, 10 October 2019 (UTC)
 * Hmm, I can't remember why I thought it should always be substituted. The safesubst bit is just to allow it to be substituted with . May as well open it up to being used without substitution. — Eru·tuon 04:03, 10 October 2019 (UTC)