Template talk:Language with name

message: :ko:Template:Llang seems to achieve a similar effect by including :ko:Template:언어 이름 ( = “language name(s)”), but without the need of creating dozens of other templates. If you like its approach, perhaps something like that can replace this template and most lang-xx templates.—Wikipeditor 05:44, 2 February 2006 (UTC)
thread_title:  Similar template 

message: I've created a variant, , to be used for languages whose writing systems do not lend themselves to being written in italics (Hebrew, East Asian languages, etc.) —Angr 11:04, 17 January 2007 (UTC)
replies: text: this template now forces no italics either. Italics are rather inserted in the "lang-xx" templates transcluding this one. dab (𒁳) 10:34, 24 July 2007 (UTC)
thread_title:  No italics 

message: See, for example, the Filipino language article. the relevant wikitext there is "", which renders here as "". However, in the Filipino language article, it renders improperly (and in violation of WP:LEDE#Format of the first sentence, "do not boldface foreign names not normally used in English") as "". This is because this template tries to place a self-referential wikilink.
It seems to me that the fix for this would involve magic words and parser functions—about which I am aware but which I don't often use. Could someone who is a better template coder than I please fix this? Thanks. -- Boracay Bill (talk) 06:05, 30 January 2009 (UTC)
thread_title:  Bolding problem with this template. 

message: I added an optout, , to make this template not link the language names (should be useful in articles where you're using it over and over and there are overlinking concerns). To make it functional in the shell templates, however, |links=yes or something alone those lines needs to be added to the templates that call this one. For example, I did this to a bunch of the Chinese templates; this make it so someone can use  and have it remove the links (for example, in the lede paragraph of Not One Less).
Anyway, whoever wants to help out is welcome to add this code to the other templates to expand the functionality of this, since there are thousands of these templates and I'm in no mood to do it to all of them (I basically just updated the few templates that I myself use). rʨanaɢ talk/contribs 03:12, 17 September 2009 (UTC)
thread_title:  Delinking 

message: Please, ASAP, change the line:
 }}: <noinclude>
to
 }}: <noinclude>
Without this fix, this template cannot be used in ;/: wkimarkup definition lists without causing them to barf. 
===Template structured glossary format===
 
 
 
Results:  
===Manually-formatted wikimarkup===
 ; British English: 
 ; American English: 
 : A resilient wheel covering usually made of vulcanized rubber.
; British English: 
; American English: 
: A resilient wheel covering usually made of vulcanized rubber.
Results:  
===Wikimarkup + Template:Language with name===
 ; 
 ; 
 : A resilient wheel covering usually made of vulcanized rubber.
; 
; 
: A resilient wheel covering usually made of vulcanized rubber.
Results:  
— SMcCandlish    Talk⇒ ɖ∘¿¤þ   Contrib.  13:04, 1 March 2012 (UTC)
replies: text: Done Anomie⚔ 04:58, 2 March 2012 (UTC)
thread_title:  Colon has to be escaped or definition lists get hosed 

message: ; 
 ; 
 : A resilient wheel covering usually made of vulcanized rubber.
; 
; 
: A resilient wheel covering usually made of vulcanized rubber.
Results:  
— SMcCandlish    Talk⇒ ɖ∘¿¤þ   Contrib.  13:04, 1 March 2012 (UTC)
replies: text: Done Anomie⚔ 04:58, 2 March 2012 (UTC)
thread_title: Wikimarkup + [[Template:Language with name]]

message: Instead of having individual templates for every language transcluding this meta template we should have one template only with a parameter for language. As it stands now, if we add a parameter to this template, as I'm going to propose next, then each of the transcluding templates will have to be updated, including user instructions. That is exceedingly cumbersome and impractical. __meco (talk) 09:28, 20 April 2012 (UTC)
thread_title:  This scheme should be streamlined 

message: I propose a new parameter be added to this template, |silent=yes, which, when active, will cause the name of the language to be suppressed altogether. The cases where this would be used are when the foreign-language term precedes the English name. Then the only effect of using the template would be to categorize the article into the relevant multilingual support category.
A more neat solution to this would perhaps be to modify the existing |links= parameter to handle a different set of values. That would probably mean to give it a new name, e.g. |show=, with the possible values yes (default), unlink and no. This proposal must be seen in connection with my proposal for streamlining this scheme altogether in the previous section. __meco (talk) 09:39, 20 April 2012 (UTC)
thread_title:  Request for added parameter 

