%% の後に
lang」
と略されることがよくあります。tag」や「langtag」などと略されることもあります。
例えば、
ja-Latn-US... は、3つの
ja Latn US t zh-Latn-CN-variant1-a-extend1-x-wadegile-private1zh-Latn-CN-variant1-a-extend1-x-wadegilezh-Latn-CN-variant1-a-extend1zh-Latn-CN-variant1zh-Latn-CNzh-Latnzh- ... という制限しかありませんでした
- ... という制限になりました
x i
ScriptLangTag
では、
t拡張T : 変換u拡張U : s も提案されていましたが、 t に統合されました。
ScriptLangTag を規定する ScriptLangTag 用に定義された
ScriptLangTag 用だと規定がない限りは、
ScriptLangTag では使えないということでしょうか。
en-US en-X-US ScriptLangTag では、
ScriptLangTag
では、
他の
ScriptLangTag 全体をx-liis* を使っています。
x-d-* が提案されています。
<html
lang="en"
dir="ltr"><html
lang="id-x-mtfrom-en"
dir="ltr"><html
lang="zh-TW-x-mtfrom-en"
dir="ltr"><html
lang="ar-x-mtfrom-en"
dir="rtl"><html
lang="th-x-mtfrom-en"
dir="ltr">x-mtfrom-en が付く。
-x-autogen
を使っています。
en-x-autogen
だけで
TextTrack の languageja-x-autogen、
label日本語 (自動生成)
となるものが利用されていることが確認できます。
language
x-autogen は
To enable automatically generated closed captions instead, provide the value
en-x-autogen. Please note that, at the present time, automatic captions are always in English.
埋め込みコードのように自動生成されたキャプションを追加するには、"texttrack=en-x-autogen"を追加する必要があります。
grandfathered = 1*3... という構文を認めていましたALPHA 1*2("-" 2*8(ALPHA /DIGIT ))
"en-GB-oed" / "i-ami" / "i-bnn" / "i-default" / "i-enochian" / "i-hak" / "i-klingon"
/ "i-lux" / "i-mingo" / "i-navajo" / "i-pwn" / "i-tao" / "i-tay" / "i-tsu" / "sgn-BE-FR"
/ "sgn-BE-NL" / "sgn-CH-DE"irregular に分類されている
"art-lojban" / "cel-gaulish" / "no-bok" / "no-nyn" / "zh-guoyu"
/ "zh-hakka" / "zh-min" / "zh-min-nan" / "zh-xiang"regular に分類されている
irregular の使用は禁止されています。
ScriptLangTag は
i-default
i-*
es-Latn-CO-x-private に es-CO は接頭辞として含まれています。
...
ja は
<html xmlns="http://www.w3.org/1999/xhtml" lang="ja-JP.UTF-8" xml:lang="ja-JP.UTF-8">
<meta http-equiv='CHARSET' content='EUC-JP'> <meta http-equiv='CONTENT-LANGUAGE' content='Japanese'> <meta http-equiv='Content-Type' content='text/html; charset=EUC-JP'>
<html lang="en_US">
<html lang="de_DE">
<html lang="en_us" prefix="og: http://ogp.me/ns#">
<html lang="en_us" prefix="og: http://ogp.me/ns#">
<!doctype html>
<html lang="ja,zh">
The locale is set in RFC-3066 format using the lang parameter:
lang=language-region
language - Two-letter language code. Specified in ISO 639-1 format. Sets the language for objects on the map (toponyms and controls).
region - Two-letter country code. Specified in ISO 3166-1 format. Determines regional settings such as measurement units (for indicating distances between objects or driving speeds on a route).
Note. For the regions RU, UA and TR, distance is shown in kilometers; for US, it is shown in miles.
The following locales are currently supported:
lang=tr-TR
lang=en-US (distance in miles)
lang=en_RU
lang=ru-RU
lang=ru_UA
lang=uk_UA
Note. In early versions of the API, the locale was specified after a dash. For example, en-US. This notation is supported for backward compatibility, but is not recommended.
A code that indicates the language of the article. Use the IANA.org language subtag registry to find the appropriate code; e.g., en for English, or the more specific en_GB for English (U.K.) or en_US for English (U.S.).
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US.UTF-8" xml:lang="en-US.UTF-8">
<html lang="zh_tw">
fa_IR や zh_Hans_CN 式の不正な
<!DOCTYPE html> <!-- jsn_solid_pro 5.1.6 --> <html lang="*" dir="ltr">
_
を使ったり、
-
を使ったりする誤用例が散見され、それによる不具合もまま見かけます。
ややこしいことに- を使うものもあります。
u va ja-JP-mac ja-jpm
Content-Language:
Accept-Language:
lang hreflang
xml:lang
lang-
;lang=
The language associated with a resource. The default type of this property is 'RFC1766' and the vocabulary is drawn from the list of languages in RFC 1766 [4]. If RFC 1766 is updated, then the values listed in the updated version are also valid for this type.
name (OpenType)
"-" を使う方法ではなく "_" で区切っていました。
"-" の代わりに "." を使っていました。 (The Body Element and Related Elements
The term 'language tag' should be reserved for the short identifier of RFC 1766 [RFC-1766] that only serves to identify the language. While there may be other text attributes intimately associated with the language of the document, such as desired font or text direction, these should be specified with other identifiers rather than overloading the language tag.
A language tag identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information to other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and Content-Language fields.
言語札識別子は、人間が他の人間と情報の通信をするために話したり書いたりその他伝達する自然言語を識別します。
計算機言語は陽に除外します。 HTTP
は
The syntax and registry of HTTP language tags is the same as that defined by RFC 1766 [1]. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags:
HTTP 言語札の構文と登録簿は
- language-tag = primary-tag *( "-" subtag )
- primary-tag = 1*8ALPHA
{2068,2616} subtag = 1*8ALPHA- {Errata} subtag = 1*8(ALPHA / DIGIT)
White space is not allowed within the tag and all tags are case-insensitive. The name space of language tags is administered by the IANA. Example tags include:
en, en-US, en-cockney, i-cherokee, x-pig-latin
where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered in future.)
ここで、2文字の主札は
だいぶ変わってるな・・・。
Content-Language:Accept-Language:;lang=@ (RDF)ScriptLangTag
は
dc:language
- ではなく _ を区切りにしていますが、
%LanguageCode; 型 (HTML 4)%LanguageCode 型は、
%LanguageCode (LanguageCode (language-code(
NAME NMTOKEN
では HTML 4 で新しい構文の言語札を使っても良いのか、 微妙なところです。
引用規格は最新版を適用するかどうかの規定はないのですけど、
lang 属性は XML
言語符号の
No linguistic content
を表すUsed to declare the absence of linguistic information
。
(
2006-12-19 13:39:55 +09:00 版)
Human-readable Claim Values and Claim Values that reference human-readable values MAY be represented in multiple languages and scripts. To specify the languages and scripts, BCP47 [RFC5646] language tags are added to member names, delimited by a # character. For example, family_name#ja-Kana-JP expresses the Family Name in Katakana in Japanese, which is commonly used to index and represent the phonetics of the Kanji representation of the same represented as family_name#ja-Hani-JP. As another example, both website and website#de Claim Values might be returned, referencing a Web site in an unspecified language and a Web site in German.
To specify the languages and scripts, BCP47 [RFC5646] language tags are added to Client Metadata member names, delimited by a # character.
When language is specified, the language tag MUST use the RFC 3066
[LANGCODES] syntax.
カタロニア語(バレンシア) [ca-ES-valencia] を文書の内容として利用できるようになりました。 tdf#68714 (Eike Rathke)
カタロニア語(バレンシア) のUI翻訳として当座しのぎで [ca-XV] を使っていたのを、正しく [ca-ES-valencia] タグを用いるようになりました。 (Eike Rathke)
当座しのぎで [sh-*] という文書言語としていたものを、正しく [sr-Latn-*] とするように、古い [sh-*] も扱えるようにしました。 (Eike Rathke)
言語リストに [en-GB-oed] ルール外(grandfathered)タグを "English, Oxford English Dictionary spelling" 用として追加しました。 (Eike Rathke)
ラテン綴りで書かれたクルド語 [ku-*] の汚いマクロ言語のコードを綺麗にし、それぞれの国ごとに区別したスクリプトで処理するようにしました。 tdf#63460 (Eike Rathke)
ku → kmr-Latn (北部クルド語、ラテン綴り)
ku-TR → kmr-Latn-TR (トルコでの北部クルド語、ラテン綴り)
ku-SY → kmr-Latn-SY (シリアでの北部クルド語、ラテン綴り)
ku-IQ → ckb-IQ (イラクでの中部クルド語、アラビア綴り)
ku-IR → ckb-IR (イランでの中部クルド語、アラビア綴り)
追加: sdh-IQ (イラクでの南部クルド語、アラビア綴り)
<englishName>Sorani Kurdish</englishName>
<codes>
<code>
<standard>
<name>FB</name>
<representation>cb_IQ</representation>
</standard>
</code>
</codes>
<englishName>Cherokee</englishName>
<codes>
<code>
<standard>
<name>FB</name>
<representation>ck_US</representation>
</standard>
</code>
</codes>
To specify the languages and scripts, BCP 47 [RFC5646] language tags
are added to client metadata member names, delimited by a "#"
character. Since JSON [RFC7159] member names are case sensitive, it
is RECOMMENDED that language tag values used in Claim Names be
spelled using the character case with which they are registered in
the "IANA Language Subtag" registry [IANA.Language]. In particular,
normally language names are spelled with lowercase characters, region
names are spelled with uppercase characters, and languages are
spelled with mixed-case characters. However, since BCP 47 language
tag values are case-insensitive, implementations SHOULD interpret the
language tag values supplied in a case insensitive manner. Per the
recommendations in BCP 47, language tag values used in metadata
member names should only be as specific as necessary. For instance,
using "fr" might be sufficient in many contexts, rather than "fr-CA"
or "fr-FR".
An implementation MUST treat language identifiers that [BCP 47] defines as equivalent as identifying the same language. For example "mn" and "MN" are equivalent, as language tags are case insensitive, and "de" and "deu" are equivalent, as they are different codes for the same language. However, it is implementation-defined whether an implementation treats a particular language identifier with script, region, or variant portions as equivalent to the language identifier without them. For example, an implementation may treat "en-UK" as equivalent "en" and "en-US" but "sr-Latn" as different from "sr" and "sr-Cyrl".
locales引数は、すべてのUnicode拡張を除去した後、アプリケーションからの優先順位付き要求として解釈されます。ランタイムは、利用可能なローケルと比較し、利用可能なもののうち一番よいローケルを選びます。マッチングアルゴリズムは"lookup" matcherと"best fit" matcherの二つです。"lookup" matcher は、BCP 47で指定されたLookupアルゴリズムに従います。"best fit" matcher では、少なくとも "lookup" matcher と同程度の、しかし可能ならより要求に適したロケールを選択します。
The value of the property should be a language code following the [bcp47] specification.
Language: The "language" item (CAtype 0) optionally identifies the
language used for presenting the address information, drawing from
the tags for identifying languages in [4], as discussed in [13].
If omitted, the default value for this tag is "i-default" [3].
Language: The "language" item (CAtype 0) optionally identifies the
language used for presenting the address information, drawing from
the tags for identifying languages in [4], as discussed in [13].
If omitted, the default value for this tag is "i-default" [3].
In older versions you might see these language entries instead:
* {art-Cyrl-x-interslv}
* {art-Latn-x-interslv}
In Britanny and Normandy, there are also the "Gallo" and "Norman" languages but they still have no specific ISO 639 code assigned (they may be represented in conforming BCP 47 tags as "fr-gallo" or "fr-x-norman" using a private extension only to collect the data, that won't be used interoperably before there's a documented agreement on which subtags to use; for Norman the assigned code "nrf" refers ambiguously to modern Jersiais, Guernésiais or Continental Norman and don't seem to discriminate their own local dialects, so it would still safely replace the "fr-x-norman" private use extension of French, or we could use "nrf-FR" font continental Norman, "nrf-JE" for Jersiais, and "nrf-GG" for Guernésiais if a distinction is really needed at the same place).