Difference between revisions of "Template:Lang/doc"
imported>Quoth-22 (Rewrote some sections for grammar and clarity, made example styles consistent, added more examples, tried to clarify process of picking between ISO 639-1 and 639-2 language codes) |
imported>Cabayi (rm unicode, defunct) |
||
| Line 143: | Line 143: | ||
* {{tl|Cleanup-lang}} (for articles which should use this template, but do not yet) | * {{tl|Cleanup-lang}} (for articles which should use this template, but do not yet) | ||
* {{tl|transl}} (for romanisation of languages not natively written in the Latin alphabet | * {{tl|transl}} (for romanisation of languages not natively written in the Latin alphabet | ||
| − | * | + | * {{tl|script}} (for specific characters) |
* [[:Category:Language icon templates]] (for visually marking external links to foreign-language content) | * [[:Category:Language icon templates]] (for visually marking external links to foreign-language content) | ||
Revision as of 06:58, 29 April 2016
| This is a documentation subpage for Template:Lang. It contains usage information, categories and other content that is not part of the original template page. |
| This template is used on approximately 264,000 pages. To avoid major disruption and server load, any changes should be tested in the template's /sandbox or /testcases subpages, or in your own user subpage. The tested changes can be added to this page in a single edit. Consider discussing changes on the talk page before implementing them. Transclusion count updated automatically (see documentation). |
| This template should not be used in citation templates such as Citation Style 1 and Citation Style 2, because it includes markup that will pollute the COinS metadata they produce; see Wikipedia:COinS. The features of this template will be added to the citation templates in the next update. |
The purpose of this template is to indicate that a span of text belongs to a particular language. It often makes no visible changes to the text, but can prompt web browsers to use a more appropriate font, or screen readers to use a particular kind of pronunciation, and so on. The Script error: No such module "Section link"., below, provides more information.
Contents
Syntax and usage
{{lang|language tag|text}}
The language tag should consist of an ISO 639 language code, optionally extended to indicate a language's script or region. The language code is usually a two- or three-letter abbreviation, in lowercase, of the language's name. French, for example, has the code fr:
She said: "''{{lang|fr|Je suis française.}}''"
- She said: "Je suis française."
Because all languages represented by two-letter codes in ISO 639‑1 can also be represented by their newer three-letter equivalents in ISO 639‑2 and above, it is recommended to use the shortest language tag possible that sufficiently describes the target language.[1] So while French could be represented by 639‑2's fra code, 639‑1's fr should still take precedence. Likewise, script and region information should only be included when they make a necessary distinction.
It is better to only include the foreign-language text (linked if appropriate) inside the template, so that any extraneous markup which is not from the foreign language does not receive incorrect metadata for that language:
- Use
''{{lang|it|[[goriziana]]}}'' - Not
{{lang|it|''[[goriziana]]''}}
This includes italicization of foreign words; English-language quotation marks around titles of works in languages that use other quotation character glyphs; italicization of titles in languages which do not use that convention; and emphasis that is not found (in one style or another) in the original foreign text; among other cases. If in doubt, put such markup outside the template.
By default, this template will place articles into the relevant subcategory of Category:Articles containing non-English-language text. To suppress this – e.g. when using {{lang}} within a wikilink or the title parameter of a citation – add the parameter |nocat=true.
There are also language-specific versions of this template, such as {{lang-fr}} and {{lang-ru}}, which are intended to be used the first time a language appears in an article. These templates will print the language's name and, when appropriate, italicize their content:
A '''kremlin''' ({{lang-ru|кремль}}, ''castle'') is a major fortified central complex...
- A kremlin (Russian: кремль, castle) is a major fortified central complex...
Italics
By default, {{lang}} outputs plain text, while {{lang-xx}} templates (e.g. {{lang-de}}) output text in italics for languages using Latin-based scripts. If plain text is required with the latter, such as for proper names, {{noitalic}} may be used:
... the border town of Ventimiglia ({{lang-fr|{{noitalic|Vintimille}}}})
- ... the border town of Ventimiglia (French: Vintimille)
Indicating writing script
If necessary, an ISO 15924 script code can be appended to a language code to indicate the use of a specific script. For instance, Tajik (tg) is a language which can be found written in Arabic (Arab), Latin (Latn), and Cyrillic (Cyrl) scripts, making it necessary to always specify which script is in use. In such a case, taking care to preserve the script's capitalization, we could end up with the following code (language tags in bold):
Tajik ({{rtl-lang|tg-Arab|تاجیکی}}, ''{{lang|tg-Latn|toçikī}}'', {{lang|tg-Cyrl|тоҷикӣ}})
- Tajik (Template:Rtl-lang, toçikī, тоҷикӣ)
Many languages, however, are so commonly written in one particular script that specifying the script is unnecessary. Russian, for instance, is almost exclusively written in Cyrillic, so there is no need to specify ru-Cyrl, just as en-Latn would be redundant for English. The IANA's language subtag registry contains up-to-date information on which languages have redundant, or "suppressed", script codes.
Transliteration
To mark a language which has been transliterated from one script into another, append the new script's code to the code of the original language. So if transliterating from Russian Cyrillic to a Latin script, the language tag on the transliteration would be ru-Latn. As a convenience for transliterating to Latin scripts, and to work around browser styling issues with some language and script combinations, {{transl}} should be used in place of {{lang}}:
Moscow ({{lang|ru|Москва́}}, ''{{transl|ru|Moskva}}'')
- Moscow (Москва́, Template:Transl)
To specify a transliteration scheme, such as the ISO transliteration standard for Cyrillic, use {{transl|ru|ISO|Moskva}}.
Undetermined language
The {{lang}} template is not only used to specify the language of foreign words, but can also be used to specify a single symbol or character in a script, unrelated to any specific language. Many times the character or symbol is used in several languages, but when the article refers to the grapheme itself the ISO 639‑2 language code und, for Undetermined language, should be used:
The {{lang|und-Hani|字}} Han character has 6 strokes.
- The 字 Han character has 6 strokes.
Han characters are used in Chinese, Japanese, sometimes Korean, and formerly Vietnamese, and in this case the character is not used for any specific language. Note that the script code used is Hani, which specifies generic Han characters (Hanzi, Kanji, Hanja).
Compare {{script}} usage:
The {{script|Hani|字}} Han character has 6 strokes.
- The Template:Script Han character has 6 strokes.
Indicating regional variant
When it is necessary to indicate region-specific language, an ISO 3166-1 alpha-2 country code, or UN M.49 region code, should be added to the language tag, taking care to preserve capitalization. For example, Portuguese (pt) as used in Brazil (BR) could be represented as pt-BR, and Spanish as used in Latin America as es-419. Additionally, language, script, and region codes can all appear in the same tag. For instance, the code zh-Hant-TW should be used for Chinese text written with Traditional Han characters, containing words or expressions specific to Taiwan:
Taiwan ({{lang|zh-Hant-TW|臺灣}}, ''{{transl|zh|Táiwān}}'')
- Taiwan (臺灣, Template:Transl)
Writing direction
To embed a string of right-to-left text (from languages like Arabic or Hebrew) within the usual left-to-right context, you should add the |rtl=yes parameter, so the writing direction can be correctly communicated to browsers. Alternatively, you can use the {{rtl-lang}} template to accomplish the same result, or {{rtl-para}} for marking up whole paragraphs of right-to-left text.
Either of these approaches will wrap the text in a container with the dir="rtl" attribute. In order to ensure correct rendering in browsers that don't fully support HTML 5 bidirectional isolation, they may also add a left-to-right mark at the end of the text (see the W3C for details).
Note that text direction doesn't have to be specified when using the {{lang-xx}} templates, as this is implied by the template's language. There is therefore no {{rtl-lang-ar}}, only {{lang-ar}}.
Rationale
- Web browsers can use the information in such multilingual support templates 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 Script error: No such module "Section link". and these comparison table and screen photo.
- For accessibility – screen readers need language info to speak text in the correct language – and to satisfy Wikipedia accessibility guidelines.[2]
- For spell checkers and grammar checkers.
- To help browsers choose appropriate quotation marks,[3] and make decisions about hyphenation,[3] ligatures,[4] and spacing.[3]
- Users can apply styles to languages in their style sheets (useful for editors).
- Search engines can use this information when indexing text.
- Facilitates better data-scraping, parsing and re-use.
- Useful for application developers who re-publish Wikipedia (also see Script error: No such module "Section link".).
- Useful for research or compiling statistics about language use in Wikipedia.
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 may work in Internet Explorer 8; prior versions do not support attribute selectors. Alternatively, try another browser such as 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; }
Do not use quotation marks in your user style sheet; wikitext would screw them up. They are recommended in CSS, but not required other than for font families containing generic-family keywords ('inherit', 'serif', 'sans-serif', 'monospace', 'fantasy', and 'cursive'). See here for details.
TemplateData
TemplateData for Lang
Indicate that a given span of text belongs to a particular language. Use by browsers which use different styles for different languages.
| Parameter | Description | Type | Status | |
|---|---|---|---|---|
| Language code | 1 | A language tag or an ISO 639 language code.
| String | required |
| Text | 2 | The text belonging to the language specified.
| String | required |
See also
- {{Language}}
- Category:Multilingual support templates
- List of ISO 639 codes (language codes)
- {{ISO 639 name}}
- List of ISO 15924 codes (script codes)
- List of ISO transliterations (transliteration codes)
- {{Cleanup-lang}} (for articles which should use this template, but do not yet)
- {{transl}} (for romanisation of languages not natively written in the Latin alphabet
- {{script}} (for specific characters)
- Category:Language icon templates (for visually marking external links to foreign-language content)
Further information
- W3C
- Language tags in HTML and XML – Overview
- Authoring HTML: Language declarations – Latest W3C Working Draft
- Understanding the New Language Tags
- FAQ: Styling using the lang attribute
- IANA
- IANA Language Subtag Registry
- Tags for Identifying Languages (RFC 4646)
- Matching of Language Tags (RFC 4647)
- Language tags (obsolete per RFC 4646)
- Mozilla Firefox
References
- ↑ "Language tags in HTML and XML" at World Wide Web Consortium
- ↑ Heilmann, Chris (13 Mar 2008). "Yahoo! search results now with natural language support". Yahoo! Developer Network Blog. Archived from the original on 25 Jan 2009. Retrieved 28 Feb 2015. Unknown parameter
|dead-url=ignored (|url-status=suggested) (help) - ↑ 3.0 3.1 3.2 Ishida, Richard (18 November 2014). "Why use the language attribute?". World Wide Web Consortium. Retrieved 1 Mar 2015.
- ↑ "6.4 Ligatures: the font-variant-ligatures property". CSS Fonts Module Level 3 W3C Candidate Recommendation 3 October 2013.