All products

Localise an app with AI and i18next

Find visible text, connect it to locale resources and check the result in the application, with the option to keep all translations in the repository.

Localise an app with AI and i18next when switching languages changes the navigation but leaves a few buttons in the original language. The i18next-localization skill starts with the project’s current state. An app that already has working translation resources may only need the remaining strings identified and connected to the existing setup.

The developer also gets a choice about storage. Local files can remain the source of truth, or an authorised Locize project can provide a shared translation workflow. Choosing this early avoids an unnecessary sign-up and keeps the team clear about where its product copy will go.

What it does

  • Find hardcoded strings in a chosen application scope.
  • Set up locale resources appropriate to the current framework.
  • Check which extracted keys still lack values in a target language.
  • Look for discrepancies in translated placeholders before testing the screen.
  • Keep translations in version control or connect the hosted workflow the developer selected.

Install and use

  1. Use a local JavaScript project, the official i18next CLI and a compatible framework integration. The local-file route needs no Locize account.
  2. Ask, “Localise the basket page with our existing i18next setup, retain the files here and show which labels still need translated values.”
  3. Run the checks and open the same screen in both languages with representative counts and names.

FAQ

Source

Made by i18next. Original skill: i18next-localization, published on GitHub under the MIT licence.

View on GitHub