I18n checklist answers for 9 July WD of IFT #195
Labels
i18n-tracker
Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
Priority: Eventually
Long-term issue, not outside SLO
Short i18n review checklist is here
If the spec (or its implementation) contains any natural language text that will be read by a human (this includes error messages or other UI text, JSON strings, etc, etc),
No. This is just using HTTP to incrementally transfer Web fonts, which happens transparently in the background.
If the spec (or its implementation) allows content authors to produce typographically appealing text, either in its own right, or in association with graphics.
No differently to traditional (transferred in their entirety) webfonts. Just faster.
If the spec (or its implementation) allows the user to point into text, creates text fragments, concatenates text, allows the user to select or step through text (using a cursor or other methods), etc.
No
If the spec (or its implementation) allows searching or matching of text, including syntax and identifiers
No
If the spec (or its implementation) sorts text
No
If the spec (or its implementation) captures user input
No
If the spec (or its implementation) deals with time in any way that will be read by humans and/or crosses time zone boundaries
No
If the spec (or its implementation) allows any character encoding other than UTF-8.
Textual content is not transferred by this specification
If the spec (or its implementation) defines markup.
No
If the spec (or its implementation) deals with names, addresses, time & date formats, etc
No
If the spec (or its implementation) describes a format or data that is likely to need localization.
No
If the spec (or its implementation) makes any reference to or relies on any cultural norms
No
The text was updated successfully, but these errors were encountered: