မဝ်ဂျူ:languages/data/3/d/doc

This module contains definitions and metadata for three-letter language codes starting with "d". See Wiktionary:Languages for more information.

This module must not be used directly in other modules or templates. The data should be accessed through Module:languages. For the corresponding extra data, see မဝ်ဂျူ:languages/data/3/d/doc/extra.

Errors

The following errors were detected by Module:data consistency check:

Required values

Every entry in the table must contain the following indexed fields:

1

The "canonical" name of the language. This is the name that is used in Wiktionary entries and category names.

2

The Wikidata item id (Q number) for the language. Can be specified as a number (a positive integer) or a string that starts with Q and ends with decimal digits. Set to nil if not known/present. This replaces the older wikipedia_article property, which can still be used to link to specific sections or language editions.

Optional values

3

The code for the family that the language belongs to. See Wiktionary:Families.

4

A list of script codes. See Wiktionary:Scripts. These represent all the scripts (writing systems) that this language uses in the real world, as well as the ones that Wiktionary uses. The scripts that are used most often on Wiktionary should be first in the list, as this will speed up script detection.

Many templates and modules detect the script of text in a particular language using the findBestScript function in Module:scripts. This function goes down the list of scripts and counts how many characters in the text belong to each script. If all the characters belong to one script, that script will be returned; otherwise, the script with the most characters will be returned. Thus, script detection will be faster if the most frequently used scripts are first in the list. If none of the characters match any of the listed scripts, then the None script is returned (even if the characters would match a script not listed). Translingual (mul) and Undetermined (und) have the special value "All", which means they are treated as having every script. This value should not be set for any other language codes.

Due to the ongoing problems with Lua memory limits, this should be given as a comma-separated list in a string (and not a table). This is then converted into a table when returned. For example: "Latn, Brai, Shaw, Dsrt".

type

The type of language (which affects how it is handled on Wiktionary). Possible values are:

• regular - This value is the default, so it doesn't need to be specified. It indicates that the is attested according to WT:CFI and therefore permitted in the main namespace. There may also be reconstructed terms for the language, which are placed in the Reconstruction namespace and must be prefixed with * to indicate a reconstruction.
• reconstructed - This language is not attested according to CFI, and therefore is allowed only in the Reconstruction namespace. All terms in this language are reconstructed, and must be prefixed with *.
• appendix-constructed - This language is attested but does not meet the additional requirements set out for constructed languages (WT:CFI#Constructed languages). Its entries must therefore be in the Appendix namespace, but they are not reconstructed and therefore should not have * prefixed in links.

ancestors

A list of the language codes of the direct ancestors of this language. For example, the ancestor of English is listed as enm (Middle English); ang (Old English, the ancestor of Middle English), gem-pro (Proto-Germanic, the ancestor of Old English), and ine-pro (Proto-Indo-European, the ancestor of Proto-Germanic) are not listed.

For most languages, only one ancestor code should be given, but multiple ancestors can be listed for pidgins, creoles and mixed languages.

The ancestor language list should not be included if the language's direct ancestor is the proto-language of the family to which the language belongs. In such a case, if the family code has been provided, Module:languages will automatically add the proto-language as the language's ancestor. For example, Proto-Germanic (gem-pro) belongs to the Indo-European (ine) family, and its direct ancestor is Proto-Indo-European (ine-pro). Because Proto-Indo-European is the proto-language of the Indo-European languages, Proto-Germanic does not need an ancestors table; Proto-Indo-European will be automatically returned as its ancestor by the getAncestors function.

Due to the ongoing problems with Lua memory limits, this should be given as a comma-separated list in a string (and not a table). This is then converted into a table when returned. For example: "cr, fr".

wikimedia_codes

A list of the Wikimedia language codes that this language maps to. This is used to translate Wiktionary codes to Wikimedia codes, which are usually the same but there are a few languages where it is different. The language codes must be valid Wikimedia codes (as determined by the wiki software), and if they are not defined in one of the language data modules, they must be defined in Module:wikimedia languages/data.

Due to the ongoing problems with Lua memory limits, this should be given as a comma-separated list in a string (and not a table). This is then converted into a table when returned. For example: "en, simple".

wikipedia_article

The name of the Wikipedia article for the language. Should normally only be supplied if the Wikidata id cannot be used.

translit

See the Substitutions section for instructions on syntax.

Defines how a language should be transliterated, which will be automatically applied to any terms in scripts that do not have their isTransliterated value set to false in Module:scripts/data. This is used by transliterate in Module:languages.

link_tr

Set this to true to link the language's transliteration. For instance, Gothic has entries in Gothic script and entries for transliterations: 𐌷𐌻𐌰𐌹𐌱𐍃 (hlaibs).

display_text

See the Substitutions section for instructions on syntax.

Defines replacements to create the display form of the text, which is the form actually displayed on the page. This is occasionally necessary if there is a recurring issue of editors adding the wrong character, which is sometimes an issue when two or more characters are easy to confuse. For example, the palochka ӏ, used in Cyrillic in many Caucasian languages, is frequently entered as I, or even Latin l or I. As this is an ongoing issue (even among native speakers), the easiest way to solve the problem is to automatically correct the display form for those languages. This is used by makeDisplayText in Module:languages.

entry_name

See the Substitutions section for instructions on syntax.

Defines replacements to create the entry name from the displayed form of a term. This can be used to remove certain diacritical marks according to the customs or standard practice of the language. For example, it is used to remove accent marks from Russian words (ру́сский → русский), or macrons from Latin or Old English words (ōs → os), as these are not used in the normal written form of these languages. This is used by makeEntryName in Module:languages.

sort_key

See the Substitutions section for instructions on syntax.

Defines replacements to create a category sort key from the page name. The purpose is to:

1. Remove any characters that should be ignored in sorting.
2. Replace characters with other characters, if the sorting rules for that language do not distinguish them. For example, in German, the characters "ä" and "a" are considered equivalent for sorting, and are both treated as "a".
3. Replace characters that should be sorted in different places with special characters that mimic that behaviour, (which is necessary due to MediaWiki software using the Unicode codepoint to determine sort order, which is often arbitrary). For instance, in Mongolian, the letter "ү" should be sorted after "у", but due to its codepoint it is sorted after the final letter "я" by default. As such, we can replace "ү" with "у" plus a character with a very high codepoint, which ensures that it is always sorted straight after. The data modules contain an in-built way to do this for the sake of convenience: with the above example, this would be done by using "у" .. p[1]. Another character could be inserted straight after by using "у" .. p[2] (and so on).

Note: the term is converted to lowercase before applying any substitutions, so you should not try to process capital letters (as it will not work). This is used by makeSortKey in Module:languages.

dotted_dotless_i

Set this to true for languages that distinguish between the dotted and dotless I (such as some Turkic languages).

Substitutions

translit, display_text, entry_name and sort_key all use the same syntax, which is designed to be as flexible as possible:

• If they are a string, then this is treated as the name of a dedicated module which will be used to generate the output. For example, "sa-translit" refers to Module:sa-translit.
• If they are a table, then it can contain two kinds of keys:
  1. The keys from, to, remove_diacritics and remove_exceptions relate to text substitution (see below).
  2. Script code keys are used to specify script-specific behaviour. These, in turn, can be strings (for dedicated modules) or tables (for text substitution). In addition, a value with the key 1 can be used as a fallback, which will be used if no specific behaviour is defined for that script.

Note: if script keys and text substitution keys are given in the same table, then the text substitution will be applied after the script-specific behaviour has completed. Ensure any fallback text substitutions are given as a subtable with key 1 if you want to avoid this. It is not possible to process the output of a script-specific module with another module, however: this should be done (for example) with a tail call in the first module.

Dedicated modules must take the arguments text, lang, sc, where text is the input text (usually the page name or input by the user), lang is the language code (not the language object), and sc is the script code (not the script object). For performance reasons, they should only be used when it is not possible to achieve the desired result via text substitution.

Text substitution replaces or removes certain characters (or sets of characters) for particular contexts. There are three ways to do this:

1. Using the from and to keys.
2. remove_diacritics (and optionally remove_exceptions).
3. Both of the above (in that order).

from is paired with to, and both of them must be tables that are organised pairwise: each element in from is a pattern to identify which characters in the term to replace, while the corresponding element in to defines what to replace them with (as arguments to mw.ustring.gsub).

If the replacement is not present (or if it is false or nil), then any matching characters are removed altogether. This means that the from list can be longer than the to list, and an empty replacement will be assumed for any elements in from that have no counterpart in to.

The tables can contain literal characters, or the patterns (a simplified form regular expressions) that are used by the standard Scribunto mw.ustring.gsub function. See the Scribunto reference manual for more information. Note that patterns make double substitutions a viable way to achieve more complex results. See the Latin sortkey for Mandarin (cmn) as an example of this.

remove_diacritics is a string which contains characters that will be removed after the text is decomposed. For instance, if remove_diacritics is a combining acute accent, all acute accents will be stripped, even if they are part of precomposed characters (such as á or ά). Despite the name, the characters to be stripped need not be diacritics: for instance, including an apostrophe would remove all apostrophes (though be careful with hyphens, which must be be escaped as %-).

Furthermore, if remove_diacritics is given, then it is possible to specify a remove_exceptions table, which prevents specific characters from having their diacritics stripped. For instance, if remove_diacritics is a combining diaeresis, but remove_exceptions contains "ё", then any instances of ё will remain unchanged. On the other hand, an instance of ӱ would still become у (unless "ӱ" is also added to remove_exceptions).

Formerly supported values

aliases, varieties, otherNames

This data is now located in the extra data modules; see Module:languages and Template:language extradata documentation.

family

Now 3.

scripts

Now 4.