Length limits

Request shorter translated strings without truncating their meaning, then check the final result in its interface.

A translation can need more space than its source. For a compact interface, the content-length stage attempts a shorter wording within a display-column budget. It does not truncate the text. If a fitting rewrite cannot be produced, the earlier translation can remain over budget.

The budget guides wording; the actual interface determines whether it fits. Font, shaping, size, and available space still need a rendering check.

Choose the constraint #

ModeBudget
Fixed cap (fixedCap)A configured maximum number of display columns.
No longer than source (noLongerThanSource)The corresponding source string's display-column width.
Source width with tolerance (matchSource)Source width plus the configured percentage tolerance.

A fixed cap suits a known compact field. A source-relative mode expresses an expansion policy across strings of different lengths. Both need language-sensitive inspection. Source-width matching is an upper bound, so it does not pad a naturally shorter translation.

Display columns are terminal-style units. Most Latin characters count as one; CJK full-width characters commonly count as two. A short CJK label can therefore use as many columns as a longer Latin label. Neither character count nor display-column width establishes browser pixels, and neither is a token count.

Preserve the complete message #

The stage attempts shorter wording and rejects rewrites that drop expected placeholders. When fitting fails, it retains earlier output rather than cutting it at the cap. Inspect those retained violations, especially when the message includes a qualification or condition.

Removing “business” from “within five business days” changes the stated time even if the result occupies less space. The useful result is a shorter expression of the same requirement. Where that affects acceptance, define an independent meaning check.

Check the final output, not only the fitted stage #

Content-length processing follows human review and post-edit, and precedes back-translation. A later correction can change the wording again. A fitted intermediate value is therefore not a hard limit on the final output. Inspect stage warnings and retained text through run evidence.

Configure the stage on the localization engine or through the selected job contract. Submission overrides replace a supplied stage's configuration as a whole; omitted stages inherit defaults. These fields express display-column budgets, not per-string browser widths.

Load the returned translation in the consuming interface at the intended locale, font, and viewport. Check wrapping, clipping, substitutions, and meaning together. If the language cannot express the requirement safely in the available space, adjust the component or budget rather than silently removing part of the message.