Quality Controls

Quality controls run automatically as translators work, surfacing issues before a project is submitted for review rather than after it reaches QA. The goal is to shift error detection left — closer to the point of translation — where corrections are cheapest to make.

Spelling and grammar checks are the first layer. The checker is language-aware, running against the target language dictionary so French translations are checked against French rules, not English ones. Errors are flagged inline in the editor so translators can address them without leaving their current string.

Number consistency checks verify that numeric values in the source string are preserved in the translation. A source string containing '5 kg' should not produce a translation reading '6 kg'. These mismatches — common when a translator accidentally modifies a number while editing — are detected and flagged automatically.

Placeholder and tag checks verify that variables, tokens, and formatting tags survive translation intact. A source string like 'Hello , you have messages' must produce a translation that contains both and . Missing or renamed placeholders break the underlying code at runtime, so these checks run on every saved string without exception.

Together these checks form a quality gate that runs continuously rather than as a single end-of-project review step. Project managers can see which strings have outstanding issues in the quality report before approving a translation batch for release.