message: In every Wikipedia context I've seen, the colon in this template is unnecessary, ugly, and different from the usual formatting in other printed matter. Can anyone point to examples in professionally typeset material that uses the colon? In all the books I've looked at recently, you see things like
:from French carton
:this word, from the French carton, has now ...
:from Greek τρόπος
and the like, and never
:from French: carton
:this word, from the French: carton, has now ...
:from Greek: τρόπος
Why do we use the colon? I recommend we get rid of it. --Macrakis (talk) 22:02, 20 September 2014 (UTC)
replies: text: re . See below for a edit request. -DePiep (talk) 01:10, 16 October 2014 (UTC)
thread_title: Why the colon?

message: There's a little annoyance that I have noticed.  produces the redirecting link , which redirects to Latin. It seems  uses  to create the link. I don't understand how this template works, so I can't answer this question: Is there a way that  can be modified to produce the sequence  instead of  in the cases of languages like Latin and Old English, whose article names do not end in language? — Eru·tuon 02:32, 18 December 2014 (UTC)
replies: text: There would be no advantage to this, since all the redirects are in place.  The good sense is to keep the template as simple as possible to use and to maintain. All the best: Rich Farmbrough, 23:27, 24 July 2015 (UTC)
thread_title:  Problems with Template:Lang-la 

