Name: Intl
Owner: Node.js Foundation
Description: Node.js Intl Team (see new i18n WG)
Created: 2015-05-23 05:10:51.0
Updated: 2018-04-03 15:17:20.0
Pushed: 2018-02-19 16:52:43.0
Homepage: https://github.com/nodejs/TSC/issues/353
Size: 24
Language: null
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
Intl
Working Group(content kept for archival purposes)
The Intl Working Group is dedicated to support and improvement of Internationalization (i18n) and Localization (l10n) in Node.js.
This WG's responsibility would be the implementation of internationalization support (including but not limited to Ecma-402) within Node.js itself, as well as ensuring compliance with standards such as Unicode, CLDR, and other globalization efforts.
Internationalization here refers to the ability for Node.js to properly process textual content written in human languages (for example, Unicode character processing) as well as to provide services which respect the user?s cultural and socio-linguistic preferences (such as the particular way that dates and times would be displayed).
Localization here refers to the ability for Node.js and its modules and applications to be actually translated into specific human languages. It is the responsibility of this WG to provide the infrastructure necessary to allow such translations to take place, such as message bundles and message formatting.
Note, however it is not in the scope of this WG to perform the actual translation (or localization) of Node.js, its documentation and websites, nor of modules or applications built using Node.js.
Specifically, this mission is distinct from that of the various i18n working groups that are involved with translation of various project assets such as documentation and the website to benefit the global community.
In summary, this WGs responsibilities are:
Intl
implementationThe WG will pursue formal or informal relationships with other WGs or other bodies as appropriate, which may include but is not limited to:
The Intl Working Group is not responsible for, but may benefit from interaction/liaison with those interested in, the following:
If you would like to join this group, please comment on this issue or submit a pull request.