Tag Preservation Check
The tag check verifies that inline markup-style tokens are preserved where source and target strings share a path.
Examples
{ "terms": "Read <link>terms</link>" }
{ "terms": "<link>利用規約を読む" }Why this matters
Inline tags often represent links, emphasis, components, or markup. Missing or malformed tags can break rendering or strip expected UI behavior.
How the check works
LocaleQA extracts supported tag-like tokens from source and target strings and compares preservation on matching JSON paths.
Where judgment still matters
LocaleQA checks tag preservation. It does not parse application-specific rendering semantics beyond the deterministic token comparison.
How to use the finding
LocaleQA reports the affected JSON path, the source and target values involved, and the rule that triggered the finding. Developers, localization PMs, vendors, and QA reviewers can use that as a specific file-level item to fix, approve, or discuss before release.
Some findings are valid exceptions. A migration file, documented style choice, or locale-specific convention may explain the difference. In those cases, teams can leave the string as-is or disable the check for that scan.
LocaleQA is JSON file QA. It does not judge wording or rewrite translations; it surfaces the file issue so the responsible owner can decide the right fix.