Internationalization Checklist

[anssiko]

This issue is a record of the Second Screen Working Group's response to the Internationalization Checklist for the Multi-Screen Window Placement API. Completed Checklist is required for the submission of the Internationalization review, one of the wide reviews tracked in #110.

• 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),

The API specification does not contain any natural language, but does contain a per-screen string label, determined by the operating system and user agent, to aid with user identification of screens, similar to other API device strings, like BluetoothDevice.name.

The strings displayed in the permission prompt and other user agent UI surfaces (e.g. fullscreen exit bubbles) are implementation details and are expected to use language-aware strings and platform i18n APIs.

• If the spec (or its implementation) allows content authors to produce typographically appealing text, either in its own right, or in association with graphics.

N/A

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

N/A

• If the spec (or its implementation) allows searching or matching of text, including syntax and identifiers

N/A

• If the spec (or its implementation) sorts text

N/A

• If the spec (or its implementation) captures user input

N/A

• If the spec (or its implementation) deals with time in any way that will be read by humans and/or crosses time zone boundaries

N/A

• If the spec (or its implementation) allows any character encoding other than UTF-8.

N/A

• If the spec (or its implementation) defines markup.

N/A

• If the spec (or its implementation) deals with names, addresses, time & date formats, etc

N/A

• If the spec (or its implementation) describes a format or data that is likely to need localization.

N/A

• If the spec (or its implementation) makes any reference to or relies on any cultural norms

N/A

Summary

Only consideration that applies is "If the spec (or its implementation) contains any natural language". This is an implementation detail.

[anssiko]

@michaelwasserman PTAL. Similarly here, when we're happy, I'll initiate the official i18n review.

[michaelwasserman]

Thank you for drafting this and requesting review! I amended the checklist to include mention of screen labels and other user agent strings besides the permission prompt (e.g. fullscreen exit bubble).