Template talk:Lang

From Wikipedia, the free encyclopedia

You have new messages (last change).
Protected Template:Lang has been protected indefinitely. Use {{editprotected}} on this page to request an edit.
Templates for deletion This template survived a request for deletion. The result of the discussion was keep.

Contents

[edit] Documentation

[edit] Usage

The purpose of this template is to indicate that a given span of text belongs to a particular language (see language code).

{{lang|Language tag|Text}}

Use ISO 639 language codes. Example (where fr is the code for French):

* She said: "{{lang|fr|''Je suis Française.''}}"

Results in your browser:

  • She said: "Je suis Française."

Also, there are also versions of this template for each specific language that also print the language's name, intended to be used the first time that language is used in the article. For example, "{{lang-es|Español}}" and "{{lang-ru|русский язык}}" gives "Spanish: Español" and "Russian: русский язык".

Language subtags can also be used to indicate writing script or regional variation of a language. According to the W3C, "The golden rule when creating language tags is to keep the tag as short as possible",[1] so such subtags should only be added if there is an important reason to use them. ISO 639-1 is preferred over ISO 639-2 and ISO 639-3.

[edit] Indicating writing script

If necessary, add the ISO 15924 code to indicate the script.

For example, Russian is usually written in the Cyrillic alphabet, therefore the 'Cyrl' script code is superfluous and the language code will be ru instead of ru-Cyrl. However, when that text is transliterated the Latn code (latin script) should be used because it isn't the default script for Russian: ru-Latn. Example:

* Moscow ([[Russian language|Russian]]: {{lang|ru|Москва́}}, {{lang|ru-Latn|''Moskva''}})

which is the same as

* Moscow ({{lang-ru|Москва́}}, {{lang|ru-Latn|''Moskva''}})

Results in your browser:

  • Moscow (Russian: Москва́, Moskva)

IANA maintains a list specifying when the script tag should be suppressed [2]. In some cases the script must be always specified, like Tajik which can be equally written in Arabic, Latin or Cyrilic alphabets:

* Tajik ({{rtl-lang|tg-Arab|تاجیکی}}, {{lang|tg-Latn|''tojikī''}}, {{lang|tg-Cyrl|тоҷикӣ}})

Which results in your browser:

  • Tajik (تاجیکی‎, tojikī, тоҷикӣ)

Note the use of {{rtl-lang}} instead of {{lang}} when using the Arabic script (see below section writing direction).

[edit] Indicating regional variant

In some cases, maybe it will be needed to add ISO 3166-1 alpha-2 country codes (specific usage of that country). Of course the three codes can appear in the same tag, for example the code zh-Hant-TW will be used for Chinese text written with Traditional Han characters, containing words or expressions specific to Taiwan. Examples:

* {{lang|zh-Hant-TW|臺灣}}

Results in your browser:

  • 臺灣

[edit] Writing direction

{{rtl-lang}} is a specific template for right-to-left languages like Arabic or Hebrew.

[edit] Rationale

  • Web browsers can use the information to choose an appropriate font.
    • This is great for CJK where a character can be given its language-specific shape but will fall back to another form if no appropriate font is found or if the preferred font lacks that character, for example because the language does not make use of that character: see this comparison table and screenshot.
  • For accessibility purposes: screen readers need language info to provide correctly audio output.
  • For spell checkers and grammar checkers.
  • To help browsers choosing appropiate quotation marks, and making decisions about hyphenation, ligatures, and spacing.
  • Users can apply styles to languages in their style sheets (useful for editors).
  • Google and other search engines can use this information when indexing text.
  • Could be useful for application developers who re-publish Wikipedia.
  • Could be useful for research or compiling statistics about language use in Wikipedia.

[edit] Applying styles

You can apply CSS styles in your user style sheet. Registered users can put styles into User:XXX/monobook.css, where XXX is the user name.

These examples will not work in Internet Explorer, because it doesn't support attribute selectors. Try Firefox.

Example: to apply a font to Russian-language text:

 span[lang|=ru] { font-family: fonteskaya; }

Example: to apply a colour to text marked with any language:

 span[lang] { color: green; }

Note: don't use quotation marks in your your user style sheet. Wikitext will screw them up. They are recommended in CSS, but not required.

[edit] See also

[edit] References

[edit] Discussion

[edit] lang-ru, lang-ar, ...

