“Open” stayed the same; its meaning changed: review the RESX comment
AI-generated image; illustrative scene.
A source string can still say “Open” while needing a different translation. If it once labeled a button action and now describes a door’s state, Spanish “Abrir” and “Abierta” serve different purposes. Checking only that the English text matches misses the decisive question: what does it mean here?
This is an invented RESX review example. It does not describe an observed Iria defect or text generated by its model.
Keep the word and change the question
Imagine this working record, with the same identifier and source text across revisions:
| Revision | Source | Developer comment | Proposed Spanish for this example |
|---|---|---|---|
| A | Open | Button action that opens a door | Abrir |
| B | Open | State of a door that is open | Abierta |
The second comment does not prove that the rest of your interface has been adapted. Before approval, check that the component really shows a state, which noun it describes and whether the proposed translation fits. If development still uses an action button, the comment and implementation conflict: resolve that question with whoever owns the resource.
Check where context comes from
Iria’s facts document that new RESX entries can inherit their complete developer comment as context. If effective inherited context changes, previous approval is revoked and the draft’s old context is retained. A differing manual override, including an empty override, is preserved.
Review these cases separately:
- Inherited context: compare the new comment with the previous draft context. Prior approval is no longer sufficient when effective inherited context changes. Review the meaning before approving again.
- A differing manual override: check whether it remains intentional. Do not assume a new comment replaced it; an empty override can also be a retained decision.
This is not a proposal to remove overrides in bulk. In our case, “use as a verb” would be manual context worth reviewing if the interface now displays a state. Make that decision explicitly for the relevant entry.
Separate memory, structure and meaning
Studio’s exact memory depends on source-file identity, exact source text, context, glossary, language direction and the access-key contract. Two visually identical source strings are not enough to establish that an approval should be reused.
Placeholder, markup, ICU/plural, quantity, limit and access-key checks are structural. Passing them does not establish that “Abrir” correctly describes an open door’s state. Here, the meaning check remains human: action or state, which object, and what grammatical gender and number does the phrase need?
New projects default to human approval before export. Keep a review of the entry and context being approved; a technically possible export is not validation of meaning.
Check how each tool presents context
Weblate documents translation management and review; Crowdin’s editor places context and comments alongside strings. Read their own workflows when comparing tools: these links do not establish identical RESX inheritance or memory conditions to Iria. References checked on 23 October 2026.
To follow this case in Iria, read Localization Studio and check the current downloads. It is a paid Windows x64 product. Translation runs locally, while licensing and model downloads require a network. First decide what “Open” means in your resource; then review the translation you will deliver.