File Formats

Babelize uses JSON locale files for React, Next.js, Vue, React Native and static HTML projects, and gettext catalogues (.po/.mo) for Django. When it scans your repository, it extracts translatable strings from your source code and writes a locale file for every target language.

Locale Files: JSON

Each locale gets its own file, for example en.json, es.json, and fr.json. Every target file mirrors the keys of the source file, so your i18n library (such as next-intl, react-i18next, or vue-i18n) can load them side by side.

Nested keys group related strings:

{
  "messages": {
    "greeting": "Hello, {name}",
    "farewell": "Goodbye"
  }
}

Flat keys work too:

{
  "greeting": "Hello, {name}",
  "farewell": "Goodbye"
}

When translating, Babelize:

• Preserves keys and nesting exactly; only string values are translated
• Leaves numeric and boolean values untouched
• Keeps placeholders such as {name} intact (see Placeholder Protection)

Locale Files: gettext (Django)

Django projects use gettext catalogues instead of JSON: <LOCALE_PATHS[0]>/<lang>/LC_MESSAGES/django.po (by default locale/ next to manage.py).

• Strings come from Python files (.py: existing gettext calls plus hardcoded UI strings in models, forms, admin and views) and Django templates ({% trans %} / {% blocktrans %}, with hardcoded text wrapped in {% translate %})
• Existing .po translations are kept, never re-translated; fuzzy entries are left for you to review
• .mo files are recompiled when they are tracked in the repository
• LANGUAGES and LOCALE_PATHS in settings.py are updated

See Django for details and current limitations.

Not Supported

Other locale formats, such as YAML, XLIFF, ARB, Markdown content, or iOS/Android string files, are not supported yet.

Source Files Scanned

Babelize extracts hardcoded strings from these source file types:

Placeholder Protection

Babelize automatically detects and protects common placeholder patterns:

Protected spans must come back exactly once. If a translation drops, repeats or invents one — or returns an invalid ICU message, mismatched tags, or the untranslated sentence — Babelize asks the model once more with a note about what was wrong. If it still fails, the string is not written to the locale file and is reported with the reason, so your app shows the source text instead of a broken translation, and the next run retries it.

Never-translate glossary terms are protected the same way, and "always translate as" terms are sent to the model as required terminology.

Encoding

All files must be UTF-8 encoded. Other encodings are converted automatically with a warning.

Further Reading