ISO 639-2/T

ISO 639

仕様書

[5] 2文字言語符号、3文字言語符号については言語部分タグ参照。

国内規格

[4] KS X ISO 639-1:2002

文脈

[1] ISO 639言語符号を使う場面

[7] DSSSL, , http://www.y-adagio.com/public/standards/jis_dsssl/cls12.txt

(45) 特質language:は,#f又はISO 639で定義する言語コードを大文字で指定する。これは,行の組立てに処理系固有の方法で影響する。初期値は#fとする。

歴史

ISO 639-6

[14] ISO 639-6:2009 は、言語符号を定めていた国際規格の1つでした。 >>8, >>13

[15] 方言レベルの粒度の言語ラテン文字4文字の符号で表そうとしていました。 >>8, >>13

[16] しかしうまく運用できる見込みがなく、完全なリストが公表されることなく廃止されたといいます。 >>8, >>20

[19] >>18 >>17 規格本文の冒頭。

[21] Microsoft Word - tc37-nwip-cmt.docx - 16132-tc37-nwip-cmt.pdf, , https://unicode.org/L2/L2016/16132-tc37-nwip-cmt.pdf

メモ

[9] Textus Text Format - Textus - An Open Platform for Working With Cultural and Historial Texts - Open Knowledge Foundation (Open Knowledge Foundation Labs著, ) http://okfnlabs.org/textus/doc/textus-format.html

The optional ‘lang’ property in the payload can be used to specify the ISO 939-2 code for the language of the comment. If omitted the default is to assume a comment in English, so the above example is not actually necessary (there is no distinction in that particular ISO standard between British and American English, for example, but I doubt that’s something we have to worry about).

[10] JSON API Reference | Worldpay Developer () https://developer.worldpay.com/jsonapi/api#orders

shopperLanguageCode: String, optional

ISO ISO 639-1 language code indicating the preferred language of the shopper, where supported by the Payment Provider.

[11] () https://info.quantcast.com/rs/516-DGM-318/images/Framework%20Vendor%20List%20%26%20Cookie%20Format%20Specification.pdf

Translations to non-English languages of the purposes will be hosted at

https://vendorlist.consensu.org/purposes-language.json with older versions at

https://vendorlist.consensu.org/v-versionnum/purposes-language.json where language is the

two-letter lowercase ISO 639-1 language code.

[12] () https://info.quantcast.com/rs/516-DGM-318/images/Framework%20Vendor%20List%20%26%20Cookie%20Format%20Specification.pdf

ConsentLanguage 12 bits Two-letter ISO639-1

language code that

CMP asked for

consent in

Each letter should be encoded as 6 bits,

a=0..z=25 . This will result in the base64-

encoded bytes spelling out the language

code (in uppercase).

[2] Akoma Ntoso Naming Convention Version 1.0 () https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/os/akn-nc-v1.0-os.html#_Toc409028148

    The human language code in which the Expression is drafted (a three-letter code according to ISO 639-2 alpha-3). For an Akoma Ntoso XML representation, this value MUST correspond to the content of the first element <FRBRlanguage> in the metadata section. According with ISO 639-2 alpha-3 “mul” means multilingual document (text with different languages), while “und” means undetermined language

[3] Z39.82-200x TOC/F'word - https://groups.niso.org/apps/group_public/download.php/6541/, https://groups.niso.org/apps/group_public/download.php/6541/