Review of track issues for best practices (Part VI)

http://www.w3.org/International/track/issues/173

// review for best practices in encoding sniffing
// is XML's byte sniffing a good thing to reference? Other things?

http://www.w3.org/International/track/issues/177

BP: when providing examples, include a language declaration for natural language text items
BP: include non-ASCII, non-English, and non-American examples

http://www.w3.org/International/track/issues/179

BP: provide a means of declaring the language of a document at the document level

http://www.w3.org/International/track/issues/180

BP: when listing characters that some operation applies to, reference the Unicode code point (using U+#### notation) and the Unicode name, not just the character--even for ASCII characters.

http://www.w3.org/International/track/issues/181

BP: when IRIs are defined for use, provide a non-ASCII (actual IRI) example

http://www.w3.org/International/track/issues/182

BP: avoid examples that are culturally distinct to the United States (or any other specific culture or country) so that the examples may be understood by all

http://www.w3.org/International/track/issues/183

BP: use appropriate data types for time values. For example, do not use xsd:integer for a year. Use xsd:gYear instead.

http://www.w3.org/International/track/issues/184

BP: double check that your escapes use the proper syntax

http://www.w3.org/International/track/issues/185

BP: do not assume that any specific line terminators (LF, CR, CRLF) are used

http://www.w3.org/International/track/issues/186

BP: when defining a text-based document format, refer to the structure of the document as a sequence of Unicode characters (codepoints).


Addison Phillips
Globalization Architect (Amazon Lab126)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.

Received on Friday, 17 April 2015 00:04:59 UTC