Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Template:Lang/doc: Difference between revisions

Template page
Created page with "{{wikipedia|page name}} {{High-use}} {{COinS safe|n}} {{Documentation subpage}} {{Lua|Module:Lang}} {{Language templates}} {{notice|text=After a discussion in 2024, most of the {{tld|lang-??}} templates were replaced by {{tlx|langx}}}} The purpose of this template is to indicate that a piece of text belongs to a particular language other than that of the page as a whole (by..."
 
No edit summary
Line 8: Line 8:
The purpose of this template is to indicate that a piece of text belongs to a particular language other than that of the page as a whole (by default, English, on this Wikipedia). It can be used inline, or around block-level elements such as <code><nowiki><poem></nowiki></code>, paragraphs, lists, or divs.
The purpose of this template is to indicate that a piece of text belongs to a particular language other than that of the page as a whole (by default, English, on this Wikipedia). It can be used inline, or around block-level elements such as <code><nowiki><poem></nowiki></code>, paragraphs, lists, or divs.


The template italicises the text by default (this can be suppressed, and does not apply to certain scripts) and can prompt [[web browser]]s to use a more appropriate font or screen readers to use a particular kind of pronunciation and so on. See {{section link||Rationale}} for more information.
The template italicises the text by default (this can be suppressed, and does not apply to certain scripts) and can prompt web browsers to use a more appropriate font or screen readers to use a particular kind of pronunciation and so on. See {{section link||Rationale}} for more information.


== Syntax and usage ==
== Syntax and usage ==
Line 14: Line 14:
{{in5}}{{tlx|lang|{{var|language tag}}|{{var|text}}}}
{{in5}}{{tlx|lang|{{var|language tag}}|{{var|text}}}}


The {{var|language tag}} should consist of an [[ISO-639]] language code. See the [[List of ISO 639-1 codes|list of ISO 639-1 codes]] for two-letter codes; if you don't find the language you seek, then refer to the [[List of ISO 639-3 codes|list of ISO 639-3 codes]].
The {{var|language tag}} should consist of an ISO-639 language code. See the list of ISO 639-1 codes for two-letter codes; if you don't find the language you seek, then refer to the list of ISO 639-3 codes.


The template also supports properly formatted [[IETF language tag]]s using 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 code <code>fr</code>:
The template also supports properly formatted IETF language tags using 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 code <code>fr</code>:


* <code><nowiki>She said: "{{lang|fr|Je suis française.}}"</nowiki></code> → She said: "{{lang|fr|Je suis française.}}"
* <code><nowiki>She said: "{{lang|fr|Je suis française.}}"</nowiki></code> → She said: "{{lang|fr|Je suis française.}}"


Because all languages represented by two-letter codes in [[ISO 639-1]] can also be represented by their 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.<ref>[https://www.w3.org/International/articles/language-tags/index.en "Language tags in HTML and XML"] at [[World Wide Web Consortium]]</ref> So while French could be represented by ISO 639-2's <code>fra</code> code, use the ISO 639-1 code <code>fr</code> 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 the [[Internet Assigned Numbers Authority|IANA]]'s [http://www.iana.org/assignments/language-subtag-registry/language-subtag-registry language subtag registry].
Because all languages represented by two-letter codes in ISO 639-1 can also be represented by their 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.<ref>[https://www.w3.org/International/articles/language-tags/index.en "Language tags in HTML and XML"] at World Wide Web Consortium</ref> So while French could be represented by ISO 639-2's <code>fra</code> code, use the ISO 639-1 code <code>fr</code> 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 the IANA's [http://www.iana.org/assignments/language-subtag-registry/language-subtag-registry language subtag registry].


By default, this template will place articles into the relevant subcategory of {{category link|Articles containing non-English-language text}}. To suppress this – e.g. when using {{tlf|lang}} within a [[Help:Link#Wikilinks|wikilink]] or the ''title'' parameter of a citation – add the parameter {{para|cat|no}}.
By default, this template will place articles into the relevant subcategory of {{category link|Articles containing non-English-language text}}. To suppress this – e.g. when using {{tlf|lang}} within a wikilink or the ''title'' parameter of a citation – add the parameter {{para|cat|no}}.


=== Formatting ===
=== Formatting ===
Line 72: Line 72:
=== Right-to-left languages ===
=== Right-to-left languages ===


To embed a string of right-to-left text (such as [[Arabic]] or [[Hebrew language|Hebrew]]) within the usual left-to-right context, {{para|rtl|yes}} should be added to correctly communicate writing direction. To mark a whole paragraph of right-to-left text, {{tl|rtl-para}} should be used instead.
To embed a string of right-to-left text (such as Arabic]] or Hebrew) within the usual left-to-right context, {{para|rtl|yes}} should be added to correctly communicate writing direction. To mark a whole paragraph of right-to-left text, {{tl|rtl-para}} should be used instead.


Any of these approaches will wrap the text in a container with the <code>dir="rtl"</code> attribute. In order to ensure correct rendering in browsers that do not fully support [[HTML5]] [[bidirectional text|bidirectional isolation]], a [[left-to-right mark]] is also added to the end of the text (see the [http://www.w3.org/International/articles/inline-bidi-markup W3C] for details).
Any of these approaches will wrap the text in a container with the <code>dir="rtl"</code> attribute. In order to ensure correct rendering in browsers that do not fully support HTML5 bidirectional isolation, a [eft-to-right mark is also added to the end of the text (see the [http://www.w3.org/International/articles/inline-bidi-markup W3C] for details).


Note that text direction does not need to be specified when using the {{tnull|lang-{{var|xx}}}} templates, as this is implied by the template's language.
Note that text direction does not need to be specified when using the {{tnull|lang-{{var|xx}}}} templates, as this is implied by the template's language.
Line 86: Line 86:
! style="width: 12%;" | Alias
! style="width: 12%;" | Alias
|-
|-
| {{para|code}} || [[IETF language tag]] for the content in <code>text</code> || – || {{para|1}}
| {{para|code}} || IETF language tag for the content in <code>text</code> || – || {{para|1}}
|-
|-
| {{para|text}}|| non-English text || – || {{para|2}}
| {{para|text}}|| non-English text || – || {{para|2}}
Line 255: Line 255:
== Indicating writing script ==
== Indicating writing script ==


If necessary, an [[List of ISO 15924 codes|ISO 15924]] script code can be appended to a language code to indicate the use of a specific script. For instance, [[Tajik language|Tajik]] (<code>tg</code>) is a language which can be found written in [[Arabic script|Arabic]] (<code>Arab</code>), [[Latin script|Latin]] (<code>Latn</code>), and [[Cyrillic script|Cyrillic]] (<code>Cyrl</code>) 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):
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 (<code>tg</code>) is a language which can be found written in Arabic (<code>Arab</code>), Latin (<code>Latn</code>), and Cyrillic (<code>Cyrl</code>) 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):


* <code><nowiki>Tajik ({{lang|</nowiki>'''tg-Arab'''<nowiki>|rtl=yes|تاجیکی}}, {{lang|</nowiki>'''tg-Latn'''<nowiki>|toçikī}}, {{lang|</nowiki>'''tg-Cyrl'''<nowiki>|тоҷикӣ}})</nowiki></code>
* <code><nowiki>Tajik ({{lang|</nowiki>'''tg-Arab'''<nowiki>|rtl=yes|تاجیکی}}, {{lang|</nowiki>'''tg-Latn'''<nowiki>|toçikī}}, {{lang|</nowiki>'''tg-Cyrl'''<nowiki>|тоҷикӣ}})</nowiki></code>
Line 264: Line 264:
=== Transliteration ===
=== Transliteration ===


To mark a language which has been [[transliteration|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 <code>ru-Latn</code>. If the transliteration scheme is known, and listed as a "variant" in the [http://www.iana.org/assignments/language-subtag-registry/language-subtag-registry subtag registry], it can be appended after any script and region codes. For example, Chinese transliterated into a Latin script using the [[pinyin]] system would be <code>zh-Latn-pinyin</code>. As a convenience for transliterating to Latin scripts, and to work around browser styling issues with some language and script combinations, {{tl|transliteration}} may be used in place of {{tlf|lang}}:
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 <code>ru-Latn</code>. If the transliteration scheme is known, and listed as a "variant" in the [http://www.iana.org/assignments/language-subtag-registry/language-subtag-registry subtag registry], it can be appended after any script and region codes. For example, Chinese transliterated into a Latin script using the pinyin system would be <code>zh-Latn-pinyin</code>. As a convenience for transliterating to Latin scripts, and to work around browser styling issues with some language and script combinations, {{tl|transliteration}} may be used in place of {{tlf|lang}}:


* <code><nowiki>Moscow ({{lang|ru|Москва}}, {{transliteration|ru|Moskva}})</nowiki></code> → Moscow ({{lang|ru|Москва}}, {{transliteration|ru|Moskva}})
* <code><nowiki>Moscow ({{lang|ru|Москва}}, {{transliteration|ru|Moskva}})</nowiki></code> → Moscow ({{lang|ru|Москва}}, {{transliteration|ru|Moskva}})


To specify a transliteration scheme, such as the [[ISO 9|ISO transliteration standard for Cyrillic]], use {{tlc|transliteration|ru|ISO|Moskva}}.
To specify a transliteration scheme, such as the ISO transliteration standard for Cyrillic, use {{tlc|transliteration|ru|ISO|Moskva}}.


=== Glyphs not connected to a particular language ===
=== Glyphs not connected to a particular language ===


The {{tlf|lang}} template is not 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 template {{tl|script}} should be used:
The {{tlf|lang}} template is not 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 template {{tl|script}} should be used:


* <code><nowiki>The Chinese character {{script|Hani|字}} has 6 strokes.</nowiki></code>
* <code><nowiki>The Chinese character {{script|Hani|字}} has 6 strokes.</nowiki></code>
: The Chinese character {{script|Hani|字}} has 6 strokes.
: The Chinese character {{script|Hani|字}} has 6 strokes.


[[Chinese characters]] ({{aka}} ''Han characters'') have been used to write Chinese, Japanese, Korean, Vietnamese, and [[Chinese family of scripts|numerous other languages]]. In this case the character does not represent a use specific to any language in particular. Note that the script code used is <code>Hani</code>, which specifies Chinese characters generally, as opposed to <code>Hant</code> and <code>Hans</code> for traditional or simplified characters respectively.
Chinese characters ({{aka}} ''Han characters'') have been used to write Chinese, Japanese, Korean, Vietnamese, and numerous other languages. In this case the character does not represent a use specific to any language in particular. Note that the script code used is <code>Hani</code>, which specifies Chinese characters generally, as opposed to <code>Hant</code> and <code>Hans</code> for traditional or simplified characters respectively.


== Languages with no code ==
== Languages with no code ==
Line 284: Line 284:
== Indicating regional variant ==
== Indicating regional variant ==


When it is necessary to indicate region-specific language, an [[ISO 3166-1 alpha-2]] country code, or [[UN M49]] region code, should be added to the language tag, taking care to preserve capitalization. For example, Portuguese (<code>pt</code>) as used in Brazil (<code>BR</code>) could be represented as <code>pt-BR</code>, and Spanish as used in Latin America as <code>es-419</code>.
When it is necessary to indicate region-specific language, an ISO 3166-1 alpha-2 country code, or UN M49 region code, should be added to the language tag, taking care to preserve capitalization. For example, Portuguese (<code>pt</code>) as used in Brazil (<code>BR</code>) could be represented as <code>pt-BR</code>, and Spanish as used in Latin America as <code>es-419</code>.


Additionally, language, script, and region codes can all appear in the same tag. For instance, the code <code>zh-Hant-TW</code> should be used for Chinese text written with [[Traditional Chinese characters|Traditional Han characters]], containing words or expressions specific to [[Taiwan]]:
Additionally, language, script, and region codes can all appear in the same tag. For instance, the code <code>zh-Hant-TW</code> should be used for Chinese text written with Traditional Han characters, containing words or expressions specific to Taiwan:


* <code><nowiki>Taiwan ({{lang|zh-Hant-TW|臺灣}}, {{transliteration|zh|Táiwān}})</nowiki></code>
* <code><nowiki>Taiwan ({{lang|zh-Hant-TW|臺灣}}, {{transliteration|zh|Táiwān}})</nowiki></code>
Line 292: Line 292:


== Private-use language tags ==
== Private-use language tags ==
This template supports various private-use [[IETF language tag]]s. Private-use tags contain the <code>-x-</code> singleton and are used by the template to identify languages that are different, for one reason or another, from the base language identified by the ISO 639 language tag.
This template supports various private-use IETF language tags. Private-use tags contain the <code>-x-</code> singleton and are used by the template to identify languages that are different, for one reason or another, from the base language identified by the ISO 639 language tag.
{{#invoke:Lang/documentor tool|private_tags}}
{{#invoke:Lang/documentor tool|private_tags}}


Line 324: Line 324:
{{section link|Wikipedia:Manual of Style/Text formatting|Foreign terms}} requires the use of {{tl|lang}} instead of manual <nowiki>''italics''</nowiki>. This is preferred for the following reasons:
{{section link|Wikipedia:Manual of Style/Text formatting|Foreign terms}} requires the use of {{tl|lang}} instead of manual <nowiki>''italics''</nowiki>. This is preferred for the following reasons:


* [[Web browser]]s can use the information in such [[:Category:Wikipedia multilingual support templates|multilingual support templates]] to choose an appropriate font.
* Web browsers can use the information in such [[:Category:Wikipedia multilingual support templates|multilingual support templates]] to choose an appropriate font.
** This is great for [[CJK characters|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 {{section link|Han unification|Examples of language-dependent glyphs}} and [[User:Wikipeditor/CJK|these comparison tables with a screenshot]].
** 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 {{section link|Han unification|Examples of language-dependent glyphs}} and these comparison tables with a screenshot.
* For [[web accessibility|accessibility]] [[screen reader]]s need language info to speak text in the correct language – and to satisfy [[Wikipedia:Accessibility#Text|Wikipedia accessibility guidelines]].<ref>{{cite web |url=https://developer.yahoo.com/blogs/ydn/yahoo-search-results-now-natural-language-support-7318.html|title=Yahoo! search results now with natural language support |date=13 Mar 2008|first=Chris |last=Heilmann|work=[[Yahoo! Developer Network]] Blog |accessdate=28 Feb 2015|archiveurl=https://web.archive.org/web/20090125024422/http://developer.yahoo.net/blog/archives/2008/03/yahoo_search_re.html|archivedate=25 Jan 2009|url-status=dead}}</ref>
* For accessibility – screen readers need language info to speak text in the correct language – and to satisfy [[Wikipedia:Accessibility#Text|Wikipedia accessibility guidelines]].<ref>{{cite web |url=https://developer.yahoo.com/blogs/ydn/yahoo-search-results-now-natural-language-support-7318.html|title=Yahoo! search results now with natural language support |date=13 Mar 2008|first=Chris |last=Heilmann|work=Yahoo! Developer Network Blog |accessdate=28 Feb 2015|archiveurl=https://web.archive.org/web/20090125024422/http://developer.yahoo.net/blog/archives/2008/03/yahoo_search_re.html|archivedate=25 Jan 2009|url-status=dead}}</ref>
* For [[spell checker]]s and grammar checkers, to match the text to the dictionary and syntax of the correct language.
* For spell checkers and grammar checkers, to match the text to the dictionary and syntax of the correct language.
* To prevent the page from showing up on the [[Wikipedia:Typo Team/moss/not English]] report, which flags articles needing translation.
* To prevent the page from showing up on the [[Wikipedia:Typo Team/moss/not English]] report, which flags articles needing translation.
* To help browsers choose appropriate [[quotation mark]]s,<ref name="qa-lang-why">{{cite web|url=http://www.w3.org/International/questions/qa-lang-why |title=Why use the language attribute?|date=18 November 2014|first= Richard |last= Ishida | publisher=World Wide Web Consortium |issue=Previously by Deborah Cawkwell, BBC World Service|accessdate=1 Mar 2015}}</ref> and make decisions about [[Hyphen|hyphenation]],<ref name="qa-lang-why"/> [[orthographic ligature|ligature]]s,<ref>{{cite web|url=http://www.w3.org/TR/css3-fonts/#font-variant-ligatures-prop|title=6.4 Ligatures: the font-variant-ligatures property|work=CSS Fonts Module Level 3 W3C Candidate Recommendation 3 October 2013}}</ref> and spacing.<ref name="qa-lang-why"/>
* To help browsers choose appropriate quotation marks,<ref name="qa-lang-why">{{cite web|url=http://www.w3.org/International/questions/qa-lang-why |title=Why use the language attribute?|date=18 November 2014|first= Richard |last= Ishida | publisher=World Wide Web Consortium |issue=Previously by Deborah Cawkwell, BBC World Service|accessdate=1 Mar 2015}}</ref> and make decisions about hyphenation,<ref name="qa-lang-why"/> ligatures,<ref>{{cite web|url=http://www.w3.org/TR/css3-fonts/#font-variant-ligatures-prop|title=6.4 Ligatures: the font-variant-ligatures property|work=CSS Fonts Module Level 3 W3C Candidate Recommendation 3 October 2013}}</ref> and spacing.<ref name="qa-lang-why"/>
* Users can apply styles to languages in their [[style sheet (web development)|style sheet]]s (useful for editors).
* Users can apply styles to languages in their style sheets (useful for editors).
* [[Web search engine|Search engine]]s can use this information when [[search engine indexing|indexing]] text.
* Search engines can use this information when indexing text.
* Facilitates better data-scraping, parsing and reuse.
* Facilitates better data-scraping, parsing and reuse.
* Useful for application developers who re-publish Wikipedia (also see {{section link|Wikipedia:Manual of Style/Accessibility|Other languages}}).
* Useful for application developers who re-publish Wikipedia (also see {{section link|Wikipedia:Manual of Style/Accessibility|Other languages}}).
Line 338: Line 338:
== Applying styles ==
== Applying styles ==


Registered users can apply custom [[Cascading Style Sheets|CSS]] styles to articles by placing style declarations in their user style sheet. The user style sheet can be created at [[Special:Mypage/common.css]]. For more information, see [[Help:User style]]. The following examples should work in most [[List of web browsers|modern browsers]].
Registered users can apply custom CSS styles to articles by placing style declarations in their user style sheet. The user style sheet can be created at Special:Mypage/common.css. For more information, see Help:User style. The following examples should work in most modern browsers.


To apply a specific font to all text marked as Russian of any script or region:
To apply a specific font to all text marked as Russian of any script or region:
Line 362: Line 362:
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 the [http://www.w3.org/TR/CSS21/fonts.html#font-family-prop W3C] for more details.
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 the [http://www.w3.org/TR/CSS21/fonts.html#font-family-prop W3C] for more details.


You can combine this with font imports in your user stylesheet, for example, to show all German text in [[Fraktur]] and all Urdu in [[Noto fonts|Noto]] [[Nastaʿlīq script|Nastaliq]] Urdu Regular:
You can combine this with font imports in your user stylesheet, for example, to show all German text in Fraktur and all Urdu in Noto Nastaliq Urdu Regular:


<syntaxhighlight lang="css">
<syntaxhighlight lang="css">
Line 461: Line 461:
* {{tl|Title language}}
* {{tl|Title language}}
* [[:Category:Wikipedia multilingual support templates]]
* [[:Category:Wikipedia multilingual support templates]]
* [[Lists of ISO 639 codes]] (language codes)
* Lists of ISO 639 codes (language codes)
** {{tl|ISO 639 name}}
** {{tl|ISO 639 name}}
* [[List of ISO 15924 codes]] (script codes)
* List of ISO 15924 codes (script codes)
* [[List of ISO romanizations|List of ISO transliterations]] (transliteration codes)
* List of ISO transliterations (transliteration codes)
* {{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|transliteration}} (for romanisation of languages not natively written in the Latin alphabet)
* {{tl|transliteration}} (for romanisation of languages not natively written in the Latin alphabet)
Line 477: Line 477:


== External links ==
== External links ==
* [[World Wide Web Consortium|W3C]]
* W3C
** [http://www.w3.org/International/articles/language-tags/Overview.en.php Language tags in HTML and XML] – Overview
** [http://www.w3.org/International/articles/language-tags/Overview.en.php Language tags in HTML and XML] – Overview
** [https://www.w3.org/International/techniques/authoring-html#language Authoring Web pages]
** [https://www.w3.org/International/techniques/authoring-html#language Authoring Web pages]
** [http://www.w3.org/International/articles/bcp47/ Understanding the New Language Tags]
** [http://www.w3.org/International/articles/bcp47/ Understanding the New Language Tags]
** [http://www.w3.org/International/questions/qa-css-lang FAQ: Styling using the lang attribute]
** [http://www.w3.org/International/questions/qa-css-lang FAQ: Styling using the lang attribute]
* [[Internet Assigned Numbers Authority|IANA]]
* IANA
** [http://www.iana.org/assignments/language-subtag-registry IANA Language Subtag Registry]
** [http://www.iana.org/assignments/language-subtag-registry IANA Language Subtag Registry]
** [http://www.rfc-editor.org/rfc/rfc4646.txt Tags for Identifying Languages] ({{IETF RFC|4646}})
** [http://www.rfc-editor.org/rfc/rfc4646.txt Tags for Identifying Languages] ({{IETF RFC|4646}})
** [http://www.rfc-editor.org/rfc/rfc4647.txt Matching of Language Tags] ({{IETF RFC|4647}})
** [http://www.rfc-editor.org/rfc/rfc4647.txt Matching of Language Tags] ({{IETF RFC|4647}})
** [http://www.iana.org/assignments/language-tags Language tags] (obsolete per {{IETF RFC|4646}})
** [http://www.iana.org/assignments/language-tags Language tags] (obsolete per {{IETF RFC|4646}})
* [[Mozilla Firefox]]
* Mozilla Firefox
** [https://bugzilla.mozilla.org/show_bug.cgi?id=192636 Bug with script selection]
** [https://bugzilla.mozilla.org/show_bug.cgi?id=192636 Bug with script selection]



Revision as of 20:53, 29 March 2025

This page uses Creative Commons Licensed content from Wikipedia (view authors).

Template:High-use Template:COinS safe

Template:Language templates

The purpose of this template is to indicate that a piece of text belongs to a particular language other than that of the page as a whole (by default, English, on this Wikipedia). It can be used inline, or around block-level elements such as <poem>, paragraphs, lists, or divs.

The template italicises the text by default (this can be suppressed, and does not apply to certain scripts) and can prompt web browsers to use a more appropriate font or screen readers to use a particular kind of pronunciation and so on. See § Rationale for more information.

Syntax and usage

Template:In5{{lang|language tag|text}}

The language tag should consist of an ISO-639 language code. See the list of ISO 639-1 codes for two-letter codes; if you don't find the language you seek, then refer to the list of ISO 639-3 codes.

The template also supports properly formatted IETF language tags using 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 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 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 ISO 639-2's fra code, use the ISO 639-1 code fr 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 the IANA's language subtag registry.

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 |cat=no.

Formatting

Automatic italics

Template:Tld automatically applies italic styling when the text in Template:Param is written entirely in the Latn script (the Latin alphabet and its extensions), either when that is the default encoding for the language or when it is triggered by a xx-Latn language codeTemplate:Colon

  • {{lang|fr|Je suis française.}}Je suis française.
  • ''{{lang|fr|Je suis française.}}''Je suis française. – external markup is ignored
  • {{lang|he-Latn|la'az}} ({{lang|he|לעז}})la'az (Lua error in Module:Unicode_data at line 474: attempt to index field 'scripts' (a boolean value).)
  • ''{{lang|he-Latn|la'az}}'' (''{{lang|he|לעז}}'')la'az (Lua error in Module:Unicode_data at line 474: attempt to index field 'scripts' (a boolean value).) – external markup is ignored around the he-Latn text, but will incorrectly italicize the Hebrew-character material.

When Latn script should not be italicized, there are multiple approachesTemplate:Colon |italic=no – renders Template:Param in upright font; italic markup around the template is ignored; italic markup inside the template causes an error messageTemplate:Colon

  • {{lang|fr|Je suis française.|italic=no}}Je suis française.
  • ''{{lang|fr|Je suis française.|italic=no}}''Je suis française.
  • ''{{lang|fr|Je suis ''française''.|italic=no}}''[Je suis française.] Error: {{Lang}}: text has italic markup (help) – italic markup in conflict with |italic=no

|italic=unset – disables template-provided styling; Template:Param is styled according to external or internal wiki markupTemplate:Colon

  • {{lang|fr|Je suis française.|italic=unset}}Je suis française.
  • ''{{lang|fr|Je suis française.|italic=unset}}''Je suis française.
  • {{lang|fr|''Je suis'' English.|italic=unset}}Je suis English.

{{noitalic}} can also be usedTemplate:Colon

Prefixed language template

There is a version of this template, {{langx}}, which is 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''' ({{langx|ru|кремль}}, 'castle') is a major fortified central complex ... → A kremlin (Template:Langx, 'castle') is a major fortified central complex ...

While the {{langx}} template outputs 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 ({{langx|fr|Vintimille}}) → the border town of Ventimiglia (Template:Langx)
  • the border town of Ventimiglia ({{langx|fr|italic=no|Vintimille}}) → the border town of Ventimiglia (Template:Langx)
  • the border town of Ventimiglia ({{langx|fr|{{noitalic|Vintimille}}}}) → the border town of Ventimiglia (Template:Langx)

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.


Proto-languages

  • {{lang|cel-x-proto|kal-}}*kal-
  • {{lang|cel-x-proto|kal-|proto=no}}kal-
  • Lua error: expandTemplate: template "Template:langx" does not exist.
  • Lua error: expandTemplate: template "Template:langx" does not exist.
  • {{lang|en|accidently}}accidently
  • {{lang|en|accidently|proto=yes}}*accidently

Right-to-left languages

To embed a string of right-to-left text (such as Arabic]] or Hebrew) within the usual left-to-right context, |rtl=yes should be added to correctly communicate writing direction. To mark 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 the dir="rtl" attribute. In order to ensure correct rendering in browsers that do not fully support HTML5 bidirectional isolation, a [eft-to-right mark is also added to the end of the text (see the W3C for details).

Note that text direction does not need to be specified when using the {{lang-xx}} templates, as this is implied by the template's language.

Parameters

Lang supported parameters
Parameter Definition Yields to Alias
|code= IETF language tag for the content in text |1=
|text= non-English text |2=
|rtl= yes indicates that the writing system used for the content in |text= is right-to-left; accepted values are: no (default), yes IETF script subtag in |code= (if provided)
|italic= ; accepted values are: yes, no, unset, invert, default |italics=, |i=
|size= specifies font size of the content in text; use a value suitable for use with the CSS font-size property; this should almost always be a relative value supplied in Template:Mxt or Template:Mxt units, not a fixed px value.
|proto= accepted values are: no (default) or yes (default for private-use language tags with the -x-proto subtags); when yes (default or explicit), prefixes rendered text with an asterisk indicating 'unattested'
|cat= inhibits automatic categorization; mirror version of |nocat=; accepted values are: no, n, false, f, off, 0
|nocat= inhibits automatic categorization; mirror version of |cat=; accepted values are: yes, y, true, t, on, 1
Lang Template:Pipeitalic= parameter operation
Template:Pipeitalic= value description example code result html markup
  • parameter not present;
  • parameter present, not set;
  • invalid value
  • module applies style from:
  •   auto-italics or
  •   script subtag latn;
  • else inherits from external markup;
  • invalid values treated as default
{{lang|ru|тундра}} тундра <span title="Russian-language text"><span lang="ru">тундра</span></span>
Template:Deprecated code tûndra <span title="Russian-language text"><i lang="ru">tûndra</i></span>
Incorrect markup; this requires |ru-Latn.
{{lang|fr|toundra}} toundra <span title="French-language text"><i lang="fr">toundra</i></span>
{{lang|ru-Latn|tûndra}} tûndra <span title="Russian-language text"><i lang="ru-Latn">tûndra</i></span>
default {{lang|ru|тундра|italic=default}} тундра <span title="Russian-language text"><span lang="ru">тундра</span></span>
{{lang|fr|toundra|italic=default}} toundra <span title="French-language text"><i lang="fr">toundra</i></span>
{{lang|ru-Latn|tûndra|italic=default}} tûndra <span title="Russian-language text"><i lang="ru-Latn">tûndra</i></span>
no
  • module applies upright style;
  • overrides auto-italics
  • overrides script subtag latn;
  • overrides external markup
{{lang|ru|тундра|italic=no}} тундра <span title="Russian-language text"><span lang="ru" style="font-style: normal;">тундра</span></span>
{{lang|fr|toundra|italic=no}} toundra <span title="French-language text"><span lang="fr" style="font-style: normal;">toundra</span></span>
{{lang|ru-Latn|tûndra|italic=no}} tûndra <span title="Russian-language text"><span lang="ru-Latn" style="font-style: normal;">tûndra</span></span>
''{{lang|fr|toundra|italic=no}}'' toundra ''<span title="French-language text"><span lang="fr" style="font-style: normal;">toundra</span></span>''
yes
  • module applies italic style;
  • ignores auto-italics;
  • ignores script subtag latn
Template:Deprecated code тундра <span title="Russian-language text"><i lang="ru">тундра</i></span> Incorrect markup per MOS:BADITALICS.
{{lang|ru-Latn|tûndra|italic=yes}} tûndra <span title="Russian-language text"><i lang="ru-Latn">tûndra</i></span>
unset
  • module applies no style;
  • inherits style from external markup;
  • disables auto-italics
  • overrides script subtag latn;
{{lang|ru|тундра|italic=unset}} тундра <span title="Russian-language text"><span lang="ru">тундра</span></span>
Template:Deprecated code тундра ''<span title="Russian-language text"><span lang="ru">тундра</span></span>'' Incorrect markup per MOS:BADITALICS.
{{lang|ru-Latn|tûndra|italic=unset}} tûndra <span title="Russian-language text"><span lang="ru-Latn">tûndra</span></span>
''{{lang|ru-Latn|tûndra|italic=unset}}'' tûndra ''<span title="Russian-language text"><span lang="ru-Latn">tûndra</span></span>''
invert
  • module applies no style;
  • inverts style in internal markup;[lower-alpha 1]
  • disables auto-italics
  • overrides script subtag latn;
Template:Deprecated code тундра <span title="Russian-language text"><span lang="ru">''тундра''</span></span> Incorrect markup per MOS:BADITALICS.
{{lang|ru|''тундра''|italic=invert}} тундра <span title="Russian-language text"><span lang="ru">тундра</span></span>
{{lang|ru-Latn|tûndra|italic=invert}} tûndra <span title="Russian-language text"><span lang="ru-Latn">''tûndra''</span></span>
{{lang|ru-Latn|''tûndra''|italic=invert}} tûndra <span title="Russian-language text"><span lang="ru-Latn">tûndra</span></span>

Notes

  1. compare |italic=invert to |italic=unset:
    {{Lang|de|... ein neues Opernprojekt in Angriff: ''Das Käthchen von Heilbronn'', nach Heinrich von Kleists gleichnamigem Drama.|italic=invert}}
    ... ein neues Opernprojekt in Angriff: Das Käthchen von Heilbronn, nach Heinrich von Kleists gleichnamigem Drama.
    {{Lang|de|''... ein neues Opernprojekt in Angriff: ''Das Käthchen von Heilbronn'', nach Heinrich von Kleists gleichnamigem Drama.''|italic=unset}}
    ... ein neues Opernprojekt in Angriff: Das Käthchen von Heilbronn, nach Heinrich von Kleists gleichnamigem Drama.

The function selector parameter

{{lang}} uses the Lua function lang() Module:Lang. That module also supports all of the {{lang-??}} templates using the Lua functions lang_xx_inherit() and lang_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 – returns true if the provided IETF language tag is valid; nil else
    • {{lang|fn=is_ietf_tag|nv}} →true←
    • {{lang|fn=is_ietf_tag|xx}} →←
  • is_lang_name – returns true if the provided language name is valid; nil else
    • {{lang|fn=is_lang_name|navajo}} →true←
    • {{lang|fn=is_lang_name|xxxxx}} →←
  • lang – the function that renders {{lang}}; listed here for completeness, this particular usage is more-or-less pointless
  • name_from_tag – returns the language name associated with the provided IETF language tag:
    • {{lang|fn=name_from_tag|apa}} → Apache languages
  • 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}} → yuf-x-hav
  • 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ī}}al-Ḫawārizmī

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 code's capitalization, we could end up with the following code (language tags in bold):

  • Tajik ({{lang|tg-Arab|rtl=yes|تاجیکی}}, {{lang|tg-Latn|toçikī}}, {{lang|tg-Cyrl|тоҷикӣ}})
Tajik (تاجیکی, 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 unnecessary for English. The subtag registry contains up-to-date information on which languages have common script codes that should be "suppressed".

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. If the transliteration scheme is known, and listed as a "variant" in the subtag registry, it can be appended after any script and region codes. For example, Chinese transliterated into a Latin script using the pinyin system would be zh-Latn-pinyin. As a convenience for transliterating to Latin scripts, and to work around browser styling issues with some language and script combinations, {{transliteration}} may be used in place of {{lang}}:

To specify a transliteration scheme, such as the ISO transliteration standard for Cyrillic, use {{transliteration|ru|ISO|Moskva}}.

Glyphs not connected to a particular language

The {{lang}} template is not 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 template {{script}} should be used:

  • The Chinese character {{script|Hani|字}} has 6 strokes.
The Chinese character Template:Script has 6 strokes.

Chinese characters (Template:Aka Han characters) have been used to write Chinese, Japanese, Korean, Vietnamese, and numerous other languages. In this case the character does not represent a use specific to any language in particular. Note that the script code used is Hani, which specifies Chinese characters generally, as opposed to Hant and Hans for traditional or simplified characters respectively.

Languages with no code

The code mis, for "Miscellaneous", to indicate any language not listed in ISO-639.

Indicating regional variant

When it is necessary to indicate region-specific language, an ISO 3166-1 alpha-2 country code, or UN M49 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|臺灣}}, {{transliteration|zh|Táiwān}})
Taiwan (Lua error in Module:Unicode_data at line 474: attempt to index field 'scripts' (a boolean value)., Template:Transliteration)

Private-use language tags

This template supports various private-use IETF language tags. Private-use tags contain the -x- singleton and are used by the template to identify languages that are different, for one reason or another, from the base language identified by the ISO 639 language tag. Script error: No such module "Lang/documentor tool".

Links

Template:Tld emits a language-specific category link when used in article space (one of the categories in Category:Articles containing non-English-language text). Category wikilinks within wikilinks are not accepted by MediaWiki.

This example is a simulation because Template:Tld does not categorize in the Template namespace:

[[Book of hours|{{lang|de|Stundenbuch}}]]
[[Book of hours|<span title="German-language text"><i lang="de">Stundenbuch</i></span>[[Category:Articles containing German-language text]]]]
[[Book of hours|Stundenbuch]]

To create a working link, set |nocat=yes:

[[Book of hours|{{lang|de|Stundenbuch|nocat=yes}}]]
[[Book of hours|<span title="German-language text"><i lang="de">Stundenbuch</i></span>]]
Stundenbuch

When using Template:Tld with {{Interlanguage link}}, use that template's link-text parameter |lt=:

{{ill|Ehōmaki|ja|恵方巻|lt={{lang|ja-Latn|ehōmaki|nocat=yes}}}}
[[:Template:Ill]]
Template:Ill

When using Template:Tld with non-English wiktionary links:

[[wikt:Κλεοπάτρα#Ancient Greek|{{lang|grc|Κλεοπάτρα|nocat=yes}}]]
[[wikt:Κλεοπάτρα#Ancient Greek|<span title="Ancient Greek (to 1453)-language text"><span lang="grc">Κλεοπάτρα</span></span>]]
Κλεοπάτρα
Do not write:
{{lang|grc|[[wikt:Κλεοπάτρα#Ancient Greek|Κλεοπάτρα]]|nocat=yes}}
The words 'wikt' and 'Ancient Greek' are not Ancient Greek words so do not belong in the same markup as the Ancient Greek word Κλεοπάτρα.

In general, when using Template:Tld with wikilinks, markup the wikilink's display (piped) text, not the entire wikilink.

Rationale

Wikipedia:Manual of Style/Text formatting § Foreign terms requires the use of {{lang}} instead of manual ''italics''. This is preferred for the following reasons:

  • 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 Han unification § Examples of language-dependent glyphs and these comparison tables with a screenshot.
  • 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 match the text to the dictionary and syntax of the correct language.
  • To prevent the page from showing up on the Wikipedia:Typo Team/moss/not English report, which flags articles needing translation.
  • 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 reuse.
  • Useful for application developers who re-publish Wikipedia (also see Wikipedia:Manual of Style/Accessibility § Other languages).
  • Useful for research or compiling statistics about language use in Wikipedia.

Applying styles

Registered users can apply custom CSS styles to articles by placing style declarations in their user style sheet. The user style sheet can be created at Special:Mypage/common.css. For more information, see Help:User style. The following examples should work in most modern browsers.

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 the W3C for more details.

You can combine this with font imports in your user stylesheet, for example, to show all German text in Fraktur and all Urdu in Noto Nastaliq Urdu Regular:

@import url(https://fonts.googleapis.com/css?family=UnifrakturMaguntia);
@import url(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|ٹھنڈ میں، ایک قحط زدہ گاؤں سے گزرتے وقت ایک چڑچڑے، بااثر و فارغ شخص کو بعض جل پری نما اژدہے نظر آئے۔}}

Template:Wide image

Tracking categories

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. See a monthly parameter usage report for Template:Lang in articles based on its TemplateData.

TemplateData for Lang

Indicate that a given span of text belongs to a particular language. Allows browsers to correctly present and pronounce foreign languages.

Template parameters

This template prefers inline formatting of parameters.

ParameterDescriptionTypeStatus
Language tag1 code

A language tag, or an ISO 639 language code.

Example
fr
Stringrequired
Text2 text

The text belonging to the language specified.

Example
Je suis française.
Stringrequired
Right to leftrtl

Indicates that the language should be displayed from right to left.

Default
no
Example
yes
Stringoptional
Italicizeitalic italics i

Italicizes the text

Default
yes
Example
no
Booleanoptional
Font-sizesize

sets font-size

Example
120%, 1.2em
Unknownoptional
catcat

no description

Unknownoptional
nocatnocat

no description

Unknownoptional

See also

  • {{Langr}}, variant of this template that forces "roman" (non-italic) output, e.g. for proper names of places and institutions
  • {{Langx}}, variant of this template that displays the name of the language before the marked-up text
  • {{IPA}}
  • {{Title language}}
  • Category:Wikipedia multilingual support templates
  • Lists of ISO 639 codes (language codes)
  • 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)
  • {{transliteration}} (for romanisation of languages not natively written in the Latin alphabet)
  • {{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)
  • {{mw lang}} (similar to {{ISO 639 name}} for MediaWiki-supported languages)
  • {{interlanguage link}}

References

  1. "Language tags in HTML and XML" at World Wide Web Consortium
  2. 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.
  3. 3.0 3.1 3.2 Ishida, Richard (18 November 2014). "Why use the language attribute?". World Wide Web Consortium. Retrieved 1 Mar 2015.
  4. "6.4 Ligatures: the font-variant-ligatures property". CSS Fonts Module Level 3 W3C Candidate Recommendation 3 October 2013.

External links