node-gettext


node-gettext is a JavaScript implementation of (a large subset of) gettext, a localization framework originally written in C.

If you just want to parse or compile mo/po files, for use with this library or elsewhere, check out gettext-parser.

NOTE: This is the README for v2 of node-gettext, which introduces several braking changes. You can find the README for v1 here.

* Features
* Differences from GNU gettext
* Installation
* Usage
* Error events
* Recipes
* API
* Migrating from v1 to v2
* License
* See also

Features

* Supports domains, contexts and plurals
* Supports .json, .mo and .po files with the help of gettext-parser
* Ships with plural forms for 136 languages
* Change locale or domain on the fly
* Useful error messages enabled by a debug option
* Emits events for internal errors, such as missing translations

$3

There are two main differences between node-gettext and GNU's gettext:

1. There are no categories. GNU gettext features categories such as LC_MESSAGES, LC_NUMERIC and LC_MONETARY, but since there already is a plethora of great JavaScript libraries to deal with numbers, currencies, dates etc, node-gettext is simply targeted towards strings/phrases. You could say it just assumes the LC_MESSAGES category at all times.
2. You have to read translation files from the file system yourself. GNU gettext is a C library that reads files from the file system. This is done using bindtextdomain(domain, localesDirPath) and setlocale(category, locale), where these four parameters combined are used to read the appropriate translations file.

However, since node-gettext needs to work both on the server in web browsers (which usually is referred to as it being universal or isomorphic JavaScript), it is up to the developer to read translation files from disk or somehow provide it with translations as pure JavaScript objects using addTranslations(locale, domain, translations).

bindtextdomain will be provided as an optional feature in a future release.

Installation

``sh
npm install --save node-gettext
`

Usage

`js
import Gettext from 'node-gettext'
import swedishTranslations from './translations/sv-SE.json'

const gt = new Gettext()
gt.addTranslations('sv-SE', 'messages', swedishTranslations)
gt.setLocale('sv-SE')

gt.gettext('The world is a funny place')
// -> "Världen är en underlig plats"
`

$3

`js
// Add translations etc...

gt.on('error', error => console.log('oh nose', error))
gt.gettext('An unrecognized message')
// -> 'oh nose', 'An unrecognized message'
`

$3

#### Load and add translations from .mo or .po files

node-gettext expects all translations to be in the format specified by gettext-parser. Therefor, you should use that to parse .mo or .po files.

Here is an example where we read a bunch of translation files from disk and add them to our Gettext instance:

`js
import fs from 'fs'
import path from 'path'
import Gettext from 'node-gettext'
import { po } from 'gettext-parser'

// In this example, our translations are found at
// path/to/locales/LOCALE/DOMAIN.po
const translationsDir = 'path/to/locales'
const locales = ['en', 'fi-FI', 'sv-SE']
const domain = 'messages'

const gt = new Gettext()

locales.forEach((locale) => {
const fileName = ${domain}.po
const translationsFilePath = path.join(translationsDir, locale, filename)
const translationsContent = fs.readSync(translationsFilePath)

const parsedTranslations = po.parse(translationsContent)
gt.addTranslations(locale, domain, parsedTranslations)
})
`

API

Gettext

* Gettext
* [new Gettext([options])](#new_Gettext_new)
* .on(eventName, callback)
* .off(eventName, callback)
* .addTranslations(locale, domain, translations)
* .setLocale(locale)
* .setTextDomain(domain)
* .gettext(msgid) ⇒ String
* .dgettext(domain, msgid) ⇒ String
* .ngettext(msgid, msgidPlural, count) ⇒ String
* .dngettext(domain, msgid, msgidPlural, count) ⇒ String
* .pgettext(msgctxt, msgid) ⇒ String
* .dpgettext(domain, msgctxt, msgid) ⇒ String
* .npgettext(msgctxt, msgid, msgidPlural, count) ⇒ String
* .dnpgettext(domain, msgctxt, msgid, msgidPlural, count) ⇒ String
* .textdomain()
* .setlocale()
* ~~.addTextdomain()~~

$3

- [options]: Object - A set of options
- .sourceLocale: String - The locale that the source code and its
texts are written in. Translations for
this locale is not necessary.
- .debug: Boolean - Whether to output debug info into the
console.

$3

- eventName: String - An event name
- callback: function - An event handler function

$3

- eventName: String - An event name
- callback: function - A previously registered event handler function

$3

- locale: String - A locale string
- domain: String - A domain name
- translations: Object - An object of gettext-parser JSON shape

Example
`js
gt.addTranslations('sv-SE', 'messages', translationsObject)
`


$3

- locale: String - A locale

Example
`js
gt.setLocale('sv-SE')
`


$3

- domain: String - A gettext domain name

Example
`js
gt.setTextDomain('domainname')
`


$3

- msgid: String - String to be translated

Example
`js
gt.gettext('Some text')
`


$3

- domain: String - A gettext domain name
- msgid: String - String to be translated

Example
`js
gt.dgettext('domainname', 'Some text')
`


$3

- msgid: String - String to be translated when count is not plural
- msgidPlural: String - String to be translated when count is plural
- count: Number - Number count for the plural

Example
`js
gt.ngettext('One thing', 'Many things', numberOfThings)
`


$3

- domain: String - A gettext domain name
- msgid: String - String to be translated when count is not plural
- msgidPlural: String - String to be translated when count is plural
- count: Number - Number count for the plural

Example
`js
gt.dngettext('domainname', 'One thing', 'Many things', numberOfThings)
`


$3

- msgctxt: String - Translation context
- msgid: String - String to be translated

Example
`js
gt.pgettext('sports', 'Back')
`


$3

- domain: String - A gettext domain name
- msgctxt: String - Translation context
- msgid: String - String to be translated

Example
`js
gt.dpgettext('domainname', 'sports', 'Back')
`


$3

- msgctxt: String - Translation context
- msgid: String - String to be translated when count is not plural
- msgidPlural: String - String to be translated when count is plural
- count: Number - Number count for the plural

Example
`js
gt.npgettext('sports', 'Back', '%d backs', numberOfBacks)
`


$3

- domain: String - A gettext domain name
- msgctxt: String - Translation context
- msgid: String - String to be translated
- msgidPlural: String - If no translation was found, return this on count!=1
- count: Number - Number count for the plural

Example
`js
gt.dnpgettext('domainname', 'sports', 'Back', '%d backs', numberOfBacks)
`


$3

Version 1 of node-gettext confused domains with locales, which version 2 has corrected. node-gettext also no longer parses files or file paths for you, but accepts only ready-parsed JSON translation objects.

Here is a full list of all breaking changes:

* textdomain(domain) is now setLocale(locale)
* dgettext, dngettext, dpgettext and dnpgettext does not treat the leading domain argument as a locale, but as a domain. To get a translation from a certain locale you need to call setLocale(locale) beforehand.
* A new setTextDomain(domain) has been introduced
* addTextdomain(domain, file) is now addTranslations(locale, domain, translations)
* addTranslations(locale, domain, translations) only accepts a JSON object with the shape described in the gettext-parser README. To load translations from .mo or .po files, use gettext-parser, and it will provide you with valid JSON objects.
* _currentDomain is now domain
* domains is now catalogs
* The instance method __normalizeDomain(domain) has been replaced by a static method Gettext.getLanguageCode(locale)`

License

MIT

See also

* gettext-parser - Parsing and compiling gettext translations between .po/.mo files and JSON
* lioness – Gettext library for React
* react-gettext-parser - Extracting gettext translatable strings from JS(X) code
* narp - Workflow CLI tool that syncs translations between your app and Transifex