The Node.js Internationalization Working Group – A Community Committee initiative.
Clone or download
Latest commit 4d299ab Nov 20, 2018

Node.js Internationalization


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


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

  1. Supporting l10n groups who are actively translating the content of Node.js into their own languages.
  2. i18n support for Node.js, and its related initiatives.
  3. Ensuring i18n compliance with all relevant standards such as Unicode and ECMA-402.
  4. 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 and related i18n efforts from other external projects. For example:

Current Members

Name GitHub Twitter
Adam Miller amiller-gh millea9
Andrew Bus iAndrewCA AndrewPaulBus
Antoine Olivier Toinane Toinane
Amor amorist amor90s
Ben Michel obensource obensource
Benjamin Zaslavsky Tiriel Ben_Tiriel
Dhruv Jain maddhruv maddhruv
Franz de Copenhague FranzDeCopenhague FranzDeCopenhague
Jonathan Cardoso JCMais _jonathancardos
Laurent Goderre LaurentGoderre LaurentGoderre
Łukasz Szewczak lukaszewczak lukaszewczak
Rachel White rachelnicole ohhoe
Raja Sekar rajzshkr rajzshkr
Richard Littauer RichardLitt richlitt
Ryo Aramaki ryo-a geo_vitya
Sam Yamashita sotayamashita sota0805
Steven R. Loomis srl295 srl295
Tiago Danin TiagoDanin _TiagoEDGE
Vanessa Yuen vanessayuenn vanessayuenn
Volkan Nazmi Metin Volem volemnic
Wexpo Lyu laosb it99p
Zeke Sikelianos zeke zeke

Current l10n groups we support


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.

Need Translators

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.