Your TMX travels; your complete translation project does not fit inside it

Move the memory; keep the project separately

TMX is used to exchange translation memory. Do not treat it as a complete Iria project backup: also retain the source resources and context needed to review the work. Another program accepting the file does not establish that every project decision arrived.

Iria documents bounded TMX 1.1, 1.4 and 1.4b import and plain-text TMX 1.4 export. It does not promise complete Level 2 interchange. Localization Studio works with JSON and RESX resources; segment memory and application resources have different purposes.

Prepare a sample before moving everything

This is a proposed review exercise, not an Iria export or a completed compatibility test:

• One example resource has source “Save changes” and translation “Guardar cambios.”
• Another has source “Discard changes” and translation “Descartar cambios.”
• Keep the source file, target language and explanation of where each action appears separately.

In the receiving program, check whether the sample segments arrive in the correct language direction with the expected text. If they contained formatting or extra information, inspect what survived. Plain-text export is not a promise to preserve inline tags or every metadata field.

Do not replace your original memory with the sample. The exercise is intended to reveal what you can reuse and what needs review before deciding on a larger migration.

“It was already translated” is not enough

An Iria project-memory match requires source-file identity, exact source text, context, glossary, language direction and access-key contract. A similar phrase in another file does not establish automatic reuse.

The example does not impose translations on every product. “Save” as a button and “saved” as a state need their own context. Review wording where it will be used, even when the memory exchange reports no errors.

Studio’s translation-import workflow previews conflicts before mutation and requires explicit replacement decisions. Do not turn that documented workflow into a claim that any TMX file will be applied without review.

Before moving the memory, ask whether you will use it as a reference or incorporate translations into the current work. Keep that decision with the sample.

Check each tool’s exchange options

Consulted on 24 October 2026, the OmegaT manual describes project and reference memories, while Trados documentation explains import, overwrite and plain-text options. They help frame questions; they do not certify interchange between those products and Iria.

Read the Localization Studio walkthrough and current Iria downloads. Iria is a paid Windows product. Retain originals and review a sample at its destination before calling a migration complete. Structural checks do not certify meaning.