The string grew and the button no longer fits. Whose job is that?
The translator owns a string that says the right thing inside the limit. The person who builds the page owns the control: its width, its wrapping, and whether the design can give the button more room. When the string grows and the button breaks, both jobs are open, and neither is finished by blaming the other. The wording is shortened only with the meaning intact, or the control is widened, or the string moves to a place that can hold it. Someone has to choose, and the choice is visible.
“Request a sample” came back from translation several words longer, and the navigation bar on the product page wrapped into a second line on a laptop and overflowed the edge on a phone. The developer asked for “the short version by default.” The marketing owner asked for the full words because the short version sounded like a download. The translator could write a shorter true label, and could not see the pixel width from a spreadsheet alone. The fix started by putting the long string and a shorter true string into the actual bar, on one desktop width and one phone width, and letting the page owner pick. Guessing a character count in a table had already failed once.
The limit is part of the source, so ask for it early
A button, a tab, a menu item, and a card title have a length. Get the limit in characters or, better, get the component and look at it. Write to the limit on the first draft. Chinese and English swell in different directions. About two Chinese characters to one English word is a rough money comparison for running text, and it is a poor predictor of a button, where one long compound or one short verb changes the pixels. Count the source string by the word if it is English and by the character if it is Chinese, and still judge the result in the component.
Layout and front-end adjustment are separate from the translation rate. There is no public unit price that includes every broken component in a site. The quote says whether you are delivering strings, or strings placed and checked in the page.
Who edits the words when the control is fixed
If the design cannot move, the translator proposes a shorter string that keeps the action: what the user does, and what they get. A shorter string that changes the action, from a sample request into a generic “submit,” fails even if it fits. The page owner accepts the shorter string in email, against the version, with a screenshot. If the words cannot shrink without lying, the control has to change, and that change belongs to the people who own the template. The translator flags the collision. The translator does not quietly restore an overflowing line because it was “more correct,” and the developer does not quietly invent a synonym.
Record the chosen short string in the key list, so the next language and the next redesign inherit the limit and the decision.
Hand back a string the build can import
Deliver the key, the string, the screenshot of the fitted control, and a note of any key still overflowing. The import file is the delivery. A paragraph pasted into chat will lose the key name and come back applied to the wrong button. Versions live in the project system with the date. Unchanged keys stay frozen, the way a three-sentence site change does not justify retranslating the whole site. Only the grown string and the keys that repeat it are in this round.
Review the visible page after import, not only the spreadsheet. A string can fit the sheet and break the component, which is the situation that started the job.
Is truncation with an ellipsis an acceptable fit?
It is acceptable when the full string is still available to the user, for example in a tooltip that is itself translated, and when the truncated form does not become a different command. An ellipsis that hides the word “not” is a defect. If you use truncation, say so, and test it in the language that grew.
Do icon-only buttons avoid the problem?
They avoid the width problem and create a meaning problem. The accessible name still has to be translated and still has to carry the action. Deliver that name with the same care as the visible label, and check it with a screen reader or the accessibility tree if the page is being verified.
The related service page is localization.
Quick FAQ: AI Translation Accuracy
- How accurate are AI translators? Accuracy is often high for repetitive or general content, while domain-sensitive content still needs expert review.
- How to improve AI translation quality? Use glossary control, domain prompts, QA checks, and human post-editing in one workflow.
- Where does human translation still win? Legal, medical, and high-stakes brand content usually requires human nuance and accountability.