Veronica Prilutskaya

You can now send translations to human review only when they re in a language you select and score below your quality threshold. All others continue without human review.

Keep human review to selected languages

You could already use a quality threshold to send low-scoring translations to human review. Now you can narrow that rule to selected languages within the same localization engine.

For example, when introducing Japanese or working through terminology issues in German, you can send low-scoring translations in those languages to a reviewer. Translations that meet your threshold continue automatically, and your other languages skip human review.

You can now connect content sources to your localization engines in Studio, translate content with your team's glossary, rules, and brand voice, and write translations back to your repositories, CMSs, or help centers.

Connect GitHub, Payload CMS, or Zendesk Help Center, or submit content through the CLI and API. Each source uses the localization engine you choose, with your team's glossary, rules, and brand voice. Product and content teams submit content from their own tools, while the localization team runs the localization infrastructure.

The CLI. Engineers use lingo push to submit source files through the localization engine's configured pipeline. lingo pull writes the completed translations to local target files on the same machine and checkout. Studio lists each submission with its status by language.

The GitHub App. When source files change on the default branch, the app translates the changes and opens a pull request with the translated files. Enable the pull request workflow to commit translations directly to a pull request branch. Require approval before automatic runs, or use /lingo translate to request specific files and languages.

Localization infrastructure is now in one place.

Infrastructure is where you configure localization engines, models, context, pipelines, and everything else that controls how your content gets translated.

Here's what you'll find there:

Localization engines. Create separate localization engines for different kinds of content. Your product UI, help center, and legal content can each have their own setup, models, context, and localization pipeline.