Help us get the documentation translated into your native language and reach more people's hearts. Visit Crowdin/project/NodeJs and help translating docs
Languages being Translated
- Chinese Simplified
- Chinese Traditional
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.
Small note: If you do not speak English, go to the Need Translators? section.
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.
Our Current Trajectory
Please read this article to get up to speed on our current trajectory.
In order to ensure best practices, this working group may work directly with representatives of similar and related i18n efforts from other external projects. For example:
- Electron i18n
- W3C i18n Working Group
- V8 i18n (implements ECMA-402 in Node.js)
|Franz de Copenhague||FranzDeCopenhague||FranzDeCopenhague|
|Steven R. Loomis||srl295||srl295|
|Volkan Nazmi Metin||Volem||volemnic|
Current l10n groups we support
- Arabic (nodejs-ar)
- Bengali (nodejs-bn)
- Bulgarian (nodejs-bg)
- Chinese (nodejs-zh-CN)
- Czech (nodejs-cs)
- Danish (nodejs-da)
- Dutch (nodejs-nl)
- Finnish (nodejs-fi)
- French (nodejs-fr)
- Georgian (nodejs-ka)
- German (nodejs-de)
- Greek (nodejs-el)
- Hebrew (nodejs-he)
- Hindi (nodejs-hi)
- Hungarian (nodejs-hu)
- Indonesian (nodejs-id)
- Italian (nodejs-it)
- Japanese (nodejs-ja)
- Macedonian (nodejs-mk)
- Malay (nodejs-ms)
- Norwegian (nodejs-no)
- Persian (nodejs-fa)
- Polish (nodejs-pl)
- Portuguese (nodejs-pt)
- Russian (nodejs-ru)
- Spanish (nodejs-es)
- Swahili (nodejs-sw)
- Swedish (nodejs-sv)
- Taiwan (nodejs-zh-TW)
- Tamil (nodejs-ta)
- Turkish (nodejs-tr)
- Ukrainian (nodejs-uk)
- Vietnamese (nodejs-vi)
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.
If you cannot speak or read English easily, we can provide translators for this group's documents and during our video meetings. Please get in touch with Ben Michel or Zeke Sikelianos and ask for help for your language.
This document was influenced by the nodejs/Intl working group's mandate, and is seen as a continuation of that work.