Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autoplay Policy Detection API i18n self-review #31

Closed
12 tasks done
chrisn opened this issue Apr 13, 2022 · 4 comments
Closed
12 tasks done

Autoplay Policy Detection API i18n self-review #31

chrisn opened this issue Apr 13, 2022 · 4 comments

Comments

@chrisn
Copy link
Member

chrisn commented Apr 13, 2022

Short i18n review checklist is here

  1. 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 spec does not require any UI text

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

    The spec does not allow content authors to produce text

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

    The spec does not allow such user interaction

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

    The spec does not allow searching or matching of text

  5. If the spec (or its implementation) sorts text

    The spec does not allow sorting of text

  6. If the spec (or its implementation) captures user input

    The spec does not require capturing user input

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

    The spec does not deal with times in this way

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

    The spec does not involve character encodings

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

    The spec does not define markup

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

    The spec does not deal with such data

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

    The spec does not describe a format or data that would need localization

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

    The spec does not rely on cultural norms

@chrisn chrisn mentioned this issue Apr 13, 2022
5 tasks
@alastor0325
Copy link
Collaborator

These answers look correct to me, I will file a request to the Internationalization Working Group. Thank you.

@chrisn
Copy link
Member Author

chrisn commented Sep 1, 2022

Thank you @alastor0325!

@alastor0325
Copy link
Collaborator

@chrisn As i81n review is finished, should we close this issue?

@chrisn
Copy link
Member Author

chrisn commented Sep 16, 2022

Thanks, let's close, the review completed with no issues found.

@chrisn chrisn closed this as completed Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants