The Node.js Internationalization (i18n) Working Group
Here you can find contribution guides, discuss ideas or join meetings. This repo also contains the source English Node.js API documentation as well as translated versions of the documentation. The source English is copied on a schedule from its canonical home in the doc directory of the nodejs/node repository. The translated files are added by pull requests from our Crowdin integration.
This repository can be installed as an npm package. See guides/NPM_PACKAGE.md for installation and usage instructions.
Help us get Node.js translated into your native language and reach more people's hearts. Please read these guides to get started:
- Getting started - basic understanding about translation process
- Roles - information about roles and hierarchy in Node.js localization process
- Teams - explain the structure of localization teams and their goals
- Crowdin - review functionality of Crowdin that we're using for Node.js
The Node.js i18n Working Group is dedicated to the support and improvement of both 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 harmonized with other globalization efforts.
What i18n (Internationalization) means to us
Maintaining the ability for Node.js to effectively support the cultural & socio-linguistic preferences of all international users, through:
- Unicode processing and related services to support text written in all human languages.
- APIs and implementations which support the specific cultural & socio-linguistic preferences, such as localized methods for displaying dates & times.
- The ability for Node.js and its related modules & applications to be translated into distinct human languages.
What l10n (Localization) means to us
- Making the Node.js project's API documentation, site, and tutorial content available in every language.
- 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 relevant standards such as Unicode and ECMA-402.
- Continual refinement and maintenance of the i18n Working Group's processes, platform service accounts, and related module repositories & source code.
NOTE: Still confused with "i18n" and "l10n" terms? Read "i18n vs l10n — what’s the diff?" article to find answers.
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. Keep in mind, you don't have to be a member of this group to start translating. You can read more about contributing translations in the Getting started guide.