2.1 Declaring language

Language information for a given resource can be used with two main objectives in mind: for text-processing, or as a statement of the intended use of the resource. We will explain the difference here.

2.2 Defining language values

​Values for language declarations must use BCP 47. more

BCP 47 defines a method to combine subtags in order to create a much more powerful notation for language tags than that provided by the old ISO lists, but it is also backwards compatible with the ISO lists.

For an overview of the key features of BCP 47, see Language tags in HTML and XML.

​Refer to BCP 47, not to RFC 5646. more

The link to and name of BCP 47 was created specifically so that there is an unchanging reference to the definition of Tags for the Identification of Languages. RFCs 3066, 4646 and 5646 are versions of BCP 47.

​Be specific about what level of conformance you expect for language tags. The word "valid" has special meaning in BCP 47. Generally "well-formed" is a better choice.

​Reference BCP47 for language tag matching.

2.3 Setting the default base direction

In order to correctly display text written in a 'right-to-left' script, it is important to know the base direction that should be applied to that text. For more information see Unicode Bidirectional Algorithm basics.

​The spec should indicate how to define a default base direction for the resource as a whole, ie. set the overall base direction. more

​The default base direction, in the absence of other information, should be LTR. more

2.4 Defining resource identifiers

​Resource identifiers must permit the use of characters outside those of plain ASCII. discussion

​ Specifications MUST define when the conversion from IRI references to URI references (or subsets thereof) takes place, in accordance with Internationalized Resource Identifiers (IRIs). more

Many current specifications already contain provisions in accordance with Internationalized Resource Identifiers (IRIs). For XML 1.0, see Section 4.2.2, External Entities. XML Schema Part 2: Datatypes provides the anyURI datatype (see Section 3.2.17). The XML Linking Language (XLink) provides the href attribute (see Section 5.4, Locator Attribute).

Document formats should allow IRIs to be used; handlers for protocols that do not currently support IRIs can convert the IRI to a URI when the IRI is dereferenced.

3.1 Establishing the language

​By default, blocks of content should inherit the text-processing language set for the resource as a whole. more

See 2.1 Declaring language for guidance related to the default text-processing language information.

​It should be possible to indicate a change in language for blocks of content where the language changes. more

3.2 Establishing the base direction

​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.

Relying on Unicode control characters to establish direction for every block is not feasible because line breaks terminate the effect of such control characters. It also makes the data much less stable, and unnecessarily difficult to manage if control characters have to appear at every point where they would be needed.

​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.

A typical approach here would be to set the direction based on the first strong directional character outside of any markup, but this is not the only possible method. The algorithm used to determine directionality when direction is set to auto should match that expected by the receiver.

The first-strong algorithm looks for the first character in the paragraph with a strong directional property according to the Unicode definitions. It then sets the base direction of the paragraph according to the direction of that character.

Note that the first-strong algorithm may incorrectly guess the direction of the paragraph when the first character is not typical of the rest of the paragraph, such as when a RTL paragraph or line starts with a LTR brand name or technical term.

For additional information about algorithms for detecting direction, see Estimation algorithms in the document where this was discussed with reference to HTML.

​If the overall base direction is set to auto for plain text, the direction of content paragraphs should be determined on a paragraph by paragraph basis.

​To indicate the sides of a block of text where relative to the start and end of its contained lines, you should use 'before' and 'after' (maybe block-start/block-end – the terminology is changing), rather than 'top' and 'bottom'.

​To indicate the start/end of a line you should use 'start' and 'end' rather than 'left' and 'right'.

​Provide dedicated attributes for control of base direction and bidirectional overrides; do not rely on the user applying style properties to arbitrary markup to achieve bidi control.

For example, HTML has a dir attribute that is capable of managing base direction without assistance from CSS styling. XML formats should define dedicated markup to represent directional information, even if they need CSS to achieve the required display, since the text may be used in other ways.

Style sheets such as CSS may not always be used with the data, or carried with the data when it is syndicated, etc. Directional information is fundamentally important to correct display of the data, and should be associated more closely and more permanently with the markup or data.

4.1 Establishing the language

​It should be possible to indicate language for spans of inline text where the language changes. more

