How to use the Translation Quality Reviewer.
Translation review should prioritize meaning, terminology and audience before stylistic preference. Distinguish clear errors from acceptable alternatives and explain each proposed revision.
Make the workflow fit your task.
Compare source and target against the intended audience, terminology and product action. Classify meaning errors separately from style preferences and propose minimal justified corrections. Preserve placeholders and formatting, then test critical interface wording in context.
- What you provide
- Original, translation and style requirements.
- What you get
- Accuracy, terminology and fluency issues.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
English source: Save your draft. French translation: Supprimez votre brouillon.
Completed example
Critical meaning error: Supprimez means delete. Suggested French: Enregistrez votre brouillon. Confirm the product glossary and the action the button actually performs.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a reviewer replace every phrase with their preferred wording?
Distinguish acceptable alternatives from actual problems. Prioritize meaning, terminology and usability over personal style.
Why is a fluent translation still a serious interface error?
It may describe the wrong action, such as delete instead of save. Check the control's actual behavior and source intent.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