LocaleQAEarly access
Pricing
Checks

Deterministic localization QA checks for JSON files

LocaleQA compares source and target JSON localization files with fixed rules. The checks focus on file issues before release, not translation generation or linguistic review.

Run a scanPricing

Key structure

Key structure checks keep source and target JSON in sync before files are merged, delivered, or handed to QA.

Missing Keys Check
The missing keys check flags source string paths that the target JSON file does not provide.
Extra Keys Check
The extra keys check flags target string paths that do not exist in the source JSON file.

Runtime tokens

Runtime token checks catch placeholders and inline tags that can break interpolation, links, formatting, or component rendering even when the JSON syntax is valid.

Placeholder Integrity Check
The placeholder check verifies that dynamic tokens remain intact between source and target strings.
Tag Preservation Check
The tag check verifies that inline markup-style tokens are preserved where source and target strings share a path.
Placeholder Full-Width Mutation Check
The placeholder full-width mutation check catches runtime tokens whose ASCII syntax was accidentally converted into full-width Japanese characters.

Whitespace and formatting

Whitespace checks cover strings where spaces, tabs, or line endings are part of the output, such as emails, generated text, snapshots, and CLI messages.

Leading Whitespace Check
The leading whitespace check flags strings where target leading whitespace differs from source.
Trailing Whitespace Check
The trailing whitespace check catches target strings where ending spaces or tabs no longer match the source string.
Line Endings Check
The line endings check flags localized strings where newline style changes between source and target.
Internal Whitespace Check
The internal whitespace check flags changes to repeated spaces or tabs inside a string, excluding leading and trailing whitespace.
Mixed-Width Whitespace Check
The mixed-width whitespace check flags half-width spaces that appear inside continuous Japanese text where they are likely accidental.

Untranslated content

Same-as-source checks create a review list for strings that may have been missed. They do not decide whether an unchanged brand name or code is wrong.

Untranslated Same-as-Source Check
The same-as-source check creates a review list for target strings that still match source text on the same JSON path.

Glossary and profile rules

Glossary and profile checks enforce agreed terminology and locale conventions without turning the scan into translation review.

Glossary Exact Match Check
The glossary exact match check verifies required terminology when a configured source term appears in a source string.
Katakana Style Mismatch Check
The katakana style mismatch check flags long-vowel style differences against glossary target terms in Japanese localization files.

Japanese-specific profile checks

Japanese profile checks cover problems that show up in real Japanese files: full-width token changes, mixed character width, encoding damage, spacing artifacts, and katakana style drift.

Encoding Validation Check
The encoding validation check flags file-level encoding risks that can appear when JSON translation files move between tools, vendors, and editors.
Placeholder Full-Width Mutation Check
The placeholder full-width mutation check catches runtime tokens whose ASCII syntax was accidentally converted into full-width Japanese characters.
Script Inconsistency Check
The script inconsistency check flags suspicious mixtures of half-width and full-width alphanumeric or punctuation characters in Japanese localized strings.
Mixed-Width Whitespace Check
The mixed-width whitespace check flags half-width spaces that appear inside continuous Japanese text where they are likely accidental.
Katakana Style Mismatch Check
The katakana style mismatch check flags long-vowel style differences against glossary target terms in Japanese localization files.