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

Discuss issues with localization of metadata vs localization of web app #23

Open
marcoscaceres opened this issue Nov 28, 2013 · 1 comment

Comments

@marcoscaceres
Copy link
Contributor

Need to describe the problem at the moment that even if you get the localized name, the application won't be localized. The navigator.language is the navigator language, so the application has no way of knowing (currently) that the system language has changed. This would require a change to how the web platform interfaces with the OS to get the user's language. This has privacy issues, as it helps narrow down a user's geographic location down to a country. The HTML5 spec currently tries to protect users from this by telling the UA to always report "en-US".

@ernesto-jimenez
Copy link
Member

Sounds good.

We should probably expand what's currently the relationship between navigator.language and the device's language in mobile.

In Desktop we are more used to browsers having different language settings to the OS, but I'm not sure that's the case in mobile. e.g: I haven't found any language settings in Chrome nor Safari for iPhone.

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