Skantlyn:Lang
Skantlyn:High-use Skantlyn:COinS safe Lua error in Module:Lua_banner at line 113: attempt to index field 'edit' (a nil value). Skantlyn:Language templates
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 promptweb browsersto use a more appropriate font or screen readers to use a particular kind of pronunciation and so on. See§ Rationalefor more information.
Syntax and usage
[pennfenten]Skantlyn:In5{{lang|Skantlyn:Var|Skantlyn:Var}}
TheSkantlyn:Varshould consist of anISO 639language code. The template supports properly formattedIETF language tagsusing subtags that identify the language's script, region, and/or variant. The ISO 639 language code is a two- or three-letter abbreviation, in lowercase, of the language's name. French, for example, has the codefr
:
She said: "{{lang|fr|Je suis française.}}"
→ She said: "Script error: No such module "Lang"."
Because all languages represented by two-letter codes inISO 639-1can also be represented by their three-letter equivalents inISO 639-2and 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'sfra
code, use the 639‑1 codefr
instead. Likewise, script, region, and variant information should be included only when they provide a necessary distinction. For an up-to-date list of available language, script, region, and variant codes, please refer to theIANA'slanguage subtag registry.
By default, this template will place articles into the relevant subcategory ofSkantlyn:Category link.To suppress this – e.g. when usingSkantlyn:Tlfwithin awikilinkor thetitleparameter of a citation – add the parameter|nocat=true
.
Formatting
[pennfenten]Automatic italics
[pennfenten]Skantlyn:Tldautomatically applies italic stylingwhen the text in{{{2}}}
is written entirely in theLatn
script (the Latin Alpha bet and its extensions), either when that is the default encoding for the language or when it is triggered by aSkantlyn:Var-Latn
language code:
{{lang|fr|Je suis française.}}
→Script error: No such module "Lang".''{{lang|fr|Je suis française.}}''
→Script error: No such module "Lang".– external markup is ignored{{lang|he-Latn|la`az}} ({{lang|he|לעז}})
→Script error: No such module "Lang".(Script error: No such module "Lang".)''{{lang|he-Latn|la`az}}'' (Skantlyn:!mxt)
→Script error: No such module "Lang".(Script error: No such module "Lang".) – external markup is ignored around thehe-Latn
text, but will incorrectly italicize the Hebrew-character material.
WhenLatn
script should not be italicized, there are multiple approaches:
|italic=no
– renders{{{2}}}
in upright font; italic markup around the template is ignored; italic markup inside the template causes an error message:
{{lang|fr|Je suis française.|italic=no}}
→Script error: No such module "Lang".''{{lang|fr|Je suis française.|italic=no}}''
→Script error: No such module "Lang".''{{lang|fr|Je suis ''française''.|italic=no}}''
→Script error: No such module "Lang".– italic markup in conflict with|italic=no
|italic=unset
– disables template-provided styling;{{{2}}}
is styled according to external or internal wiki markup:
{{lang|fr|Je suis française.|italic=unset}}
→Script error: No such module "Lang".''{{lang|fr|Je suis française.|italic=unset}}''
→Script error: No such module "Lang".{{lang|fr|''Je suis'' English.|italic=unset}}
→Script error: No such module "Lang".
{{noitalic}}can also be used:
{{lang|fr|Je suis {{noitalic|English}}.}}
→Script error: No such module "Lang".
Language-specific templates
[pennfenten]There are 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...
→ Akremlin(Skantlyn:Lang-ru,'castle') is a major fortified central complex...
While{{lang-Skantlyn:Var}}templates output text in italics for languages with Latin-based scripts, if plain text is required, such as for proper names,|italic=no
or{{noitalic}}may be used:
the border town of Ventimiglia ({{lang-fr|Vintimille}})
→ the border town of Ventimiglia (Skantlyn:Lang-fr)the border town of Ventimiglia ({{lang-fr|italic=no|Vintimille}})
→ the border town of Ventimiglia (Skantlyn:Lang-fr)the border town of Ventimiglia ({{lang-fr|{{noitalic|Vintimille}}}})
→ the border town of Ventimiglia (Skantlyn:Lang-fr)
When formatting foreign-language text to match style guidelines, it is best to exclude the styling markup from the template, so that any extraneous markup which is not from the foreign language does not receive incorrect metadata for that language. This includes: 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 when possible.
Right-to-left languages
[pennfenten]To embed a string of right-to-left text (such asArabicorHebrew) within the usual left-to-right context,|rtl=yes
should be added to correctly communicate writing direction. For convenience, the {{rtl-lang}} template accomplishes the same result by automatically including|rtl=yes
.To markup a whole paragraph of right-to-left text, {{rtl-para}} should be used instead.
Any of these approaches will wrap the text in a container with thedir= "rtl"
attribute. In order to ensure correct rendering in browsers that do not fully supportHTML5bidirectional isolation,aleft-to-right markis also added to the end of the text (see theW3Cfor details).
Note that text direction does not need to be specified when using the{{lang-Skantlyn:Var}}templates, as this is implied by the template's language. Therefore there is noSkantlyn:Tlf,only {{lang-ar}}.
Parameters
[pennfenten]Skantlyn:Lang-x/doc/parameters
the function selector parameter
[pennfenten]{{lang}}uses the Lua functionlang()
Module:Lang.That module also supports all of the{{lang-??}}templates using the Lua functionslang_xx_inherit()
andlang_xx_italic()
.The module has other functions that may be useful. The function selector parameter|fn=
tells module:lang which function to execute. The available functions are:
is_ietf_tag
– returnstrue
if the providedIETF language tagis valid; nil else{{lang|fn=is_ietf_tag|nv}}
→Script error: No such module "Lang".←{{lang|fn=is_ietf_tag|xx}}
→Script error: No such module "Lang".←
is_lang_name
– returnstrue
id the provided language name is valid; nil else{{lang|fn=is_lang_name|navajo}}
→Script error: No such module "Lang".←{{lang|fn=is_lang_name|xxxxx}}
→Script error: No such module "Lang".←
lang
– the function that renders{{lang}};listed here for completeness, this particular usage is more-or-less pointlesslang_xx_inherit
– the function that renders{{lang-??}}template where the text is not italicized; can be used when a{{lang-??}}template, for example{{lang-aao}},does not exist for a particular language:{{lang|fn=lang_xx_inherit|code=aao|Algerian Saharan Arabic text}}
→Script error: No such module "Lang".
lang_xx_italic
– the function that renders{{lang-??}}template where the text is italicized; can be used when a{{lang-??}}template, for example{{lang-svc}},does not exist for a particular language:{{lang|fn=lang_xx_italic|code=svc|Vincentian Creole English text}}
→Script error: No such module "Lang".
name_from_tag
– returns the language name associated with the provided IETF language tag:{{lang|fn=name_from_tag|apa}}
→Script error: No such module "Lang".
tag_from_name
– returns the ISO 639 language code (sometimes IETF language tag) associated with the provided language name:{{lang|fn=tag_from_name|havasupai}}
→Script error: No such module "Lang".
transl
– the function that renders{{transl}};listed here for completeness, this particular usage is more-or-less pointless{{lang|fn=transl|ar|DIN|al-Ḫawārizmī}}
→Script error: No such module "Lang".
Indicating writing script
[pennfenten]If necessary, anISO 15924script 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 inArabic(Arab
),Latin(Latn
), andCyrillic(Cyrl
) scripts, making it necessary to always specify which script is in use. In such a case, taking care to preserve the script code'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 (Skantlyn:Rtl-lang,Script error: No such module "Lang".,Script error: No such module "Lang".)
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 specifyru-Cyrl
,just asen-Latn
would be unnecessary for English. Thesubtag registrycontains up-to-date information on which languages have common script codes that should be "suppressed".
Transliteration
[pennfenten]To mark a language which has beentransliteratedfrom 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 beru-Latn
.If the transliteration scheme is known, and listed as a "variant" in thesubtag registry,it can be appended after any script and region codes. For example, Chinese transliterated into a Latin script using thepinyinsystem would bezh-Latn-pinyin
.As a convenience for transliterating to Latin scripts, and to work around browser styling issues with some language and script combinations, {{transl}} may be used in place ofSkantlyn:Tlf:
Moscow ({{lang|ru|Москва́}}, {{transl|ru|Moskva}})
- Moscow (Script error: No such module "Lang".,Skantlyn:Transl)
To specify a transliteration scheme, such as theISO transliteration standard for Cyrillic,useSkantlyn:Tlc.
Undetermined language
[pennfenten]TheSkantlyn:Tlftemplate 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 thegraphemeitself, theISO 639‑2language codeund
,for Undetermined language, should be used:
The {{lang|und-Hani| tự }} Han character has 6 strokes.
- TheScript error: No such module "Lang".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 isHani
,which specifies generic Han characters (Hanzi, Kanji, Hanja).
Compare {{script}} usage:
The {{script|Hani| tự }} Han character has 6 strokes.
- TheSkantlyn:ScriptHan character has 6 strokes.
Indicating regional variant
[pennfenten]When it is necessary to indicate region-specific language, anISO 3166-1 Alpha -2country code, orUN M49region 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 aspt-BR
,and Spanish as used in Latin America ases-419
.
Additionally, language, script, and region codes can all appear in the same tag. For instance, the codezh-Hant-TW
should be used for Chinese text written withTraditional Han characters,containing words or expressions specific toTaiwan:
Taiwan ({{lang|zh-Hant-TW| Đài Loan }}, {{transl|zh|Táiwān}})
- Taiwan (Script error: No such module "Lang".,Skantlyn:Transl)
Rationale
[pennfenten]Wikipedia:Manual of Style/Text formatting § Foreign termsrequires the use of {{lang}} instead of manual ''italics''. This is preferred for the following reasons:
- Webbrowserscan use the information in suchmultilingual support templatesto choose an appropriate font.
- This is great forCJKwhere 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: seeHan unification § Examples of language-dependent glyphsandthese comparison tables with a screenshot.
- Foraccessibility–screen readersneed language info to speak text in the correct language – and to satisfyWikipedia accessibility guidelines.[2]
- Forspell checkersand grammar checkers, to match the text to the dictionary and syntax of the correct language.
- To help browsers choose appropriatequotation marks,[3]and make decisions abouthyphenation,[3]ligatures,[4]and spacing.[3]
- Users can apply styles to languages in theirstyle sheets(useful for editors).
- Search enginescan use this information wheninde xingtext.
- Facilitates better data-scraping, parsing and re-use.
- Useful for application developers who re-publish Wikipedia (also seeWikipedia:Manual of Style/Accessibility § Other languages).
- Useful for research or compiling statistics about language use in Wikipedia.
Applying styles
[pennfenten]Registered users can apply customCSSstyles to articles by placing style declarations in their user style sheet. The user style sheet can be created atSpecial:Mypage/common.css.For more information, seeHelp:User style.The following examples should work in mostmodern browsers,but not inInternet Explorer 8or earlier, which lack support for attribute selectors.
To apply a specific font to all text marked as Russian of any script or region:
[lang|=ru]{font-family:fonteskaya;}
/* or */
:lang(ru){font-family:fonteskaya;}
To apply a specific font to text marked simply as Russian:
[lang=ru]{font-family:fonteskaya;}
To apply a color to all text marked with any language:
[lang]{color:green;}
If a font name contains characters besides basic Latin letters or hyphens, it is a good idea to enclose it in quotation marks because some such characters have special meanings (the most common case needing quotation marks is a multi-word font name with space characters). Quotation marks are also required for font families containing generic-family keywords ('inherit', 'serif', 'sans-serif', 'monospace', 'fantasy', and 'cursive'). See theW3Cfor more details.
You can combine this with font imports in your user stylesheet, for example, to show all German text inFrakturand all Urdu inNotoNastaliqUrdu Regular:
@importurl(https://fonts.googleapis.com/css?family=UnifrakturMaguntia);
@importurl(http://fonts.googleapis.com/earlyaccess/notonastaliqurdudraft.css);
:lang(de){
font-family:UnifrakturMaguntia;
font-style:normal;
font-weight:normal;
}
:lang(ur){
font-family:"Noto Nastaliq Urdu Regular","Noto Nastaliq Urdu";
}
then the following wikitext will look like the image below:
Victor jagt zwölf Boxkämpfer quer über den Sylter Deich {{lang|de-Latf|Victor jagt zwölf Boxkämpfer quer über den Sylter Deich}} ٹھنڈ میں، ایک قحط زدہ گاؤں سے گزرتے وقت ایک چڑچڑے، بااثر و فارغ شخص کو بعض جل پری نما اژدہے نظر آئے۔ {{lang|ur|ٹھنڈ میں، ایک قحط زدہ گاؤں سے گزرتے وقت ایک چڑچڑے، بااثر و فارغ شخص کو بعض جل پری نما اژدہے نظر آئے۔}}
Tracking categories
[pennfenten]- Skantlyn:Category link with count
- Skantlyn:Category link with count
- Skantlyn:Category link with count
TemplateData
[pennfenten]TemplateData for Lang
Indicate that a given span of text belongs to a particular language. Allows browsers to correctly present and pronounce foreign languages.
Parameter | Description | Type | Status | |
---|---|---|---|---|
Language tag | 1 code | A language tag, or an ISO 639 language code.
| String | required |
Text | 2 text | The text belonging to the language specified.
| String | required |
Right to left | rtl | Indicates that the language should be displayed from right to left.
| String | optional |
Italicize | italic italics | Italicizes the text
| Boolean | optional |
Font-size | size | sets font-size
| Unknown | optional |
nocat | nocat | no description | Unknown | optional |
See also
[pennfenten]- {{Lang-x}}
- Category:Wikipedia multilingual support templates
- Lists 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 Alpha bet)
- {{script}} (for specific characters)
- {{wikt-lang}} (to simultaneously tag text as a language and link to Wiktionary)
- {{in lang}} (for visually marking external links to foreign-language content)
References
[pennfenten]- ↑"Language tags in HTML and XML"atWorld Wide Web Consortium
- ↑Heilmann, Chris (13 Mar 2008)."Yahoo! search results now with natural language support".Yahoo! Developer NetworkBlog.Kovskrifys aan derowelwar 25 Jan 2009.https://web.archive.org/web/20090125024422/http://developer.yahoo.net/blog/archives/2008/03/yahoo_search_re.html.Kyrghys 28 Feb 2015.
- ↑3.03.13.2Ishida, Richard (18 November 2014)."Why use the language attribute?".World Wide Web Consortium.http:// w3.org/International/questions/qa-lang-why.Kyrghys 1 Mar 2015.
- ↑"6.4 Ligatures: the font-variant-ligatures property".CSS Fonts Module Level 3 W3C Candidate Recommendation 3 October 2013.http:// w3.org/TR/css3-fonts/#font-variant-ligatures-prop.
External links
[pennfenten]- 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
- Mozilla Firefox