Lingo.dev
Day 32 after signup
W46 Product Update: Introducing Radar, find translation errors in languages you don't read
Score every translation, see why it's wrong, and track quality over time.
Why it works
- Open with the feature’s main benefit so readers quickly understand the problem it solves.
- Break the capabilities into distinct use cases, making a multifaceted feature easier to scan.
- End with one clear link to setup details for readers ready to explore further.
How it is built
- Feature introduction
- Built-in measurement options
- Custom measurement examples
- Quality reporting benefits
Email copy
Radar, Lingo.dev's new feature, checks the quality of your translations, scores them, and explains every error it finds, so you don't need to read the language. With Radar, you can: Turn on built-in measurements. MQM, glossary and rule adherence, edit rate and edit distance are ready to use. Add custom measurements. Describe a requirement in plain English, like "Product names stay in English", and Radar checks every new translation against it. Track quality with reports. See how scores change each week, month or quarter, and share the report with your team. Ask your AI assistant. Through the Lingo.dev MCP server, your AI agent can query your results and chart them in the conversation. See how to set up Radar in the full changelog → – Veronica Lingo.dev · San Francisco, CA Unsubscribe