There are two templates right now that have similar functionality, lang-ru and lang-ar. (There may be others; these are the only two I know of). In addition to adding the span tag, these templates also prefix the encompassed text with the name of the language and a link to the relevant Wiki article.

I was thinking these two templates could be rewritten in terms a simpler "lang" template, in the form:

[[{{{2}}} language|{{{2}}}]]: <span lang="{{{1}}}" xml:lang="{{{1}}}">{{{3}}}</span>

This would be used like:

{{lang|ar|Arabic|لرررررل}}

And produce something like:

Arabic: لرررررل‎

But then I found that this similar lang template already exists. Since this template doesn't seem to be used in too many places, would any of its authors mind if I rewrote it to work like the above? Or perhaps this template could be left as-is and a "langWithName" template could be created for the above. What do people think?

 — J’raxis (T) 18:22:26, 2005-08-03 (UTC)
There's also lang-uk. —Michael Z. 2005-08-3 21:55 Z

In Russian wikipedia, there are a lot of these lang-xx templates (see ru:Википедия:Шаблоны:Языки). They are really handy in that form. As for the current lang template, it should be left as it is — very often foreign words or phrases are inserted many times in the same article, and it would be annoying if they are every time accompanied by (e.g.) German: .... German: .... German: .... — Monedula 05:56, 4 August 2005 (UTC)

Yep, there's a use for both of these types of templates. I'm going to make a new {{langWithName}} template and rewrite the three lang-xx ones in terms of it.
— J’raxis (T) 20:09:47, 2005-08-04 (UTC)

[edit] Language templates are being removed

Language templates are being unilaterally removed by one user. Please see related discussion at template talk:lang-uk. —Michael Z. 2005-10-16 22:29 Z

[edit] span lang vs. font lang

Can anybody explain or illustrate the difference? Wikipeditor 10:48, 10 January 2006 (UTC)

No real difference at all. But span is preferable, since it does not suggest that it is about fonts. Formerly, Wikipedia did not allow the use of span, so font was used instead. — Monedula 11:11, 10 January 2006 (UTC)
Thank you! I see either tag's main use in helping the browser to choose an appropriate font, as mentioned above. I gather from your reply that there aren't really any situations where font lang is more appropriate than span lang.—Wikipeditor
In fact, the font tag is deprecated in HTML 4.0 and absent in XHTML. — Monedula 06:39, 13 January 2006 (UTC)

[edit] What should be tagged?

Question: should we mark transliterations? (I think not) —Michael Z. 2005-01-27 10:17 Z

Why not? IMHO in the general case is more important to tag transliterations than "original" words (words written with a different script are obviously not in English). --surueña 10:38, 10 March 2006 (UTC)
Because it looks bad. Example:
A user chooses in their Firefox options to show "Western" (i.e. English and such languages) text in the font Gentium, Cyrillic text in the font Georgia, and Simplified Chinese text in the font SimSun or SimHei.
Now when this user sees a word in Cyrillic letters (e.g. Југославија), it will appear in Georgia characters if the template:lang is used, and as an irritating mix of Gentium characters (those whose shape also occurs in the Latin alphabet: Ј, о, с, а, ј) and Georgia characters (specifically Cyrillic characters: у, г, л, в, и) if it is not used.
When the same user sees a Hanyu Pinyin romanisation (e.g. Bái Máo Nǚ), it will be displayed in ugly SimSun or SimHei if the template is used to mark it as zh-CN, or in highly legible Gentium if not.
If it weren't for this problem, I agree that it wouldn't make much sense to treat romanised text in a foreign language as Western, e.g. to tag pinyin as English in an article in the Chinese Wikipedia.
Wikipeditor 18:39, 10 March 2006 (UTC)
Screenshot with Firefox 1.5 under Linux
Screenshot with Firefox 1.5 under Linux
I'm mainly interested in this template for accessibility reasons (using the lang attribute is an important point specified in the Web Content Accessibility Guidelines)[3] because text-to-speech browsers need to know the language of every (the pronunciation of an English word is very different from a French one, for example).
But you are right, if it's looks ugly nobody will use it. Once I tried to use Unicode numerals[4] instead of plain ASCII letters (yes, to allow screen readers pronounce "the second" instead of "/i i/"), but in my browser (Firefox 1.5) it was illegible in boldface:
Ferdinand II -> Ferdinand Ⅱ
Maybe a new template should be created for transliterations? --surueña 20:17, 10 March 2006 (UTC)
On a related note, do you think there is a way to use ISO 15924 to have Simplified or Traditional Chinese appear as such in Wikipedia articles, instead of using ISO 3166-1 alpha-2? It feels so wrong to use country codes sometimes.
Wikipeditor 18:39, 10 March 2006 (UTC)
I've never heard about that before, sorry. Maybe a new template like Template:Polytonic can be created for that. However, from the accessibility POV, it's not very useful to specify the script instead of the language. I mean, it's OK to create accessible templates like Template:Polytonic, because it "specifies the script" (through class="polytonic", i.e. useful to style sheets but this isn't a HTML standarized method to indicate the script) as well as the language. Please, don't create templates that only specify the writing system.
But you are OK, I don't think it's a good solution to tag Traditional Chinese with zh-tw. and Simplified Chinese with zh-cn. --surueña 20:17, 10 March 2006 (UTC)
Yes, it seems the W3C recommends the use of zh-Hant and zh-Hans language codes for Traditional and Simplified Chinese respectively, i.e. the ISO 3166-1 alpha-2 language tag followed by the ISO 15924 script tag, as you suggest.[5] I just modified some templates like Template:Chinese to follow this guidelines. It seems the language tags are richer than I expected, as there is a standard procedure to specify after the language the script, region, variant and even a private tag, see [6] --surueña 10:28, 21 September 2006 (UTC)