Where a switch in language can affect operations on the content, such as spell-checking, rendering, styling, voice production, translation, information retrieval, and so forth, it is necessary to indicate the range of text affected and identify the language of that content.

4.2 Setting base direction

​It must be possible to indicate spans of inline text where the base direction changes. If markup is available, this is the preferred method. Otherwise your specification must require that Unicode control characters are recognized by the receiving application, and correctly implemented.

​It must be possible to also set the direction for a span to auto. This means that the base direction will be determined by examining the content itself. A typical approach here would be to set the direction based on the first strong directional character outside of any markup. more

The first-strong algorithm looks for the first character in the paragraph with a strong directional property according to the Unicode definitions. It then sets the base direction of the paragraph according to the direction of that character.

Note that the first-strong algorithm may incorrectly guess the direction of the paragraph when the first character is not typical of the rest of the paragraph, such as when a RTL paragraph or line starts with a LTR brand name or technical term.

For additional information about algorithms for detecting direction, see Estimation algorithms in the document where this was discussed with reference to HTML.

​If users use Unicode bidirectional control characters, the RLI/LRI/FSI with PDI characters must be supported by the application and recommended (rather than RLE/LRE with PDF) by the spec.

​Use of RLM/LRM should be appropriate, and expectations of what those controls can and cannot do should be clear in the spec. more

The Unicode bidirectional control characters U+200F RIGHT-TO-LEFT MARK and U+200E LEFT-TO-RIGHT MARK are not sufficient on their own to manage bidirectional text. They cannot produce a different base direction for embedded text. For that you need to be able to indicate the start and end of the range of the embedded text.  This is best done by markup, if available, or failing that using the other Unicode bidirectional controls mentioned just above.

​Provide dedicated attributes for control of base direction and bidirectional overrides; do not rely on the user applying style properties to arbitrary markup to achieve bidi control.

​Allow bidi attributes on all inline elements in markup that contain text.

​Provide attributes that allow the user to (a) create an embedded base direction or (b) override the bidirectional algorithm altogether; the attribute should allow the user to set the direction to LTR or RTL in either of these two scenarios.

5.1 Choosing a definition of 'character'

​Specifications, software and content MUST NOT require or depend on a one-to-one correspondence between characters and the sounds of a language. more

​Specifications, software and content MUST NOT require or depend on a one-to-one mapping between characters and units of displayed text. more

​Protocols, data formats and APIs MUST store, interchange or process text data in logical order. more

​Independent of whether some implementation uses logical selection or visual selection, characters selected MUST be kept in logical order in storage. more

​Specifications of protocols and APIs that involve selection of ranges SHOULD provide for discontiguous logical selections, at least to the extent necessary to support implementation of visual selection on screen on top of those protocols and APIs. more

​Specifications and software MUST NOT require nor depend on a single keystroke resulting in a single character, nor that a single character be input with a single keystroke (even with modifiers), nor that keyboards are the same all over the world. more

​Specifications, software and content MUST NOT require or depend on a one-to-one relationship between characters and units of physical storage. more

​When specifications use the term 'character' the specifications MUST define which meaning they intend. more

​Specifications SHOULD use specific terms, when available, instead of the general term 'character'. more

5.2 Defining a Reference Processing Model

​Textual data objects defined by protocol or format specifications MUST be in a single character encoding. more

​All specifications that involve processing of text MUST specify the processing of text according to the Reference Processing Model described by the rest of the recommendations in this list. more

​Specifications MUST define text in terms of Unicode characters, not bytes or glyphs. more

​For their textual data objects specifications MAY allow use of any character encoding which can be transcoded to a Unicode encoding form. more

​Specifications MAY choose to disallow or deprecate some character encodings and to make others mandatory. Independent of the actual character encoding, the specified behavior MUST be the same as if the processing happened as follows: (a) The character encoding of any textual data object received by the application implementing the specification MUST be determined and the data object MUST be interpreted as a sequence of Unicode characters - this MUST be equivalent to transcoding the data object to some Unicode encoding form, adjusting any character encoding label if necessary, and receiving it in that Unicode encoding form, (b) All processing MUST take place on this sequence of Unicode characters, (c) If text is output by the application, the sequence of Unicode characters MUST be encoded using a character encoding chosen among those allowed by the specification. more

