Exports

After a babel, GitHub projects get their translations as a pull request, and ZIP projects as a translated project to download. With npx babelize, the translations are written straight into your project folder.

GitHub Pull Request

1. Start a babel on your project
2. Review the results: translations, changed files and any issues
3. Click Open pull request (or Update pull request when one is already open)
4. Review and merge the PR on GitHub

The PR contains the translated locale files, one per target language, organized to match your project structure (JSON for JavaScript projects, gettext .po and recompiled .mo catalogues for Django), plus the code changes that use them. Its description has a table of languages, how to try it, and a checklist of what to check before you merge.

While the PR is open, Update pull request adds later babels to it, and edits you make in Results, without another babel. With Auto-localize, push-triggered babels keep one rolling PR up to date on the babelize/<branch> branch.

You can also raise the PR from the terminal with babelize pr raise <project-uuid>.

Download

1. Open the project (ZIP projects), or the babel's results
2. Click Download project (on a GitHub project's results, it's the download icon next to the pull request button)
3. You get a ZIP of the project with the translations applied (locale files and i18n code changes), including any edits you made in Results

From the terminal: babelize projects download <project-id>.

Export Format

Translations are exported as JSON locale files with the same keys and nesting as your source locale file, or as gettext .po/.mo catalogues for Django. See File Formats for details.

All exports use:

• UTF-8 encoding
• Your files' existing line endings and indentation: only the lines with translated text change