An exploration into i18next and the way it works for localization and internationalization.
"boolean_key": "--- true\n",
"key_with_description": "Check it out! This key has a description! (At least in some formats)",
"key_with_line-break": "This translations contains\na line-break.",
"key": "Wow, this key is nested even deeper."
"key": "This key is nested inside a namespace."
"simple_key": "Just a simple key with a simple message.",
"unverified_key": "This translation is not yet verified and waits for it. (In some formats we also export this status)",
"pluralized_key": "Only one pluralization found.",
"pluralized_key_plural": "Wow, you have %s pluralizations!"
What is supported?
i18next offers a lot of functionality. We support
- Keys ending in _0, _1, _other etc. will be mapped to the according plural forms (see here).
- Namespaces via tags (see here)
What is not supported?
Interval Pluralizations are persisted as normal key values. There is no support in the UI.
Nesting / Variable replacement is not supported directly. However, placeholders can be activated. We currently do not support cross-referencing keys from within values. There is no support in the UI.