The translation fits fourteen characters; you still need to check the button

Fourteen characters satisfy one condition, not the whole label

If your project sets a fourteen-character maximum, “Guardar cambios” does not meet it: it has fifteen characters including the space. “Guardar” has seven and meets that limit, but deciding whether it works as a label requires knowing the button’s context. A length check can flag an oversized string; it cannot establish that the action is clear or the text renders well.

This localisation example is invented. The source string “Save changes” has twelve characters. Fourteen is a condition chosen for this example, not a general Iria limit or a property of every Windows button.

Retain three facts before shortening

Keep the source text, the control’s action and its context. If the button sits at the end of an editor and saves current changes, “Guardar” may be a candidate for review. If two nearby controls save different things, the same word may not distinguish them. Do not remove “cambios” merely to clear a warning.

A reasoned review can proceed by counting the string, consulting context and proposing an alternative, then checking that candidate in the destination interface through your project’s process. If context is missing, request it or keep the proposal pending. Passing a structural check is different from approving meaning.

What Studio checks and what a person decides

The Iria facts page documents local JSON/RESX projects in Localization Studio and structural checks for placeholders, markup, plurals, limits and access keys. It also states that those checks do not establish translation meaning or quality. Source context and RESX comments are part of the review workflow.

A character limit also does not specify width in pixels: font, size and available space are separate conditions. Keep those conditions separate: counting text addresses length, while reviewing the label in its destination lets you assess the space and font you actually use.

Interpret other tools’ results with the same care

Weblate explains its translation editor, and Crowdin documents its editor. Crowdin’s maximum-character check illustrates another threshold check. These sources do not establish identical controls or comparative translation quality.

As a next step, prepare a non-sensitive sample string and its context, consult the current Iria guide and download, and review what blocks your project before export. The published Iria release includes Studio. The cover only illustrates the distinction between counting text and reviewing its destination.