​If a specification is such that multiple textual data objects are involved (such as an XML document referring to external parsed entities), it MAY choose to allow these data objects to be in different character encodings. In all cases, the Reference Processing Model MUST be applied to all textual data objects. more

5.3 Including and excluding character ranges

​Specifications SHOULD NOT arbitrarily exclude code points from the full range of Unicode code points from U+0000 to U+10FFFF inclusive. more

​Specifications MUST NOT allow code points above U+10FFFF. more

​Specifications SHOULD NOT allow the use of codepoints reserved by Unicode for internal use. more

​Specifications MUST NOT allow the use of surrogate code points. more

​Specifications SHOULD exclude compatibility characters in the syntactic elements (markup, delimiters, identifiers) of the formats they define. more

5.4 Using the Private Use Area

​Specifications MUST NOT require the use of private use area characters with particular assignments. more

​Specifications MUST NOT require the use of mechanisms for defining agreements of private use code points. more

​Specifications and implementations SHOULD NOT disallow the use of private use code points by private agreement. more

​Specifications MAY define markup to allow the transmission of symbols not in Unicode or to identify specific variants of Unicode characters. more

​Specifications SHOULD allow the inclusion of or reference to pictures and graphics where appropriate, to eliminate the need to (mis)use character-oriented mechanisms for pictures or graphics. more

5.5 Choosing character encodings

​Specifications MUST either specify a unique character encoding, or provide character encoding identification mechanisms such that the encoding of text can be reliably identified. more

​When designing a new protocol, format or API, specifications SHOULD require a unique character encoding. more

​When basing a protocol, format, or API on a protocol, format, or API that already has rules for character encoding, specifications SHOULD use rather than change these rules. more

​When a unique character encoding is required, the character encoding MUST be UTF-8, UTF-16 or UTF-32. more

This guideline needs further consideration: utf-16 and utf-32 are not recommended these days. UTF-8 is the recommended encoding.

​Specifications SHOULD avoid using the terms 'character set' and 'charset' to refer to a character encoding, except when the latter is used to refer to the MIME charset parameter or its IANA-registered values. The term 'character encoding', or in specific cases the terms 'character encoding form' or 'character encoding scheme', are RECOMMENDED. more

​If the unique encoding approach is not taken, specifications SHOULD require the use of the IANA charset registry names, and in particular the names identified in the registry as 'MIME preferred names', to designate character encodings in protocols, data formats and APIs. more

This guideline needs further consideration: the list of character encodings recommended for Web specifications is listed in the Encoding specification.

​Character encodings that are not in the IANA registry SHOULD NOT be used, except by private agreement. more

​If an unregistered character encoding is used, the convention of using 'x-' at the beginning of the name MUST be followed. more

​If the unique encoding approach is not chosen, specifications MUST designate at least one of the UTF-8 and UTF-16 encoding forms of Unicode as admissible character encodings and SHOULD choose at least one of UTF-8 or UTF-16 as required encoding forms (encoding forms that MUST be supported by implementations of the specification). more

​Specifications that require a default encoding MUST define either UTF-8 or UTF-16 as the default, or both if they define suitable means of distinguishing them. more

5.6 Identifying character encodings

​Specifications MUST NOT propose the use of heuristics to determine the encoding of data. more

​Specifications MUST define conflict-resolution mechanisms (e.g. priorities) for cases where there is multiple or conflicting information about character encoding. more

5.7 Designing character escapes

​Specifications should provide a mechanism for escaping characters, particularly those which are invisible or ambiguous. more

It is generally recommended that character escapes be provided so that difficult to enter or edit sequences can be introduced using a plain text editor. Escape sequences are particularly useful for invisible or ambiguous Unicode characters, including zero-width spaces, soft-hyphens, various bidi controls, mongolian vowel separators, etc.

For advice on use of escapes in markup, but which is mostly generalisable to other formats, see Using character escapes in markup and CSS.

​Specifications SHOULD NOT invent a new escaping mechanism if an appropriate one already exists. more