I've come to the conclusion that all text in another language should be marked as that language. The HTML lang attribute does not indicate character set or alphabet, merely language—how it's displayed is a browser issue. So I would use the template for, e.g., both Cyrillic and romanized versions of a name in Ukrainian: {{lang |uk|Україна, ''Ukrayina''}}, yielding: Україна, Ukrayina.

Regarding Firefox's mixed-font display, I don't think this should happen if the name is entered correctly. Please note that no Unicode letters occur in both Cyrillic and Latin alphabets. Don't use Latin a in place of Cyrillic а! How does this appear in Firefox?

  • without template: Југославија
  • with lang|mk: Југославија

Won't Firefox just switch to a different font if necessary even when you don't specify it? Safari displays everything on this discussion page correctly in Lucida Grande, without any font shifts, and it doesn't even ask the user choose fonts for different scripts. Why not pick a broad Unicode font like Lucida Grande, Arial Unicode, or Gentium as your default font for everything? —Michael Z. 2006-03-10 23:02 Z

It seems to be a font issue. When I set Firefox to use a serif font and make Gentium the standard serif font for both Western and Cyrillic, the following happens:
  • Regular and bold text: у, г, л, в, и are displayed correctly (in the default font for Cyrillic where the template is used, in the default font for Western where it is not. In this case, Gentium is both.)
  • Italic and italic bold text: у, г, л, в, и are displayed in the default sans font for “other languages”. All other letters are displayed in Gentium.—Wikipeditor
