DSP 02 / ORIGINAL EDITORIAL
Two languages can mean two workflows
Translation is not a final copy step when language changes authority, evidence, tone, or review.
A translated interface can be grammatically correct and operationally wrong. Language affects who can review a result, what counts as clear evidence, and how a recommendation is understood.
Translate the job, not only the words
Compare how the task is actually described, handed off, and approved in each language. The same label may hide different sequences, responsibilities, or expectations.
Keep source and interpretation visible
Store the original source, the translated text, the translator or method, and the review state separately. A reviewer needs to know when a result is a direct source, a translation, a summary, or a generated interpretation.
Test consequential phrases
Prioritize phrases that grant permission, deny service, state uncertainty, request consent, or explain an exception. Test them with people who understand both the language and the operating setting.
TAKE TO THE FIELD
Questions before transfer
- Which phrases change a decision?
- Who can judge operational meaning in each language?
- Can a reviewer reach the original source?
- How is disagreement recorded?
Multilingual quality is a review system, not a translation checkbox.