* 仕様書 - [6] [CITE@en[ISO Standards Maintenance Portal]], [[ISO (International Organization for Standardization)]], [TIME[2023-11-10T11:59:42.000Z]] * 値 [5] 2文字言語符号、3文字言語符号については[[言語部分タグ]]参照。 * 国内規格 [4] [DFN[KS X ISO 639-1:2002]] * 文脈 [FIG(short list)[ [1] [[ISO 639言語符号]]を使う場面 - [[言語タグ]]の[[言語部分タグ]] - [[公式公開識別子]] - [[Android]] [[設定修飾子]] - [[Macintosh言語符号]] - [[skf言語]] ]FIG] [7] [CITE[DSSSL]], [TIME[2001-08-19T05:28:49.000Z]], [TIME[2023-11-23T08:14:19.063Z]] > (45) 特質language:は,#f又はISO 639で定義する言語コードを大文字で指定する。これは,行の組立てに処理系固有の方法で影響する。初期値は#fとする。 * 歴史 ** ISO 639-6 [14] [DFN[ISO 639-6:2009]] は、[[言語符号]]を定めていた[[国際規格]]の1つでした。 [SRC[>>8, >>13]] [15] [[方言]]レベルの粒度の[[言語]]を[[ラテン文字]]4文字の[[符号]]で表そうとしていました。 [SRC[>>8, >>13]] [16] しかしうまく運用できる見込みがなく、完全なリストが公表されることなく廃止されたといいます。 [SRC[>>8, >>20]] [REFS[ - [8] [CITE@en[[[ISO 639-6]] - Wikipedia]], [TIME[2024-04-03T00:16:06.000Z]], [TIME[2024-04-04T13:15:12.859Z]] - [13] [CITE@en[List of [[ISO 639-6]] codes - Wikipedia]], [TIME[2024-03-31T18:18:48.000Z]], [TIME[2024-04-04T13:15:56.430Z]] - [20] [CITE[FYI: withdrawal of ISO 639-6]], [TIME[2014-11-09T21:57:25.000Z]], [TIME[2024-04-04T13:28:26.596Z]] ]REFS] - [18] [CITE@ja[SIST-ISO-639-6-2010.pdf]], [TIME[2021-01-26T20:16:52.000Z]], [TIME[2024-04-04T13:28:10.288Z]] - [17] [CITE@ja[ISO-639-6-2009.pdf]], [TIME[2021-01-23T14:32:52.000Z]], [TIME[2024-04-04T13:27:59.858Z]] [19] >>18 >>17 規格本文の冒頭。 [21] [CITE@ja[Microsoft Word - tc37-nwip-cmt.docx - 16132-tc37-nwip-cmt.pdf]], [TIME[2016-05-06T20:44:07.000Z]], [TIME[2024-04-04T13:28:43.745Z]] [22] 関連: [[中文言語タグ]] * メモ [FIG(quote)[ [FIGCAPTION[ [9] [CITE@en[Textus Text Format - Textus - An Open Platform for Working With Cultural and Historial Texts - Open Knowledge Foundation]] ([[Open Knowledge Foundation Labs]]著, [TIME[2015-03-22 11:08:57 +09:00]]) ]FIGCAPTION] > 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). ]FIG] [FIG(quote)[ [FIGCAPTION[ [10] [CITE[JSON API Reference | Worldpay Developer]] ([TIME[2017-02-14 01:34:22 +09:00]]) ]FIGCAPTION] > shopperLanguageCode: String, optional > ISO ISO 639-1 language code indicating the preferred language of the shopper, where supported by the Payment Provider. ]FIG] [FIG(quote)[ [FIGCAPTION[ [11] ([TIME[2018-02-09 09:49:38 +09:00]]) ]FIGCAPTION] > 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. ]FIG] [FIG(quote)[ [FIGCAPTION[ [12] ([TIME[2018-02-09 09:49:38 +09:00]]) ]FIGCAPTION] > 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). ]FIG] [FIG(quote)[ [FIGCAPTION[ [2] [CITE@EN-US[Akoma Ntoso Naming Convention Version 1.0]] ([TIME[2019-02-22 02:00:00 +09:00]]) ]FIGCAPTION] >     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 in the metadata section. According with ISO 639-2 alpha-3 “mul” means multilingual document (text with different languages), while “und” means undetermined language ]FIG] [3] [CITE[Z39.82-200x TOC/F'word - https://groups.niso.org/apps/group_public/download.php/6541/]], [TIME[2020-10-13T02:01:21.000Z]]