Template:Language with name is permanently
protected from editing because 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". |
This template should not be used directly in individual articles. Instead, a template with the name lang-xx shold be created, where the xx is the ISO 639 language code. The contents of this template should take the form:
{{langWithName|xx|language-name|{{{1}}}}}
Where xx is again the ISO 639 code, and language-name is the name of the language.
In turn, when calling a lang-xx template, it should be called in the form:
{{lang-xx|your-text-here}}
template:rtl-langWithName (uses template:rtl-lang) (Actually, this one fits better for the Arabic example.)
The lang-ar template contains the following text:
{{langWithName|ar|Arabic|{{{1}}}}}
If it is called as follows:
{{lang-ar|لووووول}}
it yields:
Arabic: لووووول
This has to be some kind of record in meta-template harmfulness. I'm stunned that people would go to this much trouble, creating so many complicated templated just to avoid typing a few extra letters. In most cases the amount of characters saved is amazingly small and people actually use some of the sub-templates to replace existing links at times. Please don't create any more of these. Ever.
Peter Isotalo 20:19, 15 October 2005 (UTC)
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)
I've created a variant, {{ LangWithNameNoItals}}, to be used for languages whose writing systems do not lend themselves to being written in italics (Hebrew, East Asian languages, etc.) — An gr 11:04, 17 January 2007 (UTC)
{{ editprotected}} Add no:Mal:LangWithName (Why so many templates protected so only administrators at en:wp can edit them?) Nsaa 18:04, 29 August 2007 (UTC)
See, for example, the Filipino language article. the relevant wikitext there is "'''Filipino language''' ({{lang-fil|Wikang Filipino}})", which renders here as "Filipino language ( Filipino: Wikang Filipino)". 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 "Filipino language (Filipino: Wikang Filipino)". 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)
I added an optout, |links=no
, 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={{{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 {{
zh-sp|s=something|p=something|links=no}}
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)
Could someone help fix the issue with articles that don't include the suffix "... language" in their article-titles, e.g. Latin is the actual title, but {{ lang-la}} links to Latin language. Please and thank you. :) -- Quiddity ( talk) 17:26, 1 July 2010 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please, ASAP, change the line:
}}: [{{{3}}}] Error: {{Lang}}: unrecognized language tag: {{{1}}} (
help)<noinclude>
to
}}: [{{{3}}}] Error: {{Lang}}: unrecognized language tag: {{{1}}} (
help)<noinclude>
Without this fix, this template cannot be used in ;/: wkimarkup definition lists without causing them to barf.
Test cases
|
---|
Template structured glossary format{{term|1=tyre |content={{lang-en-GB|tyre}}}} {{term|1=tire |content={{lang-en-US|tire}}}} {{defn|1=A resilient wheel covering usually made of vulcanized rubber.}} Manually-formatted wikimarkup; [[British English]]: {{lang|en-GB|tyre}} ; [[American English]]: {{lang|en-US|tyre}} : A resilient wheel covering usually made of vulcanized rubber.
Results: Correct. Wikimarkup + Template:Language with name; {{lang-en-GB|tyre}} ; {{lang-en-US|tire}} : A resilient wheel covering usually made of vulcanized rubber.
Results: FAIL |
— SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 13:04, 1 March 2012 (UTC)
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)
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)
WP:OVERLINK says languages are not usually linked. This template links the language name by default; shouldn't that be changed? Ihardlythinkso ( talk) 03:52, 20 January 2014 (UTC)
Hi,
I am an admin, so I can edit this template, but, since it is high use, I thought I should discuss my idea here first.
I think it would be really useful to be able to have an optional literal translation. Then we could have something like the following:
I am open to suggestion on formatting, for example we could have some kind of abbreviation.
Yaris678 ( talk) 19:45, 26 June 2014 (UTC)
I have applied the change to Template:Language with name and Template:Lang-it. No one has objected to it. Is it time to roll out the change to all the other Lang-xx templates?
What do we think the best way of doing that is? A bot? AWB? One big push? Slowly but surely?
Yaris678 ( talk) 11:43, 15 August 2014 (UTC)
|links=
.|links=
with:
|language=no
) to avoid printing the language name altogether (useful if you're using more than one {{
lang-fr}} or whatever in a row, giving you in read mode e.g. "This comes from the
French: φ and χ", instead of "This comes from the
French: φ and the
French: χ")?|separator= 
) to avoid the colon being printed after the name of the language (it might sometimes fit the sentence the template is embedded in better)?It Is Me Here t / c 18:19, 1 September 2014 (UTC)
|name=no
would prevent showing the name).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
and the like, and never
Why do we use the colon? I recommend we get rid of it. -- Macrakis ( talk) 22:02, 20 September 2014 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please copy full Template:Language with name/sandbox code ( this edit) into live template code. There are two changes:
Change 1: Parameter |name=
added. Option |name=no
prevents mentioning of the language name at all.
Example (German; sandbox stack is in place as of today):
Regular:
New:
Goal 1: This option is useful when the template (and so the language name) the language name is not to be repeated in a sentence, paragraph or table that has multiple elements of the same language, while the template should be used for its other functions. (rephrase -
DePiep (
talk) 16:13, 16 October 2014 (UTC))
- DePiep ( talk) 00:41, 16 October 2014 (UTC)
Change 2: Parameter |sep=
} (for separator) added:
Regular
New:
Goal 2: the colon might not always be the right punctuation in a given situation (sentence). See also the two posts above.
Templates using this metatemplate, like {{
lang-de}}, should follow (pass through parameters |name={{{name|yes}}}
and |sep={{{sep|:}}}
).
- DePiep ( talk) 01:00, 16 October 2014 (UTC)
There's a little annoyance that I have noticed. {{
lang-la}} produces the redirecting link [[Latin language|Latin]]
, which redirects to
Latin. It seems {{
lang-la}} uses {{
language with name}} to create the link. I don't understand how this template works, so I can't answer this question: Is there a way that {{
language with name}} can be modified to produce the sequence [[x]]
instead of [[x language|x]]
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)
Hi,
Kindly enable the parameters links and lit for {{
Template:lang-fa}} as in {{
Template:lang-ar}} ({{Language with name|ar|Arabic|{{{1}}}|links={{{links|yes}}}|rtl=yes|lit={{{lit|}}}}}).
Reference: see
User talk:Harithvh § Language with name.
(
harith (
talk) 12:21, 28 September 2015 (UTC))
Extended content
|
---|
{{
Template:Lang-bh}} |
The abbreviation for "literally" should marked up semantically. The lightweight option is <abbr title="literally">lit.</abbr>
which returns:
lit.. A complete example would be:
French: déjà vu,
lit. already seen
instead of
French: [déjà vu] Error: {{Lang}}: text has italic markup (
help), lit. already seen
Thoughts? —
LLarson (
said &
done) 17:58, 21 January 2016 (UTC)
Per
MOS:SINGLE, it should also be generating single quotes around the gloss supplied in |lit=
(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 {{
lang-es|mi casa es su casa|lit='my house is your house'}}
that it will produce output like:
Spanish
: [mi casa es su casa] Error: {{Lang}}: text has italic markup (
help),
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 |[optional whitespace]lit[optional whitespace]=[optional whitespace]
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)
Please see:
Template_talk:Lang#Parameter to selectively disable auto-italics in the Lang-xx templates
—
SMcCandlish
☏
¢ >ʌⱷ҅ᴥⱷʌ< 07:17, 30 October 2017 (UTC)
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:
Latin: salve,
lit. 'hello'
salve, 'hello'
with setting labels=no using
Template:Korean:
Korean: 안녕;
Hanja: annyeong;
lit. hello
안녕; annyeong;
lit. hello
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)
Why the colon? - The matter has been raised by Macrakis since 2014, but nobody cared, apparently.
I propose to add an optional parameter to suppress the colon, in order to make the text sound more natural in sentences like:
Instead of the present code:
The colon is often useful, but it breaks the natural flow in some contexts. Est. 2021 ( talk · contribs) 16:53, 11 February 2021 (UTC)
Hi, where is the usage of this template? Is this template obsolete? Hooman Mallahzadeh ( talk) 17:25, 13 January 2022 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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={{{italic|unset}}}" i.e., change
{{#ifeq:{{{links|{{{link|}}}}}}|no
|{{{2}}}
|[[{{{2}}} language|{{{2}}}]]
}}: {{Lang|{{{1}}}|{{{3}}}|rtl={{{rtl|}}}|nocat={{{nocat|}}}}}{{#if:{{{4<includeonly>|{{{lit|}}}</includeonly>}}}|, {{small|[[Literal translation|lit.]] }}'{{{4|{{{lit}}}}}}'}}<noinclude>{{documentation}}</noinclude>
to
{{#ifeq:{{{links|{{{link|}}}}}}|no
|{{{2}}}
|[[{{{2}}} language|{{{2}}}]]
}}: {{Lang|{{{1}}}|{{{3}}}|rtl={{{rtl|}}}|nocat={{{nocat|}}}|italic={{{italic|unset}}}}}{{#if:{{{4<includeonly>|{{{lit|}}}</includeonly>}}}|, {{small|[[Literal translation|lit.]] }}'{{{4|{{{lit}}}}}}'}}<noinclude>{{documentation}}</noinclude>
that has an additional argument i.e. "italic={{{italic|unset}}}". You can test this functionality in Template:Language with name/sandbox and Template:Language with name/testcases. I.e., "{{Lang-rus/sandbox |déjà vu| lit=already seen|italic=no}}" results in " Russian: déjà vu" that is not italic. And "{{Lang-rus/sandbox |déjà vu| lit=already seen|italic=yes}}" results in " Russian: déjà vu" that is italic. But the output of {{Lang-rus|déjà vu|lit=already seen|italic=no}} is Russian: déjà vu that is incorrectly still italic. So by this small modification i.e., "adding argument italic={{{italic|unset}}}" italic property is inherited.
Thanks, Hooman Mallahzadeh ( talk) 16:25, 13 January 2022 (UTC)
|italic=no
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)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 {{ Lang-rrm}}, using the proposed ISO 639-3 code listed at its article. — HTGS ( talk) 21:47, 31 March 2022 (UTC)
I noticed a difference between the English Wikipedia and the versions in other languages. For example, on Wikipedia in other languages Template:Swahili will result in Template:lang-sw, while here these redirects don't even exist. Same for Template:Russian, Template:Ukrainian, Template:Serbian, Template:German, Template:Italian etc.
Shouldn't we allow that? Est. 2021 ( talk · contribs) 16:16, 15 October 2022 (UTC)
Template:Language with name is permanently
protected from editing because 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". |
This template should not be used directly in individual articles. Instead, a template with the name lang-xx shold be created, where the xx is the ISO 639 language code. The contents of this template should take the form:
{{langWithName|xx|language-name|{{{1}}}}}
Where xx is again the ISO 639 code, and language-name is the name of the language.
In turn, when calling a lang-xx template, it should be called in the form:
{{lang-xx|your-text-here}}
template:rtl-langWithName (uses template:rtl-lang) (Actually, this one fits better for the Arabic example.)
The lang-ar template contains the following text:
{{langWithName|ar|Arabic|{{{1}}}}}
If it is called as follows:
{{lang-ar|لووووول}}
it yields:
Arabic: لووووول
This has to be some kind of record in meta-template harmfulness. I'm stunned that people would go to this much trouble, creating so many complicated templated just to avoid typing a few extra letters. In most cases the amount of characters saved is amazingly small and people actually use some of the sub-templates to replace existing links at times. Please don't create any more of these. Ever.
Peter Isotalo 20:19, 15 October 2005 (UTC)
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)
I've created a variant, {{ LangWithNameNoItals}}, to be used for languages whose writing systems do not lend themselves to being written in italics (Hebrew, East Asian languages, etc.) — An gr 11:04, 17 January 2007 (UTC)
{{ editprotected}} Add no:Mal:LangWithName (Why so many templates protected so only administrators at en:wp can edit them?) Nsaa 18:04, 29 August 2007 (UTC)
See, for example, the Filipino language article. the relevant wikitext there is "'''Filipino language''' ({{lang-fil|Wikang Filipino}})", which renders here as "Filipino language ( Filipino: Wikang Filipino)". 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 "Filipino language (Filipino: Wikang Filipino)". 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)
I added an optout, |links=no
, 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={{{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 {{
zh-sp|s=something|p=something|links=no}}
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)
Could someone help fix the issue with articles that don't include the suffix "... language" in their article-titles, e.g. Latin is the actual title, but {{ lang-la}} links to Latin language. Please and thank you. :) -- Quiddity ( talk) 17:26, 1 July 2010 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please, ASAP, change the line:
}}: [{{{3}}}] Error: {{Lang}}: unrecognized language tag: {{{1}}} (
help)<noinclude>
to
}}: [{{{3}}}] Error: {{Lang}}: unrecognized language tag: {{{1}}} (
help)<noinclude>
Without this fix, this template cannot be used in ;/: wkimarkup definition lists without causing them to barf.
Test cases
|
---|
Template structured glossary format{{term|1=tyre |content={{lang-en-GB|tyre}}}} {{term|1=tire |content={{lang-en-US|tire}}}} {{defn|1=A resilient wheel covering usually made of vulcanized rubber.}} Manually-formatted wikimarkup; [[British English]]: {{lang|en-GB|tyre}} ; [[American English]]: {{lang|en-US|tyre}} : A resilient wheel covering usually made of vulcanized rubber.
Results: Correct. Wikimarkup + Template:Language with name; {{lang-en-GB|tyre}} ; {{lang-en-US|tire}} : A resilient wheel covering usually made of vulcanized rubber.
Results: FAIL |
— SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 13:04, 1 March 2012 (UTC)
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)
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)
WP:OVERLINK says languages are not usually linked. This template links the language name by default; shouldn't that be changed? Ihardlythinkso ( talk) 03:52, 20 January 2014 (UTC)
Hi,
I am an admin, so I can edit this template, but, since it is high use, I thought I should discuss my idea here first.
I think it would be really useful to be able to have an optional literal translation. Then we could have something like the following:
I am open to suggestion on formatting, for example we could have some kind of abbreviation.
Yaris678 ( talk) 19:45, 26 June 2014 (UTC)
I have applied the change to Template:Language with name and Template:Lang-it. No one has objected to it. Is it time to roll out the change to all the other Lang-xx templates?
What do we think the best way of doing that is? A bot? AWB? One big push? Slowly but surely?
Yaris678 ( talk) 11:43, 15 August 2014 (UTC)
|links=
.|links=
with:
|language=no
) to avoid printing the language name altogether (useful if you're using more than one {{
lang-fr}} or whatever in a row, giving you in read mode e.g. "This comes from the
French: φ and χ", instead of "This comes from the
French: φ and the
French: χ")?|separator= 
) to avoid the colon being printed after the name of the language (it might sometimes fit the sentence the template is embedded in better)?It Is Me Here t / c 18:19, 1 September 2014 (UTC)
|name=no
would prevent showing the name).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
and the like, and never
Why do we use the colon? I recommend we get rid of it. -- Macrakis ( talk) 22:02, 20 September 2014 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please copy full Template:Language with name/sandbox code ( this edit) into live template code. There are two changes:
Change 1: Parameter |name=
added. Option |name=no
prevents mentioning of the language name at all.
Example (German; sandbox stack is in place as of today):
Regular:
New:
Goal 1: This option is useful when the template (and so the language name) the language name is not to be repeated in a sentence, paragraph or table that has multiple elements of the same language, while the template should be used for its other functions. (rephrase -
DePiep (
talk) 16:13, 16 October 2014 (UTC))
- DePiep ( talk) 00:41, 16 October 2014 (UTC)
Change 2: Parameter |sep=
} (for separator) added:
Regular
New:
Goal 2: the colon might not always be the right punctuation in a given situation (sentence). See also the two posts above.
Templates using this metatemplate, like {{
lang-de}}, should follow (pass through parameters |name={{{name|yes}}}
and |sep={{{sep|:}}}
).
- DePiep ( talk) 01:00, 16 October 2014 (UTC)
There's a little annoyance that I have noticed. {{
lang-la}} produces the redirecting link [[Latin language|Latin]]
, which redirects to
Latin. It seems {{
lang-la}} uses {{
language with name}} to create the link. I don't understand how this template works, so I can't answer this question: Is there a way that {{
language with name}} can be modified to produce the sequence [[x]]
instead of [[x language|x]]
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)
Hi,
Kindly enable the parameters links and lit for {{
Template:lang-fa}} as in {{
Template:lang-ar}} ({{Language with name|ar|Arabic|{{{1}}}|links={{{links|yes}}}|rtl=yes|lit={{{lit|}}}}}).
Reference: see
User talk:Harithvh § Language with name.
(
harith (
talk) 12:21, 28 September 2015 (UTC))
Extended content
|
---|
{{
Template:Lang-bh}} |
The abbreviation for "literally" should marked up semantically. The lightweight option is <abbr title="literally">lit.</abbr>
which returns:
lit.. A complete example would be:
French: déjà vu,
lit. already seen
instead of
French: [déjà vu] Error: {{Lang}}: text has italic markup (
help), lit. already seen
Thoughts? —
LLarson (
said &
done) 17:58, 21 January 2016 (UTC)
Per
MOS:SINGLE, it should also be generating single quotes around the gloss supplied in |lit=
(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 {{
lang-es|mi casa es su casa|lit='my house is your house'}}
that it will produce output like:
Spanish
: [mi casa es su casa] Error: {{Lang}}: text has italic markup (
help),
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 |[optional whitespace]lit[optional whitespace]=[optional whitespace]
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)
Please see:
Template_talk:Lang#Parameter to selectively disable auto-italics in the Lang-xx templates
—
SMcCandlish
☏
¢ >ʌⱷ҅ᴥⱷʌ< 07:17, 30 October 2017 (UTC)
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:
Latin: salve,
lit. 'hello'
salve, 'hello'
with setting labels=no using
Template:Korean:
Korean: 안녕;
Hanja: annyeong;
lit. hello
안녕; annyeong;
lit. hello
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)
Why the colon? - The matter has been raised by Macrakis since 2014, but nobody cared, apparently.
I propose to add an optional parameter to suppress the colon, in order to make the text sound more natural in sentences like:
Instead of the present code:
The colon is often useful, but it breaks the natural flow in some contexts. Est. 2021 ( talk · contribs) 16:53, 11 February 2021 (UTC)
Hi, where is the usage of this template? Is this template obsolete? Hooman Mallahzadeh ( talk) 17:25, 13 January 2022 (UTC)
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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={{{italic|unset}}}" i.e., change
{{#ifeq:{{{links|{{{link|}}}}}}|no
|{{{2}}}
|[[{{{2}}} language|{{{2}}}]]
}}: {{Lang|{{{1}}}|{{{3}}}|rtl={{{rtl|}}}|nocat={{{nocat|}}}}}{{#if:{{{4<includeonly>|{{{lit|}}}</includeonly>}}}|, {{small|[[Literal translation|lit.]] }}'{{{4|{{{lit}}}}}}'}}<noinclude>{{documentation}}</noinclude>
to
{{#ifeq:{{{links|{{{link|}}}}}}|no
|{{{2}}}
|[[{{{2}}} language|{{{2}}}]]
}}: {{Lang|{{{1}}}|{{{3}}}|rtl={{{rtl|}}}|nocat={{{nocat|}}}|italic={{{italic|unset}}}}}{{#if:{{{4<includeonly>|{{{lit|}}}</includeonly>}}}|, {{small|[[Literal translation|lit.]] }}'{{{4|{{{lit}}}}}}'}}<noinclude>{{documentation}}</noinclude>
that has an additional argument i.e. "italic={{{italic|unset}}}". You can test this functionality in Template:Language with name/sandbox and Template:Language with name/testcases. I.e., "{{Lang-rus/sandbox |déjà vu| lit=already seen|italic=no}}" results in " Russian: déjà vu" that is not italic. And "{{Lang-rus/sandbox |déjà vu| lit=already seen|italic=yes}}" results in " Russian: déjà vu" that is italic. But the output of {{Lang-rus|déjà vu|lit=already seen|italic=no}} is Russian: déjà vu that is incorrectly still italic. So by this small modification i.e., "adding argument italic={{{italic|unset}}}" italic property is inherited.
Thanks, Hooman Mallahzadeh ( talk) 16:25, 13 January 2022 (UTC)
|italic=no
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)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 {{ Lang-rrm}}, using the proposed ISO 639-3 code listed at its article. — HTGS ( talk) 21:47, 31 March 2022 (UTC)
I noticed a difference between the English Wikipedia and the versions in other languages. For example, on Wikipedia in other languages Template:Swahili will result in Template:lang-sw, while here these redirects don't even exist. Same for Template:Russian, Template:Ukrainian, Template:Serbian, Template:German, Template:Italian etc.
Shouldn't we allow that? Est. 2021 ( talk · contribs) 16:16, 15 October 2022 (UTC)