How to check translation terminology across a set of strings
Consistency review helps identify when the same intended concept is translated differently without a useful reason. It is especially helpful when several people have contributed to a product or document.
Start with the right material.
- What you provide
- source text, translation and an optional glossary supplied together.
- The intended result
- Flag meaning changes and glossary inconsistencies for bilingual human review.
How the workflow works.
Compare the supplied source and target text against an approved glossary or stated terminology rule. Keep contextual differences visible so a button action is not forced to use the wording of a status label.
What to check in the result.
Review each proposed correction before applying it. Consistency is valuable when the underlying meaning matches; identical English wording can legitimately require different translations in different contexts.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Source term, Required translation, Observed translation, Issue. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.