​The number of different ways to escape a character SHOULD be minimized (ideally to one). more

​Escape syntax SHOULD require either explicit end delimiters or a fixed number of characters in each character escape. Escape syntaxes where the end is determined by any character outside the set of characters admissible in the character escape itself SHOULD be avoided. more

​Whenever specifications define character escapes that allow the representation of characters using a number, the number MUST represent the Unicode code point of the character and SHOULD be in hexadecimal notation. more

​Escaped characters SHOULD be acceptable wherever their unescaped forms are; this does not preclude that syntax-significant characters, when escaped, lose their significance in the syntax. In particular, if a character is acceptable in identifiers and comments, then its escaped form should also be acceptable. more

5.8 Storing text

​Protocols, data formats and APIs MUST store, interchange or process text data in logical order. more

​Specifications of protocols and APIs that involve selection of ranges SHOULD provide for discontiguous logical selections, at least to the extent necessary to support implementation of visual selection on screen on top of those protocols and APIs. more

5.9 Specifying sort and search functionality

​Software that sorts or searches text for users SHOULD do so on the basis of appropriate collation units and ordering rules for the relevant language and/or application. more

​Where searching or sorting is done dynamically, particularly in a multilingual environment, the 'relevant language' SHOULD be determined to be that of the current user, and may thus differ from user to user. more

​Software that allows users to sort or search text SHOULD allow the user to select alternative rules for collation units and ordering. more

​Specifications and implementations of sorting and searching algorithms SHOULD accommodate text that contains any character in Unicode. more

5.10 Converting to a Common Unicode Form

​Specifications of text-based formats and protocols MAY specify that all or part of the textual content of that format or protocol is normalized using Unicode Normalization Form C (NFC). more

​Specifications that do not normalize MUST document or provide a health-warning if canonically equivalent but disjoint Unicode character sequences represent a security issue. more

​Specifications and implementations MUST NOT assume that content is in any particular normalization form. more

​Specifications MUST specify that string matching takes the form of "code point-by-code point" comparison of the Unicode character sequence, or, if a specific Unicode character encoding is specified, code unit-by-code unit comparison of the sequences. more

​Specifications that define a regular expression syntax MUST provide at least Basic Unicode Level 1 support per Unicode Technical Standard #18: Unicode Regular Expressions and SHOULD provide Extended or Tailored (Levels 2 and 3) support. more

​Specifications of text-based formats and protocols that, as part of their syntax definition, require that the text be in normalized form MUST define string matching in terms of normalized string comparison and MUST define the normalized form to be NFC. more

​A normalizing text-processing component which receives suspect text MUST NOT perform any normalization-sensitive operations unless it has first either confirmed through inspection that the text is in normalized form or it has re-normalized the text itself. Private agreements MAY, however, be created within private systems which are not subject to these rules, but any externally observable results MUST be the same as if the rules had been obeyed. more

​Specifications of text-based languages and protocols SHOULD define precisely the construct boundaries necessary to obtain a complete definition of full-normalization. These definitions SHOULD include at least the boundaries between markup and character data as well as entity boundaries (if the language has any include mechanism) , SHOULD include any other boundary that may create denormalization when instances of the language are processed, but SHOULD NOT include character escapes designed to express arbitrary characters. more

​Where operations can produce denormalized output from normalized text input, specifications of API components (functions/methods) that implement these operations MUST define whether normalization is the responsibility of the caller or the callee. Specifications MAY state that performing normalization is optional for some API components; in this case the default SHOULD be that normalization is performed, and an explicit option SHOULD be used to switch normalization off. Specifications SHOULD NOT make the implementation of normalization optional. more

​Specifications that define a mechanism (for example an API or a defining language) for producing textual data object SHOULD require that the final output of this mechanism be normalized. more

5.11 Handling Case Folding

​Case sensitive matching is RECOMMENDED as the default for new protocols and formats. more

​Because the "simple" case-fold mapping removes information that can be important to forming an identity match, the "Common plus Full" (or "Unicode C+F") case fold mapping is RECOMMENDED for Unicode case-insensitive matching. more

​ASCII case-insensitive matching MUST only be applied to vocabularies that are restricted to ASCII. Unicode case-insensitivity MUST be used for all other vocabularies. more

