i18next JSON files

Changed in version 4.15.1: Support for v4 variant of this format was added.

Hint

In case you use plurals, it is recommended to use v4 as that aligned plural handling with CLDR. Older versions have different plural rules for some languages which are not correct.

i18next is an internationalization framework written in and for JavaScript. Weblate supports its localization files with features such as plurals.

i18next translations are monolingual, so it is recommended to specify a base file with (what is most often the) English strings.

i18next JSON file v4

Choose this format if unsure. It stores plurals using standard CLDR suffixes.

i18next JSON file v3

Use for legacy projects which are using numeric suffixes for plurals.

Note

The v2 and v1 variants are mostly compatible with v3, with exception of how plurals are handled.

See also

• JSON

• https://www.i18next.com/

• i18next JSON Format

• Updating target-language files

• Customize JSON output

• Cleanup translation files

Example file:

{
  "hello": "Hello",
  "apple": "I have an apple",
  "apple_plural": "I have {{count}} apples",
  "apple_negative": "I have no apples"
}

Supported features

File extensions	.json
Linguality ⓘ	Both monolingual and bilingual
Supports plural ⓘ	Yes
Supports descriptions ⓘ	No
Supports explanation ⓘ	No
Supports context ⓘ	No
Supports location ⓘ	No
Supports flags ⓘ	No
API identifier	i18nextv4
Supports read-only strings ⓘ	No

Supported features

File extensions	.json
Linguality ⓘ	Both monolingual and bilingual
Supports plural ⓘ	Yes
Supports descriptions ⓘ	No
Supports explanation ⓘ	No
Supports context ⓘ	No
Supports location ⓘ	No
Supports flags ⓘ	No
API identifier	i18next
Supports read-only strings ⓘ	No

Weblate configuration

Typical Weblate Component configuration
File mask	langs/*.json
Monolingual base language file	langs/en.json
Template for new translations	Empty
File format	i18next JSON file v3