Workflow
A translation isn't done the moment it's typed. It moves through a defined set of states, with the invalid jumps blocked, its origin recorded, and every change kept — so what reaches production has been through the checks you expect.
The states
Each translation sits in exactly one state, and the workflow only allows the transitions that make sense — you can't publish something that was never reviewed.
Being written or edited.
Produced by AI, awaiting review.
Submitted for a human check.
Signed off, not yet live.
Live, and ready to export.
Sent back for changes.
Retired from active use.
Origin & review
Each translation records how it arrived. That matters most for AI: anything marked as AI-generated enters a state that can't be published without a human review first — so machine output is always checked before it ships.
Every change kept
Nothing is silently overwritten. Every state change and every text edit is written to an append-only history — who did it, where it came from, and the text before and after — across strings, plurals, and documents alike.
Keep exploring
Strings and documents, translated with a real review workflow.
Keys with context, ICU placeholders, and CLDR-correct plurals.
Localize whole CMS documents, per language, with HTML round-trip.
Eight formats — Android, iOS, Flutter, web, and XLIFF.