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

Internationalization review #1107

Closed
11 of 12 tasks
Manishearth opened this issue Aug 4, 2020 · 2 comments
Closed
11 of 12 tasks

Internationalization review #1107

Manishearth opened this issue Aug 4, 2020 · 2 comments
Labels
i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
Milestone

Comments

@Manishearth
Copy link
Contributor

Before we hit CR, we need to go through an internationalization review in https://w3c.github.io/i18n-drafts/techniques/shortchecklist

  • ... contains any natural language text that will be read by a human (this includes error messages or other UI text, JSON strings, etc, etc),
    • We do not contain any such text
  • ... allows content authors to produce typographically appealing text, either in its own right, or in association with graphics.
    • Not inherently, people can produce text in WebGL that they may display, however.
  • ... 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.
  • Nope
  • ... allows searching or matching of text, including syntax and identifiers
  • Nope
  • ... sorts text
  • Nope
  • ... captures user input
  • Yes, but the user input is in the form of gestures and controller actions, not language
  • ... deals with time in any way that will be read by humans and/or crosses time zone boundaries
  • Nope
  • ... allows any character encoding other than UTF-8
  • Nope, we don't handle text at all
  • ... defines markup
  • Nope
  • ... deals with names, addresses, time & date formats, etc
  • Nope
  • ... describes a format or data that is likely to need localisation
  • Nope
  • ... makes any reference to or relies on any cultural norms
    • Not that I can think of. There are "norms" on how an XR device is to be used, but those are set by the XR device and we try to be accomodating to different norms on different devices.
@toji
Copy link
Member

toji commented Aug 5, 2020

Seems like an accurate assessment to me. The only thing worth adding is that for "cultural norms" we should consider that to include in this case variations in physical features across different groups, such as height and IPD. (IE: We want to avoid setting defaults that assume, for example, the average North American male IPD.)

There's no area of spec or modules I'm aware of where we set such defaults at this point, though we may inherit some from the users hardware.

@Manishearth Manishearth added this to the Pre-CR milestone Aug 7, 2020
@dontcallmedom dontcallmedom added the i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. label Sep 2, 2020
@Manishearth
Copy link
Contributor Author

The review was resolved in w3c/i18n-request#127

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.
Projects
None yet
Development

No branches or pull requests

3 participants