Review Localizations
Evaluate localizations against your engine's rules without modifying anything. Your assistant reads the engine's configuration and reports violations per string.
The workflow#
"Check these 10 German strings against our engine. Are all glossary terms applied? Do they follow the formal register?"
What happens:
- The assistant reads your engine's glossary, rules, and brand voice for
de - Evaluates each localization for glossary compliance, rule adherence, and tone consistency
- Reports violations per string: "Line 3: 'Checkout' was localized to 'Kasse' but your glossary marks it as non-translatable. Line 7: informal 'du' used, but brand voice specifies 'Sie'."
When to use this#
- Before shipping — spot-check critical strings
- After receiving localizations from an external source
- Validating that a tune actually fixed the issue across a batch
- Auditing localizations produced before the engine was configured
What gets checked#
| Dimension | What the assistant verifies |
|---|---|
| Glossary compliance | Are required term localizations honored? Are non-translatable terms preserved? |
| Rule adherence | Are locale-specific rules followed (spacing, punctuation, formatting)? |
| Brand voice consistency | Does the tone match the configured register (formal/informal, polite/casual)? |
| Terminology consistency | Are the same source terms localized the same way across the batch? |