BabelizeBabelize
Features

Results

See what a babel changed before you open the pull request: every translation by language, the code it wrapped, and edits that stick on later babels.

When a babel finishes, open it (See results, or Review the translations and code changes on the project page) to see what it did before anything reaches your repository. Results has four tabs: Translations, Changed files, Issues (when there are any) and Activity.

Translations

Every text the babel translated, with one column per language. Search across keys, the source and translations, or show only texts that are Edited, came From translation memory, are Not translated, or had an Edit replaced.

Editors and admins can fix a translation in place: hover a cell and click the pencil, then Save (or ⌘ Enter). An edit:

  • goes into the next pull request update, and into the download, without another babel;
  • wins on every later babel. Babelize never translates over it while the source text stays the same;
  • is saved to your translation memory as approved, so your other projects reuse it.

If the source text of an edited key changes, Babelize translates it again and marks the cell Your edit was replaced, so you can check the new wording. Undo puts the previous translation back, and the next babel translates the text again.

Viewers can read translations but not change them. Earlier babels are read-only; edit in the latest one.

Glossary from the table

Click the book icon on any translation to add it to the glossary: always translate a term the same way in that language. The next babel applies it wherever the term appears. Glossary terms are underlined in the source column. See Glossary.

Changed files

Each file the babel changed, before and after: the text it wrapped in translation calls (t('…')) and the i18n setup it added. Switch between Unified and Side by side. Changed files are kept for a project's latest babel only.

Issues

Texts that weren't translated or need a look, with the reason: a translation that failed a check (placeholders, tags, plural forms, glossary terms), right-to-left or length warnings. Texts that failed are retried on the next babel.

Activity

The babel's steps, from checking the project to wrapping up, with how long each took.

Next step

From the results, Open pull request (or Update pull request when one is open) for GitHub projects, or Download project for ZIP uploads. See Exports.

Last updated: 2026-10-18

How is this guide?

On this page