You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 manifest spec defines members containing natural language text: the application's name and short name, and the name, short name, and description of the shortcut items.
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 (Not Applicable)
Manifest spec does not allow content authors to produce typographically appealing text.
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 (Not Applicable)
Manifest spec does not allow users to do such operations.
If the spec (or its implementation) allows searching or matching of text, including syntax and identifiers
N/A (Not Applicable)
Manifest spec does not allow searching or matching of text.
If the spec (or its implementation) sorts text
N/A (Not Applicable)
Manifest spec does not involve sorting text.
If the spec (or its implementation) captures user input
N/A (Not Applicable)
Manifest spec does not involve capturing user input.
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 (Not Applicable)
Manifest spec does not deal with date/time values.
If the spec (or its implementation) allows any character encoding other than UTF-8.
N/A (Not Applicable)
Manifest spec only allows UTF-8 character encoding.
If the spec (or its implementation) defines markup.
N/A (Not Applicable)
Manifest spec does not define markup.
If the spec (or its implementation) deals with names, addresses, time & date formats, etc
N/A (Not Applicable)
Manifest spec does not have any fields dealing with names, addresses, time & date formats, or others.
If the spec (or its implementation) describes a format or data that is likely to need localization.
The manifest spec defines members that are likely to need localization: the application's name and short name, and the name, short name, and description of the shortcut items. In case localization is required, authors are expected to provide a localized version of the manifest, either by serving it dynamically (e.g., https://example.com/manifest.webmanifest?lang=de), or using other means such as content negotiation or geotargeting.
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),
The manifest spec defines members containing natural language text: the application's name and short name, and the name, short name, and description of the shortcut items.
TODO: See multiple natural language text fields share language/direction [I18N] #968
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 (Not Applicable)
Manifest spec does not allow content authors to produce typographically appealing text.
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 (Not Applicable)
Manifest spec does not allow users to do such operations.
If the spec (or its implementation) allows searching or matching of text, including syntax and identifiers
N/A (Not Applicable)
Manifest spec does not allow searching or matching of text.
If the spec (or its implementation) sorts text
N/A (Not Applicable)
Manifest spec does not involve sorting text.
If the spec (or its implementation) captures user input
N/A (Not Applicable)
Manifest spec does not involve capturing user input.
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 (Not Applicable)
Manifest spec does not deal with date/time values.
If the spec (or its implementation) allows any character encoding other than UTF-8.
N/A (Not Applicable)
Manifest spec only allows UTF-8 character encoding.
If the spec (or its implementation) defines markup.
N/A (Not Applicable)
Manifest spec does not define markup.
If the spec (or its implementation) deals with names, addresses, time & date formats, etc
N/A (Not Applicable)
Manifest spec does not have any fields dealing with names, addresses, time & date formats, or others.
If the spec (or its implementation) describes a format or data that is likely to need localization.
The manifest spec defines members that are likely to need localization: the application's name and short name, and the name, short name, and description of the shortcut items. In case localization is required, authors are expected to provide a localized version of the manifest, either by serving it dynamically (e.g.,
https://example.com/manifest.webmanifest?lang=de
), or using other means such as content negotiation or geotargeting.TODO: See Add optional
translations
member #676If the spec (or its implementation) makes any reference to or relies on any cultural norms
N/A (Not Applicable)
Manifest spec neither refers to nor relies on any cultural norms.
The text was updated successfully, but these errors were encountered: