Node.js Internationalization
About
The Node.js i18n Working Group is dedicated to the support and improvement of Internationalization (i18n) and Localization (l10n) within the Node.js project. This Working Group serves as a function of the Node.js Community Committee.
What we're responsible for
- The ongoing translation of the Node.js project's textual content into every language of its users.
- The implementation of i18n support including ECMA-402 within Node.js.
- Ensuring Node.js is compliant with common standards like Unicode, CLDR, and other globalization efforts.
What i18n means to us
- Making the Node.js project's API documentation, site, and tutorial content available in every language.
- Maintaining the ability for Node.js to effectively process text written in human languages (e.g., Unicode character processing).
- Providing services which support the cultural & socio-linguistic preferences of all of our international users, such as localized methods for displaying dates & times that are common to specific regions.
- Building and maintaining i18n module(s) that support Node.js.
What l10n means to us
- The ability for Node.js and its related modules & applications to be translated into distinct human languages.
- The responsibility to provide translators with a useful platform to work in.
- The responsibility to provision Node.js with all l10n assets, through coordination with Node.js core contributors.
- Members of this group are not responsible for performing the act of translation itself.
Summary of our Responsibilities
- Supporting l10n groups who are actively translating the content of Node.js into their own languages.
- i18n support for Node.js, and its related initiatives.
- Ensuring i18n compliance with all common character encoding standards such as Unicode, and ECMA.
- Continual refinement and maintenance of the i18n Working Group's processes, platform service accounts, and related module repositories & source code.
Our Current Trajectory
Please read this article to get up to speed on our current trajectory.
Inter-project relationships
In order to ensure best practices, this working group may work directly with representatives of similar i18n efforts from other external projects. For example:
Current Members
If you're interested in joining this group, or would like to leave a question or comment for its members - please create an issue or submit a pull request.
This document was influenced by the nodejs/Intl working group's mandate, and is seen as a continuation of that work.