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

I18n checklist answers for 9 July WD of IFT #195

Open
12 tasks
svgeesus opened this issue Jul 24, 2024 · 0 comments
Open
12 tasks

I18n checklist answers for 9 July WD of IFT #195

svgeesus opened this issue Jul 24, 2024 · 0 comments
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

Comments

@svgeesus
Copy link
Contributor

svgeesus commented Jul 24, 2024

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

    No. This is just using HTTP to incrementally transfer Web fonts, which happens transparently in the background.

  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.

    No differently to traditional (transferred in their entirety) webfonts. Just faster.

  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.

    No

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

No

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

    No

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

    No

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

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

    Textual content is not transferred by this specification

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

    No

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

    No

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

    No

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

    No

@svgeesus svgeesus added the i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. label Jul 24, 2024
@svgeesus svgeesus added the Priority: Eventually Long-term issue, not outside SLO label Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant