Translate “Open”, keep “open_button”: they are not the same text

The identifier finds the resource; the value addresses the user

In our JSON example, translate the value “Open” to “Abrir” and keep the key “open_button”. Our hypothetical app looks up that exact key for a button label. Renaming it to “boton_abrir” may leave valid JSON that no longer matches what the app requests.

This is an authored example with an explicit contract. It does not mean every JSON file must be translated identically or that Iria automatically repairs changed resource identifiers.

One resource, two different results

Suppose the source file contains {"open_button":"Open"} and the app’s code requests exactly open_button. Our Spanish version is {"open_button":"Abrir"}. The key still matches; the visible value changes.

Compare {"boton_abrir":"Abrir"}. Its braces and quotes may be valid, but our hypothetical program does not request that new identifier. A syntax validator does not inherently know the app’s contract.

Do not choose “Abierto” for “Open” without checking context either. We have explicitly defined a button action. A status label would need different context. The key is a clue, not a replacement for a developer’s explanation.

Review structure and meaning separately

1. Structure: compare the keys before and after. Our example must retain open_button exactly. Do not translate an identifier merely because it resembles English words.
2. Meaning: confirm where the value appears and which action it promises. We chose “Abrir” for our button.
3. Destination: test your localized version in your own app and check that it finds the intended resource. This guide does not claim to have run that app or tested its interface.

If a team deliberately renames a key, coordinate the contract change with code and other languages. Do not bury it inside a translation correction.

Where Localization Studio fits

Iria translates selected text and localizes JSON/RESX on Windows. Its official facts document multi-file projects, a glossary, context, translation memory and structural checks. Structural checks do not establish translation meaning or quality. Use context and human review for your resource contract; this example does not establish support for every schema or file type.

Weblate and Crowdin were consulted on 25 October 2026 as other localization editors. Their documentation does not establish equivalent Iria behaviour.

Before choosing the tool

Iria is available as a paid Windows x64 product. Translation is processed locally, with internet-based licence activation and validation; the initial model download also requires a connection. Check the current download and licence terms before buying. Start your first review with the minimal resource: same key, translated value and checked context.