​If the vocabulary is not restricted to ASCII or permits user-defined values that use a broader range of Unicode, ASCII case-insensitive matching MUST NOT be required. more

​The Unicode C+F case-fold form is RECOMMENDED as the case-insensitive matching for vocabularies. The Unicode C+S form MUST NOT be used for string identity matching on the Web. more

​Specifications and implementations that define string matching as part of the definition of a format, protocol, or formal language (which might include operations such as parsing, matching, tokenizing, etc.) MUST define the criteria and matching forms used. These MUST be one of: (a) Case-sensitive (b) Unicode case-insensitive using Unicode case-folding C+F (c) ASCII case-insensitive. more

​Specifications SHOULD NOT specify case-insensitive comparison of strings. more

​Specifications that specify case-insensitive comparison for non-ASCII vocabularies SHOULD specify Unicode case-folding C+F. more

​Specifications MAY specify ASCII case-insensitive comparison for portions of a format or protocol that are restricted to an ASCII-only vocabulary. more

​Specifications and implementations MUST NOT specify ASCII-only case-insensitive matching for values or constructs that permit non-ASCII characters. more

5.12 Defining 'string'

​Specifications SHOULD NOT define a string as a 'byte string'. more

​The 'character string' definition SHOULD be used by most specifications. more

5.13 Indexing strings

​The character string is RECOMMENDED as a basis for string indexing. more

​A code unit string MAY be used as a basis for string indexing if this results in a significant improvement in the efficiency of internal operations when compared to the use of character string. more

​Grapheme clusters MAY be used as a basis for string indexing in applications where user interaction is the primary concern. more

​Specifications that define indexing in terms of grapheme clusters MUST either: (a) define grapheme clusters in terms of default grapheme clusters as defined in Unicode Standard Annex #29, Text Boundaries [UTR #29], or (b) define specifically how tailoring is applied to the indexing operation. more

Need to check the above recommendation, since extended grapheme clusters are now recommended.

​The use of byte strings for indexing is NOT RECOMMENDED. more

​Specifications that need a way to identify substrings or point within a string SHOULD provide ways other than string indexing to perform this operation. more

​Specifications SHOULD understand and process single characters as substrings, and treat indices as boundary positions between counting units, regardless of the choice of counting units. more

​Specifications of APIs SHOULD NOT specify single characters or single 'units of encoding' as argument or return types. more

​When the positions between the units are counted for string indexing, starting with an index of 0 for the position at the start of the string is the RECOMMENDED solution, with the last index then being equal to the number of counting units in the string. more

5.14 Referring to Unicode characters

​Use U+XXXX syntax to represent Unicode code points in the specification. more

The U+XXXX format is well understood when referring to Unicode code points in a specification. These are space separated when appearing in a sequence. No additional decoration is needed. Note that a code point may contain four, five, or six hexadecimal digits. When fewer than four digits are needed, the code point number is zero filled. E.g. U+0020.

5.15 Referencing the Unicode Standard

​Since specifications in general need both a definition for their characters and the semantics associated with these characters, specifications SHOULD include a reference to the Unicode Standard, whether or not they include a reference to ISO/IEC 10646. more

​A generic reference to the Unicode Standard MUST be made if it is desired that characters allocated after a specification is published are usable with that specification. A specific reference to the Unicode Standard MAY be included to ensure that functionality depending on a particular version is available and will not change over time. more

​All generic references to the Unicode Standard MUST refer to the latest version of the Unicode Standard available at the date of publication of the containing specification. more

​All generic references to ISO/IEC 10646 MUST refer to the latest version of ISO/IEC 10646 available at the date of publication of the containing specification. more

6.1 Enabling vertical text display

​It should be possible to render text vertically for languages such as Japanese, Chinese, Korean, Mongolian, etc.

​Vertical text must support line progression from LTR (eg. Mongolian) and RTL (eg. Japanese)

6.2 Setting box positioning coordinates when text direction varies

​Box positioning coordinates must take into account whether the text is horizontal or vertical. more

