Two identical keys: parsing JSON does not prove both messages survived

Check names before reviewing translations

In this invented example, a file contains two members named title within the same object. A parser accepting it does not establish that both messages remain available to the consuming program. Review the original before translating: if they are distinct messages, they need distinct identities agreed with that application.

This is not a claim that Iria automatically detects duplicate keys. It is an external check of the input you intend to localize.

A small reproducible example

Consider this JSON text:

{"title":"Open the folder","title":"Close the window"}

In JavaScript, JSON.parse produces an object with one title property whose value is Close the window. Two separate title properties are not available as independent messages. Check that specific behavior with:

const text = '{"title":"Open the folder","title":"Close the window"}';
const value = JSON.parse(text);
console.log(Object.keys(value)); // ["title"]
console.log(value.title); // Close the window

Do not generalize this result to every JSON consumer. RFC 8259, section 4 recommends unique names within an object and warns that duplicate-name behavior differs: some consumers retain the last value, others fail or expose all pairs.

Repair the contract before translating values

If both messages are required, one alternative for this example is:

{"open_folder_title":"Open the folder","close_window_title":"Close the window"}

This is not a repair to paste into a real application blindly. Code looking up title also needs adapting to the new keys. Preserve the original, identify the screen using each message and agree on keys with the project maintainer before replacing the file.

Once that contract is resolved, translate the values while keeping the agreed keys. In Spanish, the example becomes “Abrir la carpeta” and “Cerrar la ventana.” Then check that each screen consumes the correct message; two different keys alone do not establish working integration.

Use Studio within its documented scope

The Iria documentation describes local JSON/RESX projects, context, translation memory and review before export. Structural checks do not establish translation meaning or quality. We also do not treat them as proof that every message survived input containing duplicate names.

Keep the source copy, resolve the ambiguity and review exported messages in the destination application. Iria is paid Windows software with local translation and network license-validation requirements. Consult its current guide and download before preparing your workflow.