How to create a localization glossary from supplied terminology
A localization glossary records the preferred treatment of important terms before translation spreads across many pages. It helps reviewers explain choices instead of correcting the same issue repeatedly.
Start with the right material.
- What you provide
- an owned technical page plus target language.
- The intended result
- Export key terms, context and proposed translations with review-needed flags.
How the workflow works.
Identify product terms, abbreviations and concepts that need consistent handling. Include context, the source term and any approved target equivalent, marking unresolved choices for review.
What to check in the result.
Confirm terminology with someone responsible for the product and target language. Avoid inventing official names or forcing a single translation onto concepts that the source uses differently.
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, Context, Spanish proposal, Review status. 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.