Extracting translations
Last updated
Last updated
At some point you will come to the question how to get new translation key/values into your namespace (translation) file.
While for sure this is the least efficient method for adding new translations, we know a lot of projects are doing this. There is actually nothing wrong with it beside being some extra work developers could avoid.
Static extraction tools can read through your code files to automatically find and export translation keys. , and are sensible choices to achieve this goal.
Or try , it shows an overview of your translations in a nice UI. Check which keys are not yet translated.
For more information about extraction tools, see documentation page.
I18next has a setting to send all keys that it was unable to resolve during runtime using the attached backend.
In case of the http-backend just set saveMissing: true
on init:
This is the most convenient way of working with react-i18next: just develop and run your applications without worrying too much about adding translations to your catalog as those get added automatically.
Check the for where missing translation gets sent.
Using node.js and express? You can get that endpoint for free:
Wanna have this process on steroids? Just hook up a localization project using the provided backend and get both the saveMissing and loading of translations automated in a true continuous localization process.