The button says the same thing: its approval does not travel to another file

Identical text is only part of the match

Two resources saying Open is not enough to reuse an approval as exact Iria memory. Localization Studio scopes memory to the project and source-file identity, alongside source text, context, glossary, language direction and access-key contract. Check the target resource before assuming it is already approved.

The aim is not to blindly retranslate every repeated string. It is to distinguish a useful candidate from a match satisfying all documented conditions.

Two files, two context questions

This original example uses fictional JSON resources:

Conceptual file A: menu.json

{ "open": "Open" }

Conceptual file B: status.json

{ "open": "Open" }

In A, verified project context says this is a command to open a file. In B, it describes an issue that remains open. Depending on the real context, the English string may call for Spanish “Abrir” and “Abierta” respectively.

These are proposed translations for those meanings, not recorded model output or a universal rule for Open. If the second resource were also an opening command, the same translation might fit; the difference in file identity would still remain.

Review the resource before approving it

Locate the destination file and string in the project. Check the current source, language direction, context and glossary before accepting a proposal. When correcting a translation, save the decision for the resource you are reviewing; shared letters do not approve every other occurrence.

New projects require human approval before export by default. An optional policy can automatically accept current drafts passing supported checks. That acceptance is recorded separately and does not create human correction memory. “Exportable under that policy” does not mean “linguistically reviewed by a person.”

Another file is not a whole imported project

Exact project memory and TMX interchange have different scopes. When moving work, consult the TMX guide rather than assuming memory transports all approvals and contexts.

The Studio documentation describes local multi-file JSON/RESX projects, structural checks and review. Those checks alone do not certify that “Abrir” or “Abierta” is correct for your interface.

Iria is a paid Windows x64 desktop translator. Check current downloads and terms before installation. Translation is local; licensing, models and updates use the network in the documented cases. No linguistic superiority or universal reuse is claimed: start with a concrete destination resource and check why its translation belongs there.