message: Hi,Kindly enable the parameters links and lit for  as in  ().Reference: see .(harith (talk) 12:21, 28 September 2015 (UTC)
replies: text: Would you kindly provide a list of templates needing to be changed? How many are protected? — Martin (MSGJ · talk) 14:04, 28 September 2015 (UTC)

text: I think. Let me know if there are any others. — Martin (MSGJ · talk) 19:56, 28 September 2015 (UTC)
replies: text:  , I have not checked all, but the ones I have noted that needed to changed are as follows, the bold ones are those I wanted to change yesterday, but somehow missed: (harith (talk) 02:46, 29 September 2015 (UTC)
replies: text:  a lot of these are not protected. Could you just list those that you need help with? — Martin (MSGJ · talk) 12:41, 29 September 2015 (UTC)
replies: text: Hi, Thanks for the notification, the ones needed help are , , and . (harith·discuss) 03:23, 30 September 2015 (UTC)
replies: text:  — Martin (MSGJ · talk) 08:32, 30 September 2015 (UTC)
thread_title: Requirements of parameters for lang-x template

message: The abbreviation for "literally" should marked up semantically. The lightweight option is  which returns: lit.. A complete example would be:
instead of
Thoughts? —LLarson (said & done) 17:58, 21 January 2016 (UTC)
replies: text: I updated the sandbox with this proposal, and updated , , and , to look to the sandbox instead of the live version of the template. All the pieces come together in testcases, where the demonstration now is live. —LLarson (said & done) 20:41, 24 March 2016 (UTC)
replies: text:  I submitted this proposal almost three months ago and presented a modified sandbox with testcases almost three weeks ago and there have been no objections. Would you consider updating the template? —LLarson (said & done) 21:16, 12 April 2016 (UTC)
replies: text:  Done. Seems straightforward enough.  We shouldn't add that around every abbreviation everywhere. We don't need it for "Dr[.]", for example, and it would be pointless if done to an abbr. used shortly after the expanded version, since it's already clear what it means in context. But it makes sense in a case like this, where it's usually the first (possibly only) occurrence on the page. The only downside I can think of is if it's used several times in the same block of text, e.g. to translate an English colloquial phrase into rough but not literal versions in 5 other languages. We don't do that often, though.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  21:00, 13 April 2016 (UTC)
thread_title:  Abbreviation for literally 

message: Per MOS:SINGLE, it should also be generating single quotes around the gloss supplied in  (i.e. appearing after the text "lit.". I've implemented this in the sandbox, so the test cases in the above thread also testcase this.  I implemented it as ', so that it does not accidentally trigger any parsing problems, e.g. when used with a value that leads or ends with the same character, which would put two in a row and turn on italicization accidentally.  The only downside I can think of is that in a few cases where people have included single quotes around a value manually (e.g. as  that it will produce output like: Spanish
: , lit. my house is your house. But this is not a big problem. It just looks like double quotes (which many cases already incorrectly have), and it's not any more incorrect that the majority use (no quotes at all) that we're stuck with in the vast majority of cases. A bot can fix it; just look for any string in this template, occurring after |lit= that both begins and ends with a ' (or, while we're at it, any other quotation-character pairs). I could probably cobble up the regular expression to do this myself.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  21:29, 13 April 2016 (UTC)
replies: text: You know I’m pretty fond of you and your work, but this doesn’t look quite right to me; apologies if I got the order of operations wrong, but I brought it up on MOS talk instead of here. Thank you, again. —LLarson (said & done) 16:48, 14 April 2016 (UTC)
thread_title:  Single quotes for value of "lit" parameter 

message: Please see: Template_talk:Lang#Parameter to selectively disable auto-italics in the Lang-xx templates
 — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  07:17, 30 October 2017 (UTC)
thread_title:  Overhauling the lang-{{var|xx}} templates for more selective italics behavior 

message: In the documentation (for example, near the bottom of Template:Lang-la), the label parameter description says, "If 'none', suppresses language link and label". However, it also seems to suppress the 'lit.' which is normally generated by the lit parameter, and not just the language label. Is this intended, and if so, should it be changed so that there is a separate control for the lit label?
Compare setting label=none using Template:Lang-la:
with setting labels=no using Template:Korean:
The implementation of label=none and labels=no, respectively, is different. Even though Template:Korean uses Template:Lang, the plaintext lit label remains even when the labels parameter is off. I'm not sure which one is better for usability and complexity, but I do wonder about it. ChromeGames923 (talk) 02:52, 4 March 2020 (UTC)
thread_title:  Effect of label parameter on lit. 

message: To inherit italic property of first argument text from templates like "Template:Lang-rus" to this template and from this template to the template Template:Lang and then pass to Module:Lang, please add this argument "italic=unset" i.e., change 
: 
to
: 
that has an additional argument i.e. "italic=unset". You can test this functionality in Template:Language with name/sandbox and Template:Language with name/testcases. 
I.e., "" results in "" that is not italic. And "" results in "" that is italic. But the output of  is  that is incorrectly still italic. So by this small modification i.e., "adding argument italic=unset" italic property is inherited.
Thanks, Hooman Mallahzadeh (talk) 16:25, 13 January 2022 (UTC)
replies: text: . P.I. Ellsworth - ed. put'r there 02:33, 14 January 2022 (UTC)
replies: text:  Is the default value "unset" in "italic=unset" true? If it should be italic in the default case, set it to "yes" or remove "unset" from that argument. Thanks, Hooman Mallahzadeh (talk) 06:09, 14 January 2022 (UTC)
replies: text:  my limited understanding is that any value other than  results in italics. Do you mean that your intial request should have defaulted to "yes" instead of "unset"? P.I. Ellsworth - ed. put'r there 04:36, 15 January 2022 (UTC)

text: , makes no difference. P.I. Ellsworth - ed. put'r there 12:53, 16 January 2022 (UTC)
replies: text: Greetings User:Paine_Ellsworth. It seems that the code tweek affected Template:Lang-ka and now all Georgian script-written texts are in Italic. Can you please tweek in a way that Georgian is not affected? Regards, An emperor /// Ave 16:29, 16 January 2022 (UTC)
replies: text:  To do that, we should set "italic=no" in the template Template:Lang-ka, but in this template, we should set "italic" to "yes" value as the default value. Hooman Mallahzadeh (talk) 16:46, 16 January 2022 (UTC)
replies: text:   is . P.I. Ellsworth - ed. put'r there 02:10, 17 January 2022 (UTC)
replies: text: Thank you dear colleagues! Regards, An emperor /// Ave 18:05, 17 January 2022 (UTC)
thread_title:  Template-protected edit request on 13 January 2022 

message: Is this an appropriate place to discuss which language templates should exist? It is rare, but I would like to be able to tag words or phrases from Moriori. If appropriate, I can happily clone another template at , using the proposed ISO 639-3 code listed at its article. — HTGS (talk) 21:47, 31 March 2022 (UTC)
thread_title:  Additional languages? 

message: I noticed a difference between the English Wikipedia and the versions in other languages. For example, on Wikipedia in other languages  will result in , while here these redirects don't even exist.
Same for , , , ,  etc.
Shouldn't we allow that? Est. 2021 (talk · contribs) 16:16, 15 October 2022 (UTC)
replies: text: Probably not. Templates should be named for what they do, and we would end up with a confusing mix of template purposes. See , , , and others that already exist and point to a variety of template types. I would prefer that those templates did not exist either, or were template disambiguation pages. – Jonesey95 (talk) 19:26, 15 October 2022 (UTC)
thread_title:  Redirect from Language name