Strange; Gentium does have an italic font: are you sure you have the italic version installed? And come to think of it, Gentium only has enough Cyrillic letters for Russian and Bulgarian, so it's just not a great choice for an international font if you're going to need other Cyrillic-alphabet languages. Sorry.
I think Arial Unicode has a pretty good range, although it displays a few characters incorrectly (see #Affricates and double articulation). —Michael Z. 2006-03-11 03:47 Z
Screenshot with Firefox 1.5 under Linux
Screenshot with Firefox 1.5 under Linux
This is how I see it in my machine. They are rendered with different fonts (see the J), maybe too big when the language tag is used. Both look OK to me, don't you think?
--surueña 11:50, 11 March 2006 (UTC)


I propose to use these language templates with every foreing word, i.e. words that currently should be put in italics in Wikipedia (except those commonly used in English, see Wikipedia:Manual of Style#Loan words) but also with foreing proper names (but I'm not completely sure). However, as Wikipeditor has said, they sometimes looks very bad, for example look the following test I made to Akira (film):

Screenshot with Firefox 1.5 under Linux
Screenshot with Firefox 1.5 under Linux

'''''{{lang|ja|Akira}}''''' ({{lang-ja|アキラ}}) is a ...

Note that the title not only looks ugly, it's not even in italics (and every title should be put in italics, see Wikipedia:Manual of Style (titles)). The Akira at the bottom is rendered right because it doesn't have any lang attribute.

It's very important for accessibility reasons that every foreing word is marked with the proper language, but if it looks like so bad nobody will use it. Maybe we can create another template for romanized words:


<span lang="{{{1}}}" xml:lang="{{{1}}}" class="romanization">{{{2}}}</span>

and a new standard style for that class that uses the right font (a font with all diacritical marks, needed in words like rōmaji). Maybe a good name for this template could be Template:latn (for latinization), or Template:rom (for romanization). Transliteration is not a good name because it seems that can be used between any two writing systems, as we want to refer only with latinized words. But I'm not very good choosing template names!, please help me out with that :-) See also: Template:IPA, Template:Unicode, Template:polytonic, Template:Nihongo, Template:Zh-all, Template:Ruby, Template:Ivrit, Template:ArB, Template:ArTranslit --surueña 12:41, 11 March 2006 (UTC)

Proper names should not be tagged. That's overkill, and they are not in a foreign language.
A separate template for romanized text would just confuse things. There is no correct font for romanized words; different platforms have different sets of fonts, and choose how to display them differently. Everything on this page looks right in my Safari. You are just making a workaround for the selection of fonts and display settings of your Firefox (or whatever). This is a system and browser configuration problem, and it shouldn't be worked around by injecting custom HTML and styles into Wikipedia. —Michael Z. 2006-03-11 16:25 Z
"Proper names should not be tagged. That's overkill, and they are not in a foreign language."
I'm not sure about that. The pronunciation of a name depends on its language, but maybe in practice the best behavior is to pronounce it like an English speaker, and refer to the phonetic notation if you want the native pronunciation. Maybe an accessibility expert can help with this.
Of course there is not a specific font for romanization characters, I was talking about using a widely available font in the MediaWiki:Common.css. I agree with you that the romanization template is only a hack (as well as Template:polytonic and Template:Unicode), but nowadays browsers have some limitations and those problems should be circumvented. The best option is to use Template:lang for everything, but this is problematic for a high number of users. Also, I've checked the above examples with Firefox 1.5 under Windows and it looks much better, but still not perfect. The rendering with Internet Explorer 6.0 is nearly the same.
So, Michael Z., in your opinion, what's the best policy? Use the lang template only for words in different scripts? For every foreign word (except proper nouns)? This last option in my opinion is problematic, you know. --surueña 17:33, 11 March 2006 (UTC)
Well, we could formulate all sorts of complicated rules: "Antonín Dvořák" should be pronounced as by a Czech, "August Dvorak" as by an American, etc. Should "Paris" be pronounced in French, even though it has its own English pronunciation? Pages of discussion and many revert wars would ensue, and screen readers probably wouldn't support any of the results anyway. A name is a name; it is not text in a foreign language. If a screen reader supports a database of foreign names, it will choose its own pronunciation for them; if it doesn't, then there's no point in our trying to coach it.
Regarding some of those other templates mentioned above:
Template:IPA, Template:Unicode, and Template:polytonic are necessary workarounds for a bug in MSIE/Windows; certain text will not display at all in MSIE/Win without these templates. The fix is performed by a style sheet rule which is hidden from all other browsers, so these templates do not affect display in any other browser (although they do allow you to use your user style sheet to alter the display; e.g. I have IPA displayed in green).
Template:Nihongo breaks accessibility by injecting junk text into the page and then hiding using CSS. This is bad, and it should not be used.
I can't tell what template:ZH-all is, and there is no documentation.
Template:Ruby breaks the validation of both the HTML and CSS of pages, by injecting non-HTML (MSIE-specific) tags into the page, and by incorporating a CSS hack which doesn't survive wikitext rendering. This should not be used.
All of these things display correctly in my browser. If your browser has a bug or problem that mixes up the fonts a bit, 1) please don't add code to the page that changes the display in my web browser to fix the display in yours, 2) editors should not be required to add specialized tags just for this purpose. —Michael Z. 2006-03-11 17:56 Z
Sorry for the delay, but I'm somewhat busy these days… I've been thinking about the Template:lang and the Template:rom, and although a template for romanized words can be a good solution to currently solve the font problems of some browsers, you are right that this can be hard to use by editors (and this is only a short-term solution for the problems found in some Linux distributions AFAIK) and probably will not help voice browsers (probably each transliteration should be tagged with a different template to choose the good pronuntiation, and this could be a real nightmare.
I'm not an expert about accessibility, although I've read some articles in my free time about Web Accessibility, Universal Design and Device Independence, and made some web pages WCAG 1.0-AA compliant. I also have some knowledge about assistive technologies, but I've never used a screen reader or voice brower. Do you know how JAWS and other common assistive techonologies use the lang attribute?
In summary, Template:lang should be used for every non-English words, regardless of the script. But, I'm still not sure about:
* Book and film titles: Amistad (film), El Ingenioso Hidalgo Don Quixote de la Mancha
* Names of places: Palazzo Pitti
* Names of non-English instituions: Real Academia Española
* Words in two or more languages, see Template:lang-ru/uk
Also, I suppose that when talking about the origins of words, nearly all of them must refer to Ancient Greek (Template:polytonic), i.e. it's wrong to tag it merely as Greek ({{lang|el|…}}) because it would refer to modern Greek.
--surueña 09:27, 16 March 2006 (UTC)

[edit] Interwiki

please add es:Plantilla:Lang to the interwiki --Yonghokim 21:37, 22 April 2006 (UTC)

Done.—Ëzhiki (ërinacëus amurënsis) • (yo?); 04:37, 23 April 2006 (UTC)

Please add bg:Шаблон:lang. Thanks. --Petar Petrov 10:44, 29 December 2006 (UTC)

Done Metros232 15:14, 30 December 2006 (UTC)

[edit] Overspecifying

Keeping in mind the W3C's golden rule, what is the purpose of the following additions?

Slang words are typical examples of terms used only in some regions, for example the Mexican Spanish word chale:

This is not an example like Taiwanese, where the language script is used differently in a different location. It's merely a local word. We're not going to add a language tag to every English regionalism in Wikipedia, nor should we promote the needless practice of labelling regionalisms in foreign words as if they belonged to yet another language.

Changes in script must always be specified (when not inferred from the language), even when the language doesn't change. The following example shows this for text always in English: ... In the sign can be read the word {{lang|en-Brai|⠃⠗⠊⠇⠇⠑}}, which means "braille".

Does this come from any W3C guideline? It seems to me that the language (en) is already specified for the page, and the fact that the script is braille should be inferred by any Unicode-capable web browser. Adding a language tag is superfluous. (Anyway, since this is not a braille encyclopedia, better style would be to write "the word braille, itself written in braille."

I'm going to remove these examples from the page, pending evidence that they represent good practice. —Michael Z. 2006-09-26 01:35 Z

I'm agree with you, both examples weren't very good. In the first, I wanted to put another example to show that the script isn't needed when specifying the variant. And currently, with the example of Taiwan, this isn't very clear. As a side note, in my opinion the example of Taiwan isn't very good neither, don't reflect why that word is a variant only found in that region (and as far as I know, it isn't, it's also used in any Chinese dialect). For that reason I didn't include any word when I write that example, only the language tag needed in a hipotetical case. I'm a native Spanish speaker, and I know when a Spanish word is a regionalism, but not in other languages.
In the other example, I wanted to put a more exotic case: a non-intuitive script, and also that language tags can be needed for English words. Probably it wasn't very well written, but I still think the idea is good. And isn't an academic example, it seems browsers need to specify those changes in script, otherwise the user won't be able to choose the font she wants (but I haven't make the test, maybe I'm wrong with current browsers). Anyway, I'm happy to see you again, comments are always welcome and you know really about this. Best regards --surueña 19:17, 26 September 2006 (UTC)
I understand the desire to be exhaustive with the examples, but don't worry: sooner or later an editor will come here and add a real example which they used. These are both unusual cases, and if the need arises, a solution will come. In the meantime, simpler instructions are always better.
I think Taiwanese script has to be indicated because some of the characters are different, or have different meaning: it's a technical difference that the browser/OS needs to be aware of for correct rendering, and not an indicator to the reader that the content uses local vocabulary—but "Taiwanese language" doesn't really offer much information about this.
Perhaps en-brai should be used for braille text, but I think the Cyrillic and transliterated Russian example is sufficient to illustrate the same point as in the braille example.
Regarding the browser choosing script, I suggest you test with a few different browsers. I find that Safari and Firefox render almost anything correctly as long as the OS has an appropriate font installed, while Internet Explorer is brain-dead about blocks of text from different Unicode ranges, and requires font-specification hacks like template:IPA and template:Unicode to be used in Wikipedia, although even these sometimes fail. —Michael Z. 2006-09-27 01:45 Z
After reading the article about "Taiwanese language" I think the example is even more misleading, because somebody can understand TW is used for dialects, where in fact the correct tag in that case would be zh-min-nan-Hant. Isn't a good idea to use a macrolanguage for explaining this subtag, and maybe it would be better if we don't explain them. Anyway, I think the 99% of editors writing articles with loan words will use only the language code, and less frequently maybe the script code and the rtl writing direction. I think the variant subtag it's very specialised. However, although it's true the variant code isn't an indicatior for the reader, it is an indicator for a spell checker.
I'm interested in which cases template:IPA and template:Unicode sometimes fail. I want to use a similar technique for improving language templates: to add an optional second parameter to language templates written in a non-Latin script to ease adding the trasliteration. For example {{lang-ru|Москва́|''Moskva''}}, where the second parameter is optional for backwards compatibility, will generate the following code:
[[Russian language|Russian]]: <span lang="ru" xml:lang="ru">Москва́</span>, [[Romanization of Russian| translit.]]: <span lang="ru-Latn" xml:lang="ru-Latn" class="Unicode"><i>Moskva</i></span>
--surueña 22:25, 28 September 2006 (UTC)
It can't ever be simple, can it!? I thought the Taiwanese example would be safe because the W3C uses it in their overview page. Oh, well.... This stuff is new anyway, I'm sure more will be published on the subject, or conventions will emerge eventually.
IPA and its friends sometimes fail to render particular characters because different fonts include different characters, and no one seems to be the best. One of the Windows XP default fonts with the widest range of supported characters has a bug and renders double-width combining tie bars incorrectly. You can read the details on the templates' talk pages. Or use Firefox and forget about it forever. (I use a Mac so I never suffer from any of the MSIE font bugs, but ironically I've done much of the implementation of these templates just so we could abandon ugly, confusing SAMPA and just use proper Unicode characters in Wikipedia.)
The extended template with transliteration sounds like a very good idea. —Michael Z. 2006-09-29 03:42 Z
I'm a bit late to join in, but examples for regional variants could be:
  • Poetry or other texts written in Classical Chinese by Koreans (i.e. most pre-1900 texts from Korea) that could be displayed using Korean variants, for example {{lang|zho-Hant-KR|平}} instead of {{lang|zho-Hant|平}}: printed texts for use in Korea usually use the variant where the small strokes point upwards (/\), whereas in texts printed for use in China, I think the other variant (\/) is more common. One problem is that old prints often don't use the standard variants of today, another is that the use of KR would be an anachronism in many cases. Anyhow, as long as browsers give precedence to language tags over script tags, we must act as if those texts were Korean language: {{lang|ko-Hant|平}} = 平.
  • Swiss texts use ss in words where other standards use ß, but unlike the above Korean example, regional information (i.e.-CH/-FL) is of course unnecessary for such words to be correctly rendered by an application.
I'm sure there are better examples, but I can't think of any right now. Wikipeditor 13:13, 16 October 2006 (UTC)
Better late than never! :-) And any example can help, because this is a difficult topic. Actually, after thinking about this for some days I believe this is probably too much specialised for the Wikipedia (and maybe more appropriate for the Wiktionary?). At least from my POV, we should start tagging only the language, and the script when needed (not an easy task, though), removing from the documentation the part about regional variants or at least stating this is needed rarely.
But I think your examples are interesting. I believed regional variants are only useful to spell checkers, but you showed more uses. Maybe in the future. However, I don't agree with you in the example about Korean poetry: altough a Chinese text is printed with a Korean font the language is still Chinese, so the subtag must be zh instead of ko. We must circunvent browser bugs when we can, but in this case we are tagging the text with a wrong tag and not with a compatible one. Anyway, it will be interesting to known the behavior of current browsers (and other user agents :-) regarding language tags. I still working with the Template:lang-ru test and lang-uk test templates (to busy theses days), I hope to have time to make some tests also with IE. I will keep you informed. --surueña 20:37, 16 October 2006 (UTC)

[edit] ISO 639; more exactly

I was trying to use {{lang-gla}} and did not realise for some time we have {{lang-gd}}. I think we should specify more exactly which codes to use to name templates. Namely, should we use ISO 639-1, ISO 639-2 or ISO 639-3? Then perhaps create redirects from other used codes. --Eleassar my talk 13:02, 22 December 2006 (UTC)

"The golden rule when creating language tags is to keep the tag as short as possible",[7] so ISO 639-1 is preferred over ISO 639-2 and ISO 639-3. Also, some browsers only recognize alpha-2 codes. Best regards --surueña 00:27, 25 December 2006 (UTC)
Retrieved from "http://en.wikipedia.org../../../l/a/n/Template_talk%7ELang_f854.html"