Test page: Detailed review checklist

[r12a]

Detailed internationalisation review checklist

Check marks indicate requirements that are fulfilled by this spec. Add comments to describe conformance.

This checklist was created here.

2. Language

Language basics

1. It should be possible to associate a language with any piece of localizable text or natural language content. more
   Comments_go_here
2. Where possible, there should be a way to label natural language changes in inline text. more
   Comments_go_here
3. Consider whether it is useful to express the intended linguistic audience of a resource, in addition to specifying the language used for text processing. more
   Comments_go_here
4. 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

Defining language values

1. Values for language declarations must use BCP 47. more
   Comments_go_here
2. Refer to BCP 47, not to RFC 5646. more
   Comments_go_here
3. 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

Declaring language at the resource level

Establishing the language of a content block

Establishing the language of inline runs

[r12a]

Detailed internationalisation review checklist

Check marks indicate requirements that are fulfilled by this spec. Add comments to describe conformance.

This checklist was created here.

3. Text direction

Basic requirements

1. It must be possible to indicate base direction for each individual paragraph-level item of natural language text that will be read by someone. more
   Comments_go_here
2. It must be possible to indicate base direction changes for embedded runs of inline bidirectional text for all localizable text. more
   Comments_go_here
3. Annotating right-to-left text must require the minimum amount of effort for people who work natively with right-to-left scripts. more
   Comments_go_here

Background information

1. Do not assume that direction can be determined from language information. more
   Comments_go_here

Base direction values

1. Values for the default base direction should include left-to-right, right-to-left, and auto. more
   Comments_go_here

Handling direction in markup

1. The spec should indicate how to define a default base direction for the resource as a whole, ie. set the overall base direction. more
   Comments_go_here
2. The default base direction, in the absence of other information, should be LTR. more
   Comments_go_here
3. The content author must be able to indicate parts of the text where the base direction changes. At the block level, this should be achieved using attributes or metadata, and should not rely on Unicode control characters. more
   Comments_go_here
4. It must be possible to also set the direction for content fragments to auto. This means that the base direction will be determined by examining the content itself. more
   Comments_go_here

Handling base direction for strings

Setting base direction for inline or substring text