Template:Lang/doc

From Drifter's Wiki TEST
Revision as of 15:24, 23 October 2022 by Archer (talk | contribs) (1 revision imported)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Lua error: Internal error: The interpreter exited with status 127. Lua error: Internal error: The interpreter exited with status 127. Lua error: Internal error: The interpreter exited with status 127. Lua error: Internal error: The interpreter exited with status 127. Lua error: Internal error: The interpreter exited with status 127.

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. See Lua error: Internal error: The interpreter exited with status 127. for more information.

Syntax and usage

Lua error: Internal error: The interpreter exited with status 127.Lua error: Internal error: The interpreter exited with status 127.

The language tag should consist of an ISO-639 language code (click here for list of most 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: "Lua error: Internal error: The interpreter exited with status 127."

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 Lua error: Internal error: The interpreter exited with status 127. within a wikilink or the title parameter of a citation – add the parameter |cat=no.

Formatting

Automatic italics

Lua error: Internal error: The interpreter exited with status 127. automatically applies italic styling when the text in {{{2}}} 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 code:

  • {{lang|fr|Je suis française.}}Lua error: Internal error: The interpreter exited with status 127.
  • ''{{lang|fr|Je suis française.}}''Lua error: Internal error: The interpreter exited with status 127. – external markup is ignored
  • {{lang|he-Latn|la'az}} ({{lang|he|לעז}})Lua error: Internal error: The interpreter exited with status 127. (Lua error: Internal error: The interpreter exited with status 127.)
  • ''{{lang|he-Latn|la'az}}'' (''{{lang|he|לעז}}'')Lua error: Internal error: The interpreter exited with status 127. (Lua error: Internal error: The interpreter exited with status 127.) – 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 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}}Lua error: Internal error: The interpreter exited with status 127.
  • ''{{lang|fr|Je suis française.|italic=no}}''Lua error: Internal error: The interpreter exited with status 127.
  • ''{{lang|fr|Je suis ''française''.|italic=no}}''Lua error: Internal error: The interpreter exited with status 127. – 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}}Lua error: Internal error: The interpreter exited with status 127.
  • ''{{lang|fr|Je suis française.|italic=unset}}''Lua error: Internal error: The interpreter exited with status 127.
  • {{lang|fr|''Je suis'' English.|italic=unset}}Lua error: Internal error: The interpreter exited with status 127.

Lua error: Internal error: The interpreter exited with status 127. can also be used:

  • {{lang|fr|Je suis {{noitalic|English}}.}}Lua error: Internal error: The interpreter exited with status 127.

Lua error: Internal error: The interpreter exited with status 127.

Language-specific templates

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 ... → A kremlin (Lua error: Internal error: The interpreter exited with status 127., 'castle') is a major fortified central complex ...

While Lua error: Internal error: The interpreter exited with status 127. templates output text in italics for languages with Latin-based scripts, if plain text is required, such as for proper names, |italic=no or Lua error: Internal error: The interpreter exited with status 127. may be used:

  • the border town of Ventimiglia ({{lang-fr|Vintimille}}) → the border town of Ventimiglia (Lua error: Internal error: The interpreter exited with status 127.)
  • the border town of Ventimiglia ({{lang-fr|italic=no|Vintimille}}) → the border town of Ventimiglia (Lua error: Internal error: The interpreter exited with status 127.)
  • the border town of Ventimiglia ({{lang-fr|{{noitalic|Vintimille}}}}) → the border town of Ventimiglia (Lua error: Internal error: The interpreter exited with status 127.)

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.

Lua error: Internal error: The interpreter exited with status 127.

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 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 the dir="rtl" attribute. In order to ensure correct rendering in browsers that do not fully support HTML5 bidirectional isolation, a left-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 Lua error: Internal error: The interpreter exited with status 127. templates, as this is implied by the template's language.

Parameters

{{#lst:Template:Lang-x/doc/parameters|lang_parameters}}

the function selector parameter

Lua error: Internal error: The interpreter exited with status 127. uses the Lua function lang() Module:Lang. That module also supports all of the Lua error: Internal error: The interpreter exited with status 127. 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}}Lua error: Internal error: The interpreter exited with status 127.
    • {{lang|fn=is_ietf_tag|xx}}Lua error: Internal error: The interpreter exited with status 127.
  • is_lang_name – returns true if the provided language name is valid; nil else
    • {{lang|fn=is_lang_name|navajo}}Lua error: Internal error: The interpreter exited with status 127.
    • {{lang|fn=is_lang_name|xxxxx}}Lua error: Internal error: The interpreter exited with status 127.
  • lang – the function that renders Lua error: Internal error: The interpreter exited with status 127.; listed here for completeness, this particular usage is more-or-less pointless
  • lang_xx_inherit – the function that renders Lua error: Internal error: The interpreter exited with status 127. template where the text is not italicized; can be used when a Lua error: Internal error: The interpreter exited with status 127. template, for example Lua error: Internal error: The interpreter exited with status 127., does not exist for a particular language:
    • {{lang|fn=lang_xx_inherit|code=aao|Algerian Saharan Arabic text}}Lua error: Internal error: The interpreter exited with status 127.
  • lang_xx_italic – the function that renders Lua error: Internal error: The interpreter exited with status 127. template where the text is italicized; can be used when a Lua error: Internal error: The interpreter exited with status 127. template, for example Lua error: Internal error: The interpreter exited with status 127., does not exist for a particular language:
    • {{lang|fn=lang_xx_italic|code=svc|Vincentian Creole English text}}Lua error: Internal error: The interpreter exited with status 127.
  • name_from_tag – returns the language name associated with the provided IETF language tag:
    • {{lang|fn=name_from_tag|apa}}Lua error: Internal error: The interpreter exited with status 127.
  • 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}}Lua error: Internal error: The interpreter exited with status 127.
  • transl – the function that renders Lua error: Internal error: The interpreter exited with status 127.; listed here for completeness, this particular usage is more-or-less pointless
    • {{lang|fn=transl|ar|DIN|al-Ḫawārizmī}}Lua error: Internal error: The interpreter exited with status 127.

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|تاجیکی}}, ''{{lang|tg-Latn|toçikī}}'', {{lang|tg-Cyrl|тоҷикӣ}})
Tajik (Lua error: Internal error: The interpreter exited with status 127., Lua error: Internal error: The interpreter exited with status 127., Lua error: Internal error: The interpreter exited with status 127.)

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 Lua error: Internal error: The interpreter exited with status 127.:

  • Moscow ({{lang|ru|Москва}}, {{transliteration|ru|Moskva}}) → Moscow (Lua error: Internal error: The interpreter exited with status 127., Lua error: Internal error: The interpreter exited with status 127.)

