How to localize interface microcopy with context and length limits
Short interface text needs more context than its word count suggests. A button, error message and status label may use different wording even when the English source looks similar.
Start with the right material.
- What you provide
- visible UI labels plus target language and supplied length limits.
- The intended result
- Export source strings and translated suggestions with context and length flags.
How the workflow works.
Provide each string's role, target language and actual length constraint. Preserve placeholders and distinguish a proposed translation from a layout-tested final value.
What to check in the result.
Check meaning, character counting and the rendered interface. A string can fit a supplied character limit while still wrapping poorly or describing the wrong action in the product.
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 label, Context, French draft, Character count, Limit, Length 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.