Another translation arrived: choose what to keep before importing

Read both versions before choosing

When an imported translation differs from the local one, check what the string means in context before deciding whether to replace it. Receiving a file today does not establish that its translation matches the current source.

Iria’s Localization Studio documents conflict previews before data mutation and explicit replacement decisions. Use that review to inspect differences without treating an import as automatic linguistic approval.

A small-looking conflict

Authored example: a button has the source “Save draft” and context “Save the draft without submitting the application”. Your local Spanish translation is “Guardar borrador”. The received file proposes “Guardar cambios”.

Both may sound natural, but the second no longer names the draft. In this example you want that distinction preserved. Before accepting replacement, ask whether the source or the button’s purpose changed. If they remain as described, retain or correct the translation to express the draft; do not justify the new phrase just by its date.

If another imported entry has no conflict, review its own meaning. Approving one button does not establish the correctness of every other string.

Prepare a comparison for each entry

1. Identify the project, file, key and language under review without mixing in entries from another file.
2. Read the current source and context alongside the local and received translations.
3. Record why you would retain, correct or replace it: for example, “preserve the mention of the draft”.
4. Confirm only decisions you have reviewed and check the resulting state before export.

These are human review steps, not button names or an observed click sequence. If you cannot explain your preference, keep the decision pending while checking the actual context.

Structure and meaning need different checks

Studio supports multi-file JSON or RESX projects and structural checks for placeholders, markup, ICU/plurals and access keys. Passing a structural check does not determine whether “draft” belonged in that sentence. New projects require human approval before export by default: there is no need to disable that control to resolve an import.

Do not transfer import rules from another tool to Iria either. This guide is limited to the preview and explicit replacement documented in Localization Studio.

Iria is a paid Windows x64 translator with local translation; activation, downloads and license checks use the network. Check current product facts and official downloads. For your next file, begin with a conflict whose meaning you can check against its source.