Internationalization Checklist

[anssiko]

This issue is a record of the Web Machine Learning Working Group's response to the Internationalization Checklist. Completed Checklist is required for the submission of the Internationalization review, one of the wide review steps.

• [x] 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),

WebNN API contains DOMStrings that are developer-defined and meant purely to improve web developer ergonomics, and not surfaced to users:

https://www.w3.org/TR/webnn/#typedefdef-mlnamedoperands https://www.w3.org/TR/webnn/#dom-mlgraphbuilder-input https://www.w3.org/TR/webnn/#typedefdef-mlnamedinputs https://www.w3.org/TR/webnn/#typedefdef-mlnamedoutputs

For example, a web developer can create an operand for a graph input and assign it a name 'A':

const inputs = { 'A': bufferA, 'B': bufferB };

And later refer to this input using the name 'A':

console.log(inputs.A);

• [ ] 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 text that will be read by a human (this includes error messages or other UI text, JSON strings, etc, etc),".

[anssiko]

(Reviewed at WebML WG Teleconference – 5 May 2022)

[anssiko]

(i18n review request was submitted 10 May 2022 https://github.com/w3c/i18n-request/issues/179 and this checklist was provided as input.)

[anssiko]

Review feedback received, closing this checklist issue.

[anssiko]

Similarly to a11y, I've re-reviewed also this i18n checklist for the purpose of our upcoming CR Snapshot delta wide review and suggest no changes to our initial response that still stands.

[aphillips]

When you perform a self-review, it is a good idea to have it reviewed by I18N. Using our i18n-tracker label will get our attention without introducing anything blocking.