To specify a transliteration scheme, such as the ISO transliteration standard for Cyrillic, use Lua error: Internal error: The interpreter exited with status 127..

Undetermined language

The Lua error: Internal error: The interpreter exited with status 127. 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 Lua error: Internal error: The interpreter exited with status 127. 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 Han character has 6 strokes.

Languages with no code

Use the code "mis" (Miscellaneous) for 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: Internal error: The interpreter exited with status 127., Lua error: Internal error: The interpreter exited with status 127.)

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. Lua error: Internal error: The interpreter exited with status 127.

Links

If the {{lang}} template will have to be combined with links one might be tempted to move the {{lang}} template into the link so that it would only frame the link's text label, not the syntax elements of the links or other stylistic elements of some types of links. However, this does not work. The {{lang}} will have to wrap the entire link, regardless if it is an internal or external link, or a link provided through a {{ill}} interwiki link template:

Works:

  • {{lang|en|[[Book of hours]]}}Lua error: Internal error: The interpreter exited with status 127.
  • {{lang|de|[[Book of hours|Stundenbuch]]}}Lua error: Internal error: The interpreter exited with status 127.
  • {{lang|he-LA|{{ill|Machsor Lipsiae|de}}}}Lua error: Internal error: The interpreter exited with status 127.

Does not work:

Rationale

Lua error: Internal error: The interpreter exited with status 127. 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 Lua error: Internal error: The interpreter exited with status 127. and these comparison tables with a screenshot.
  • For accessibilityscreen 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 re-use.
  • Useful for application developers who re-publish Wikipedia (also see Lua error: Internal error: The interpreter exited with status 127.).
  • 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|ٹھنڈ میں، ایک قحط زدہ گاؤں سے گزرتے وقت ایک چڑچڑے، بااثر و فارغ شخص کو بعض جل پری نما اژدہے نظر آئے۔}}

Lua error: Internal error: The interpreter exited with status 127.Lua error: Internal error: The interpreter exited with status 127.

Tracking categories

  • [[:Category:Lua error: Internal error: The interpreter exited with status 127.|Category:Lua error: Internal error: The interpreter exited with status 127.]] (0)
  • [[:Category:Lua error: Internal error: The interpreter exited with status 127.|Category:Lua error: Internal error: The interpreter exited with status 127.]] (0)
  • [[:Category:Lua error: Internal error: The interpreter exited with status 127.|Category:Lua error: Internal error: The interpreter exited with status 127.]] (0)

TemplateData

This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. Click here to see a monthly parameter usage report for this template based on this TemplateData.

TemplateData for Lang

Lua error: Internal error: The interpreter exited with status 127.

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

References

  1. "Language tags in HTML and XML" at World Wide Web Consortium
  2. Lua error: Internal error: The interpreter exited with status 127.
  3. 3.0 3.1 3.2 Lua error: Internal error: The interpreter exited with status 127.
  4. Lua error: Internal error: The interpreter exited with status 127.

Lua error: Internal error: The interpreter exited with status 127.

External links

  • W3C
  • IANA
    • IANA Language Subtag Registry
    • Tags for Identifying Languages (Lua error: Internal error: The interpreter exited with status 127.)
    • Matching of Language Tags (Lua error: Internal error: The interpreter exited with status 127.)
    • Language tags (obsolete per Lua error: Internal error: The interpreter exited with status 127.)
  • Mozilla Firefox