Translate Ayuda, preserve the link: review HTML inside JSON

If a resource contract fixes a link destination at /help, translating “Ayuda” as “Help” does not authorize changing that destination. Review the text a person reads and the attribute that opens the page separately, even when both live inside one JSON string.

Iria includes a JSON/RESX Localization Studio with markup checks. Structural checks do not establish translation meaning on their own. The resource below is an original example, not an observed Iria output or a route you need to add to your project.

Decide what may change

Imagine a team maintains a help page at /help in every language. That is this example’s contract. Visible text is translated; the destination and helpLink key stay unchanged. Another project may localize routes, in which case its contract takes precedence over this choice.

Here is the source resource as valid JSON:

{"helpLink": "<a href=\"/help\">Ayuda</a>"}

The backslashes before the inner quotation marks allow those marks to live inside the JSON string. They are not visitor-facing text. If your project represents links differently, follow its format instead of copying this resource unchanged.

A translation that respects the contract

For this example, our authored English version is:

{"helpLink": "<a href=\"/help\">Help</a>"}

The visible letters between the opening and closing link tags changed. The key helpLink, the href attribute, its /help value and the markup remain. Changing /help to /ayuda might leave perfectly parseable JSON while still violating the agreed destination.

Preserving the address is not enough if a closing tag disappears or the resource’s quotation marks break. These are separate questions: can the JSON be read, does the markup follow project rules, is the destination agreed, and does the visible text communicate the right action?

Bring context into the review

Before translating in Studio, supply available context such as: “Link to the help centre; preserve /help in every language.” Use the context or comment appropriate to the resource. Do not call a route fixed if the team changes it by language.

Then review structural checks, visible wording and the link in the destination application. A check with no errors does not establish that the destination exists or that the wording is suitable. Functional validation belongs to the consuming project; this guide does not perform it for you.

Where Iria fits

The official fact sheet documents local multi-file JSON/RESX projects with context, RESX comments, glossary and review. Checks cover elements including placeholders, markup and plural branches; they do not certify quality or meaning. New projects require human approval before export by default under the documented policy.

Iria is a paid Windows product with local translation; activation, validation and model downloads require network access under the conditions described in its fact sheet. See the product and current installers. Before exporting your link, settle both decisions: what people should read and which destination it should open.