How to use the Multilingual UI Length Checker.
UI text length checks need an explicit counting rule and real layout testing. Character count is a screening signal; glyph width, font, wrapping and placeholders determine whether text fits.
Make the workflow fit your task.
Choose the counting unit and any hard limit, then measure source and target strings including substitutions where relevant. Report overages without shortening automatically. Test the actual interface because font, script, wrapping and dynamic values determine visual fit.
- What you provide
- Interface strings and supplied length budgets.
- What you get
- Potential expansion and truncation risks.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Button limit is 10 Unicode code points. English Save has 4; French Enregistrer has 11.
Completed example
Save passes the supplied character limit. Enregistrer exceeds it by 1. Review the translated button in the actual font and layout before shortening it or changing its meaning.
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.
Can equal character counts guarantee equal button widths across languages?
No. Glyph widths and fonts differ, so length screening must be followed by layout review.
Why does a translation pass the limit but overflow in use?
A placeholder may expand to a longer value or the container may be narrower. Test representative dynamic values and viewport sizes.
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 ↑