@jesuskris/i18n-json-multi-client NPM

@jesuskris/i18n-json-multi-client

Simple framework-neutral json-based translations with no dependencies and support for multi-client.

Forked and extended upon @codeborne/i18n-json

npm install @jesuskris/i18n-json-multi-client

See sample on how to structure your translation files.

This format is also supported by Translate Tool GUI.

Usage

Non-specific

In your project create a i18n.ts which will you use for imports:

import {init} from '@jesuskris/i18n-json-multi-client'
export * from '@jesuskris/i18n-json-multi-client'

export let langs = ["en", "fi"]
export async function initTranslations() {

  await init({langs})
}

Then call await initTranslations() in your index.ts to load the selected language file.

To translate a key, call _('your.translate.key') Or with replacements: _('users.hello', {name: 'World'})

Pluralized strings are also supported: _('trees', {count: 1}), which for English could look like: "trees": "You have {count|one:# tree|other:# trees}" and Russian would be: "trees": "У вас есть {count|one:одно дерево|few:# дерева|many:# деревьев}". Plurality keys are provided by browser's Intl.PluralRules for the language.

See tests for more examples.

Client-specific

To write client-specific translations, you need to pass in an identifier:

import {init} from '@jesuskris/i18n-json-multi-client'
export * from '@jesuskris/i18n-json-multi-client'

export let langs = ["en", "fi"]
export let clientIdentifier = "client1"
export async function initTranslations() {
  await init({langs, clientIdentifier})
}

Then in translation format define client specific translations:

{
  "homepage": {
    "header": {
      "client1": "Welcome to our Client 1 Portal",
      "client2": "Welcome to our Client 2 Portal",
      "default": "Welcome to our Portal"
    }
  },
  "contacts": {
    "email": "Email",
    "phone": "Phone",
    "address": "Address"
  }
}

In the above example we have defined 2 client specific translations for key homepage.header

Now simply call the translation in your code:

<header>{_("homepage.header")}</header> <!--Welcome to our Client 1 Portal-->

The default key in client-specific translations acts as a fallback if clientIdentifier is not matched.

Keep in mind that it works without the default fallback. When a key is not found, it returns the full key path.

See tests for more examples.

Frameworks

The library is very small, has zero dependencies and is framework-agnostic. You can use with Svelte, React, Vue or anything else.

If using a SPA framework and want to switch languages on-the-fly (without page reload), you need to add a small wrapper for the _ function.

E.g. in Svelte you would use a store to set/retrieve the function and then use it as $_().

Post compilation step

You can merge translation files by adding missing keys/values from default lang to all others at build time, not needing to do fallback for untranslated keys at runtime.