Planta does not always mean plant: test your glossary before repeating the mistake

Before making a word your preferred translation, test it in two phrases with different meanings. In a building, the Spanish “Planta 2” can be Floor 2; at an industrial facility, “Planta de montaje” can be Assembly plant. A general “planta → plant” terminology preference does not resolve both texts.

These are original writing examples, not outputs obtained from Iria or errors observed in customer work. The useful decision is which meaning you need to preserve and where it appears.

Describe the meaning before fixing the term

Suppose you are preparing two texts for a fictional application. One directs someone around a building and the other names an industrial facility. Make a working note with four parts:

• The complete source expression, rather than the isolated word.
• What it refers to on that screen or in that document.
• Your proposed translation for that use.
• Another phrase where the proposal would no longer fit.

For “Planta 2,” the note could say: “Building level; proposed Floor 2; do not apply this decision to a factory.” For “Planta de montaje”: “Industrial facility; proposed Assembly plant; not a building level.” These are manual working notes created for this guide, not new Iria fields.

Check what the glossary can help you repeat

The Iria facts document a custom glossary of up to 80 entries for preferred terminology and ask users to review important results. They also document source context and RESX comments in Localization Studio. This supports preparing terminology and context; it does not prove automatic resolution of every ambiguous word.

In this case, check whether your preference applies to a sufficiently specific expression and meaning. If you cannot formulate it without contradicting the other phrase, retain the distinction as review context before adding a general equivalence. We do not promise phrase matching or an exception rule that this guide has not verified.

Review the pair after translation, rather than just the term

Compare both proposals against their intended use. “Floor 2” should still identify a building level in this example; “Assembly plant” should still name the facility. If a proposal is wrong, correct it and reconsider the preference that led you to accept it. Using the same English word consistently in both phrases is not enough.

Make a second pass with the actual context: do you mean a numbered building level, a factory or even a living plant? The final translation needs that context; the example does not set building numbering conventions for every country.

Structural checks answer a different question

Studio’s structural checks include placeholders, markup and other published constraints. Its documentation explicitly says these do not establish translation meaning or quality. A sentence can preserve its structure and still use the wrong sense. This lexical review therefore complements the JSON and RESX review without replacing it.

Do not change a human approval merely because wording looks uniform. Read the complete result and check that it conveys the function the reader needs to understand.

What to examine in other tools

DeepL describes its glossaries as preferred terminology resources and explains that it applies those preferences with contextual and grammatical understanding. Weblate documents its glossaries and how matching terms appear in its editor. These are different implementations: we do not assign their matching rules to Iria or rank translation quality. Sources consulted on 23 October 2026.

Before expanding your list, test one entry with two real uses and write down the distinction you need to preserve. Check Iria and its current download: it is a paid Windows product. Text processing is local; activation, license validation, models and updates have the connection requirements documented in its facts.