It is typical, when localizing a user interface or web page, to create mirror-images for the RTL and LTR versions. For example, it is likely that a box that appears near the left side of a window containing English content would appear near the right side of the window if the content is Arabic or Hebrew. It should preferably automatic for this to change, based on the base direction of the current context, unless there is a strong reason for using absolute geometry. One way to achieve this is to use keywords such as start and end, rather than left and right, to indicate position.

6.3 Miscellaneous

​Line heights must allow for characters that are taller than English.

​Box sizes must allow for text expansion in translation.

​Ruby text alongside base text should be supported for CJK text.

​Line wrapping should take into account the special rules needed for non-Latin scripts. more

Various non-Latin writing systems don't simply wrap text on inter-word spaces. They have additional rules that must be respected. For example

• Chinese, Japanese and Korean wrap after characters, but don't put certain characters at the start/end of a line.
• Thai and other SE Asian scripts wrap at word boundaries, but words are not delimited by spaces – spaces are instead used to separate phrases.
• Tibetan wraps after the tsek character that follows a syllable – words are not separated by spaces, and lines can break within a word.
• Indic and other complex scripts break at orthographic syllable boundaries, which are often two or more grapheme clusters.

See the CSS Text Level 3 specification for additional background. (This tutorial provides additional examples, if needed.)

​Avoid specifying presentational tags, such as b for bold, and i for italic. more

It is best to avoid presentational markup b, i or u, since it isn't interoperable across writing systems and furthermore may cause unnecessary problems for localisation. In addition, some scripts have native approaches to things such as emphasis, that do not involve, and can be very different from, bolding, italicisation, etc.

In the HTML case, there was a legacy issue, but unless there is one for your specification, the recommendation is that styling be used instead to determine the presentation of the text, and that any markup or tagging should allow for general semantic approaches.

For an explanation of the issues surrounding b and i tags, see Using <b> and <i> elements.

7.1 Working with time

​When defining calendar and date systems, be sure to allow for dates prior to the common era, or at least define handling of dates outside the most common range.

​When defining time or date data types, ensure that the time zone or relationship to UTC is always defined.

​Provide a health warning for conversion of time or date data types that are "floating" to/from incremental types, referring as necessary to the Time Zones WG Note. more

​Allow for leap seconds in date and time data types. more

These occur occasionally when the number of seconds in a minute is allowed to range from 0 to 60 (ie. there are sixty-ONE seconds in that minute).

​Use consistent terminology when discussing date and time values. Use 'floating' time for time zone independent values.

​Keep separate the definition of time zone from time zone offset.

​Use IANA time zone IDs to identify time zones. Do not use offsets or LTO as a proxy for time zone.

​Use a separate field to identify time zone.

​When defining rules for a "week", allow for culturally specific rules to be applied. more

For example, the weekend is not always Saturday/Sunday; the first day of week is not always Sunday [or Monday or...], etc.

​When defining rules for week number of year, allow for culturally specific rules to be applied.

​When non-Gregorian calendars are permitted, note that the "month" field can go to 13 (undecimber).

7.2 Designing forms

​When defining email field validation, allow for EAI (smtputf8) names.

7.3 Working with numbers

​When parsing user input of numeric values, allow for digit shaping (non-ASCII digits).

​When formatting numeric values for display, allow for culturally sensitive display, including the use of non-ASCII digits (digit shaping).

8.1 Defining elements and attributes

​Do not define attribute values that will contain user readable content. Use elements for such content. more

​If you do define attribute values containing user readable content, provide a means to indicate directional and language information for that text separately from the text contained in the element.

​Provide a way for authors to annotate arbitrary inline content using a span-like element or construct. more

9.1 Providing for content negotiation based on language

​In a multilingual environment it must be possible for the user to receive text in the language they prefer. This may depend on implicit user preferences based on the user's system or browser setup, or on user settings explicitly negotiated with the user.

10.1 Miscellaneous

​Avoid natural language text in elements that only allow for plain text and in attribute values.

​Provide a span-like element that can be used for any text content to apply information needed for internationalization. more

Internationalization information may include a change of language, bidirectional text behaviour changes, translate flags, etc.

11.1 Miscellaneous

​Identifiers should be case-sensitive.