i18n-temporary

The Node.js Internationalization Working Group – A Community Committee initiative.

Showing:

Popularity

Downloads/wk

0

GitHub Stars

117

Maintenance

Last Commit

5d ago

Contributors

45

Package

Dependencies

2

Size (min+gzip)

31.0KB

License

MIT

Type Definitions

Tree-Shakeable

No?

Categories

Readme

The Node.js Internationalization (i18n) Working Group

Crowdin

Here you can find contribution guides, discuss ideas, and find out how to join meetings. This repo also contains the source for the English Node.js API documentation as well as translated versions of the documentation. The source English content 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.

Usage

This repository can be installed as an npm package. See guides/NPM_PACKAGE.md for installation and usage instructions.

About

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 such as 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.

For details on these aspects, see the i18n API guide.

What l10n (Localization) means to us

  • Making the Node.js project's API documentation, site, and tutorial content available in every language.
  • Providing translators with a useful and productive platform to work in.
  • Provisioning Node.js with all l10n assets, through coordination with Node.js core contributors.

Members of this group are not responsible for performing the actual translations, but of coordinating the translation among the language-specific l10n groups.

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.

NOTE: Still confused about the "i18n" versus "l10n" distinction? Read "i18n vs l10n — what’s the diff?" article to find some answers.

Contributing

There are many ways to get involved, and your help is wanted and appreciated.

Translations

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 the translation process
  • Roles - information about roles and hierarchy in Node.js localization process
  • Teams - explains the structure of localization teams and their goals
  • Crowdin - reviews the functionality of Crowdin which is used to translate Node.js

Internationalization

Help make sure Node.js applications continue to support all the world’s languages and cultures. See i18n API to get started.

Current Members

NameGitHubTwitter
Adam Milleramiller-ghmillea9
Aissaoui AhmedAissaoui AhmedAissaoui Ahmed
Alexandr Tovmachalexandrtovmachalexandrtovmach
Alexey TemnykovAlex-Temnytemnykov
Amoramoristamor90s
Andrew BusiAndrewCAAndrewPaulBus
Antoine OlivierToinaneToinane
Benjamin ZaslavskyTirielBen_Tiriel
Ben Michelobensourceobensource
Dhruv Jainmaddhruvmaddhruv
Franz de CopenhagueFranzDeCopenhagueFranzDeCopenhague
Ilyes ChouiaIlyes ChouiaIlyes Chouia
Jonathan CardosoJCMais_jonathancardos
José J. Pérez RivasJoseJPRJoseJ_PR
Laurent GoderreLaurentGoderreLaurentGoderre
Łukasz Szewczaklukaszewczaklukaszewczak
Nick Schonningnschonninschonni
Rachel Whiterachelnicoleohhoe
Raja Sekarrajzshkrrajzshkr
Richard LittauerRichardLittrichlitt
Ryo Aramakiryo-ageo_vitya
Ryuichi Okumuraokuryuokuryu
Sam Yamashitasotayamashitasota0805
Steven R. Loomissrl295srl295
Tiago DaninTiagoDanin_TiagoEDGE
Vanessa Yuenvanessayuennvanessayuenn
Volkan Nazmi MetinVolemvolemnic
Wexpo Lyulaosbit99p
Yuki OkushiJohnTitorfr4ternite
Zeke Sikelianoszekezeke

Joining

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.

Rate & Review

Great Documentation0
Easy to Use0
Performant0
Highly Customizable0
Bleeding Edge0
Responsive Maintainers0
Poor Documentation0
Hard to Use0
Slow0
Buggy0
Abandoned0
Unwelcoming Community0
100