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
Locale Extensions #844
Comments
I've made substantial revisions to this proposal, which are reflected in the new explainer. I'd love to hear your feedback! @dminor @hsivonen |
Hi Ben, we're discussing this internally and we hope to get you feedback soon. |
Here's the slideset from a talk at TG2 on the proposal as stands. |
Sorry about the delay. Here's my review: Proposed position: negative. The use cases have legitimacy, but it's not clear that the importance of the use cases overrides other concerns: primarily fingerprintability and, secondarily, reconciling in implementation the relative role of browser and operating system given that the browser language may not be coupled with the OS language and that operating systems do not consistently provide UI surface for these settings. Third, if we were to expose this information, we should consider if a HTML+CSS-based declarative solution makes more sense, particularly for numbering systems, hour cycle, dates rendered according to a calendar, and amounts with units. Additional Notes:
|
Request for Mozilla Position on an Emerging Web Specification
Other information
On the Web platform, content is localized dependent only upon a user's language or region. However, this behavior can result in annoyance, frustration, offense, or even uninteligibility for some users.
Some example situations:
In the native environment these problems do not occur, since users can specify these desired customizations in their system settings. However, the full amount of flexibility allowed for in the native environment is not possible in the potentially hostile web environment. This proposal defines a mechanism for making a limited subset of the Unicode Extensions for BCP 47 available for content negotiation, providing options that address some of the worst problems with incomplete localization while only exposing coarse-grained data about the users who take advantage of these improvements.
Read the complete Explainer
Slide deck about Locale Extensions
Feedback
I welcome feedback in this thread, but encourage you to file bugs against the Explainer.
The text was updated successfully, but these errors were encountered: