Search results
Page title matches
- 3 KB (373 words) - 19:17, 6 December 2020
Page text matches
- ...list of the languages) in which the source is written, as either the [[ISO 639]] language code (preferred) or the full language name. Examples: {{para|lan1 KB (171 words) - 19:17, 6 December 2020
- script -> ISO 15924 script tags region -> ISO 3166 region tags20 KB (2,299 words) - 19:17, 6 December 2020
- ...Module:Lang/ISO 639 synonyms'); -- ISO 639-2/639-2T code translation to 639-1 code if synonym_table[code] then -- if 639-2/639-2T code has a 639-1 synonym69 KB (10,770 words) - 19:17, 6 December 2020
- which became part of ISO 8601 in 2019. See '§Sub-year groupings'. The standard defines various di should be out of the ISO 8601 (EDTF) range of uses for a while.81 KB (10,495 words) - 19:17, 6 December 2020
- 2char – list of ISO 639-1 codes and names sorted by code 3char – list of ISO 639-2, -3 codes and names sorted by code36 KB (5,374 words) - 19:17, 6 December 2020
- ...es with \"in\" before the language name. Use the full language name or ISO 639-1 code.",14 KB (1,608 words) - 19:18, 6 December 2020
- ...ure. The value in |script-title= may be prefixed with a two-character ISO 639-1 language code and a colon: The prefix is checked for validity. If it is a valid ISO 639-1 language code, the lang attribute (lang="ja") is added to the <bdi> tag s200 KB (29,753 words) - 19:17, 6 December 2020
- ...follows transliteration defined in chapter. Should be prefixed with an ISO 639-1 two-character code to help browsers properly display the script",55 KB (5,931 words) - 19:18, 6 December 2020
- ...here <code>xx</code> or <code>xxx</code> is a valid [[ISO 639-1]] or [[ISO 639-3]] language code known to CS1|2 as a language that uses a non-Latin script116 KB (17,474 words) - 19:17, 6 December 2020