You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A language declaration that indicates the text-processing language for a range of text must associate a single language value with a specific range of text. more Comments_go_here
Use the HTML lang and XML xml:lang language attributes where appropriate to identify the text processing language, rather than creating a new attribute or mechanism. more Comments_go_here
It should be possible to associate a metadata-type language declaration (which indicates the intended use of the resource rather than the language of a specific range of text) with multiple language values. more Comments_go_here
Attributes that express the language of external resources should not use the HTML lang and XML xml:lang language attributes, but should use a different attribute when they represent metadata (which indicates the intended use of the resource rather than the language of a specific range of text). more I don't think we link to any external resources, so this should not apply to us
Defining language values
Values for language declarations must use BCP 47. more Comments_go_here
Refer to BCP 47, not to its constituent parts, such as RFC 5646 or RFC 4647. more Comments_go_here
Be specific about what level of conformance you expect for language tags: BCP 47 defines two levels of conformance, "valid" and "well-formed". more Comments_go_here
Specifications may require implementations to check if language tags are "valid", but in most circumstances should only require that the language tags be "well-formed". more Comments_go_here
Specifications should require content and content authors to use "valid" language tags. more Comments_go_here
Specifications SHOULD refer to the IANA Language Subtag Registry instead of providing lists of codes extracted from ISO 639, ISO 3166, or other standards. more Comments_go_here
Avoid creating a list of valid or supported language tags, language subtags, or locales. more Comments_go_here
Declaring language
The specification should indicate how to define the default text-processing language for the resource as a whole. more Comments_go_here
Content within the resource should inherit the language of the text-processing declared at the resource level, unless it is specifically overridden. more Comments_go_here
Consider whether it is necessary to have separate declarations to indicate the text-processing language versus metadata about the expected use of the resource. more Comments_go_here
If there is only one language declaration for a resource, and it has more than one language tag as a value, it must be possible to identify the default text-processing language for the resource. more Comments_go_here
By default, blocks of content should inherit any text-processing language set for the resource as a whole. more Comments_go_here
It should be possible to indicate a change in language for blocks of content where the language changes. more Comments_go_here
It should be possible to indicate language for spans of inline text where the language changes. more Since we return highly structured JSON and have a mechanism to set the language for each object, I don't think this applies to us
Identifying the language of strings (TBD)
Detecting & matching language
Reference BCP47 for language tag matching. more Comments_go_here
The text was updated successfully, but these errors were encountered:
This is a self-review checklist based on the Internationalization Best Practices for Spec Developers.
(All lines seemed relevant for us here, I suggest we
strikeoutthings that turn out not to be.)See also issue #52, PR #108 and notes at https://etherpad.lobid.org/p/reconciliation-i18n.
Check marks indicate requirements that are fulfilled by this spec. Add comments to describe conformance.
Language basics
Comments_go_here
Comments_go_here
Comments_go_here
Comments_go_here
lang
and XMLxml:lang
language attributes where appropriate to identify the text processing language, rather than creating a new attribute or mechanism. moreComments_go_here
Comments_go_here
Attributes that express the language of external resources should not use the HTML
I don't think we link to any external resources, so this should not apply to uslang
and XMLxml:lang
language attributes, but should use a different attribute when they represent metadata (which indicates the intended use of the resource rather than the language of a specific range of text). moreDefining language values
Comments_go_here
Comments_go_here
Comments_go_here
Comments_go_here
Comments_go_here
Comments_go_here
Comments_go_here
Declaring language
Comments_go_here
Comments_go_here
Comments_go_here
Comments_go_here
Comments_go_here
Comments_go_here
It should be possible to indicate language for spans of inline text where the language changes. more
Since we return highly structured JSON and have a mechanism to set the language for each object, I don't think this applies to usIdentifying the language of strings (TBD)
Detecting & matching language
Comments_go_here
The text was updated successfully, but these errors were encountered: