Template talk:Ls
Change
[edit]I'd like to perform this change:
To add a classname 'langlabel' and a lang attribute to the language label, so the label can be detected and hidden if necessary by javascripts.
The span attribute might be necessary to support inlining properly, this part of change is not important to my eyes for now.
Any opinion against the change?
Esby (talk) 03:46, 17 April 2010 (UTC)
- I'd support adding the attributes. I'm unsure about the span. Do you plan to change it or not? It's not clear to me whether the sentence The span attribute might be necessary to support inlining properly, this part of change is not important to my eyes for now. means that the span is "necessary" or "not important". If you plan to change it, could you elaborate about the advantages and how this will or will not affect the default display of the template? --Slomox (talk) 11:43, 17 April 2010 (UTC)
- The span was an idea I had, I actually did not wanted to suggest changing it for now, it's just the link I copy pasted from my test page contained this unwanted change : basically, using a div trigger a line break while this makes it not compatible with inlining since inlining requires no line break at all, inlining here being putting the translations together in one line. Now the problem with the span is that a div cannot be contained in a span. So the usage is actually not universal and I don't think it should be done. I am thinking to create a template {{Mldi}} that would use a template {{Lsi}} which would ouput all language in one row. Basically, the mldi should also uses a span. You can see an inlining example here Esby (talk) 12:20, 17 April 2010 (UTC)
Change about the class & lang attributes performed. [1]. Actually, there might be a similar change to perform in {{Description}}, since templates like {{En}} or {{Fr}} uses it... Esby (talk) 11:43, 23 April 2010 (UTC)
Title
[edit]Hi. Is it possible to hide the "English:" (or similar) prefixes when using this template? Rehman 03:38, 16 January 2011 (UTC)
- You can simply use the parameter
CSS-label
with the value:display:none
— François [Discussion] 13:41, 24 July 2012 (UTC)- Mmm, don't remember why I needed this, but thanks anyways ;) Should be useful for others like you said... Rehman 06:07, 25 July 2012 (UTC)
Uppercase 1st letter of language
[edit]{{Edit request}} Hello,
could someone add a {{ucfirst: ... }}
around {{#language:}}
, so for example French will be renderred as Français and not français? (note that it is already so in Template:Description).
Thanks! — François [Discussion] 12:56, 7 July 2012 (UTC)
- Done. Please check if I did it correctly. Thanks! Trijnsteltalk 21:16, 8 July 2012 (UTC)
- Seems to perfectly work! Thank you — François [Discussion] 13:24, 24 July 2012 (UTC)
- {{Edit request}} Please UNDO that! This is NOT correct in languages that distinguish letter case of the initial for different meanings. The original native language names must be displayed as is, without any alteration. They should all be exactly like in the interlanguage links on the side bar and as they are translated in MediaWiki. Great care was taken in translating language names that you would not alter these names. The basic simple capitalization of initials only works reliably in English, but not even in other Latin-written languages (e.g. French uses lowercase for languages, an a capital for another meaning; the capitalization follows other rules).
- So we should see "français" (the language), not "Français" (the people). See français vs. Français in French Wiktionary for more.
- Other languages have their own capitalization rules as well. Don't blindly apply the basic English capitalization rules (or even just the French capitalization rules) to any foreign words! displaying for example "ChiTsonga" instead of "chiTsonga" is simply false (there are similar issues with other non-Latin scripts, notably the Georgian script(s) that have complex grammatical capitalization rules...). verdy_p (talk) 17:10, 26 May 2016 (UTC)
- Seems to perfectly work! Thank you — François [Discussion] 13:24, 24 July 2012 (UTC)
Machine-readable standard markup for i18n templates
[edit]I started a discussion about standardizing the markup generated by i18n templates so that it can be made machine-readable: Commons talk:Machine-readable data#Machine-readable markup for languages/language names; please share your opinion! --Tgr (WMF) (talk) 11:16, 11 November 2014 (UTC)