Formats / i18next JSON

i18next JSON, with the plural suffixes per language

i18next spells plurals as a suffix on the key, and which suffixes exist depends on the language rather than on the file.

.json

The suffix set is not the same in every language

English needs key_one and key_other. Czech and Polish need key_one, key_few, key_many and key_other. Spanish, French and Italian need one, many and other. A file copied from the English locale and translated in place ends up with two forms in a language that needs four, and the missing ones render the key.

Linguiqo lays out the boxes a language actually has and writes exactly those keys back.

Nested or flat, whichever the file is

Nested objects and flat dotted keys are both read, and the file is written in the shape it arrived in rather than reorganized underneath the project that consumes it.

Questions

Does it support namespaces?

One project holds one set of keys, and every file mapped to a language receives all of them. Give each namespace its own project, and each file gets back exactly its keys.

What about interpolation like {{name}}?

Interpolations are detected and checked. A translation missing one the source has is a quality error, not a warning.

Upload a i18next JSON file and see

The demo reads a real file of yours and shows what came back. No account, nothing kept.

Open the demo

What Linguiqo is