Skip to main content
The frontend only loads the translation keys listed in services/web/frontend/extracted-translations.json (services/web/frontend/translations-loader.js). The backend and its templates read the full files in services/web/locales/. Run this in the develop directory once after the first setup, and again after adding a translation or changing branch:
bin/i18n does two things:
  1. It resets services/web/locales/*.json to the committed files, then applies the locale patches the way the image builds do: the files of the highest locales_patches/v* folder replace the locales, and locales_patches/added/*.json are merged on top, key by key.
  2. It runs yarn run extract-translations as the node user in the webpack container, which rewrites extracted-translations.json. If the webpack image is missing, it first syncs yarn.lock with bin/sync and builds the image.
It needs jq on the host.
The changes bin/i18n makes to services/web/locales/*.json are local only. Do not commit them.
Please reuse an existing key whenever possible. The locale files come from Overleaf upstream or a third-party translation site, so do not edit them directly. A new key goes into services/web/locales/locales_patches/added/, in the file of every language at once (en.json, zh-CN.json and the others).
Last modified on November 13, 2026