Lingo.dev product update: language-specific review

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. Open the localization engine’s Pipeline tab, select the languages under Human review, and set your quality threshold. You can change the selection as your needs change, or leave it empty to apply the review rule to every language. If your integration sends its own human-review settings with a request, include the selected languages there too. Request-level settings replace the saved human-review configuration; omitting the language list applies review to all languages, subject to the threshold supplied in that request. Focus improvement suggestions on selected languages You can also choose which languages your localization engine generates improvement suggestions for. This selection is separate from human-review routing, so the two lists don’t have to match. For example, after reviewers correct terminology in a newly added language, you can focus suggestions on that language. Lingo.dev uses quality findings and reviewer corrections to propose changes to your glossary, rules, and brand voice for future translations. Choose the languages in the localization engine’s Suggestions tab. Leave the selection empty to include all languages. In Queue, filter to suggestions to select several and apply or dismiss them together. Bulk apply shows progress and can be stopped between batches. Its final summary shows how many suggestions were applied, failed, or never started. More improvements and fixes Require a localization engine ID. Turn on Require engine ID under Settings → General to reject requests that omit it, instead of automatically using a default localization engine. Leaving the setting off preserves the existing behavior. Recover CLI downloads after temporary connection failures. The server now retries transient database failures during translated-file downloads. The fix applies without upgrading your CLI. See active incidents directly on the platform. You could already subscribe to service updates at status.lingo.dev. Now, active incidents also appear in a banner on the Lingo.dev platform, with a link to the incident report. The banner disappears when the incident is resolved. Read the full changelog → – Veronica Lingo.dev · San Francisco, CA Unsubscribe