Checks

Deterministic QA checks for web, mobile, and Java localization files

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

Key structure

Structure checks keep matching paths, resource names, and translation units in sync before files are merged, delivered, or handed to QA.

Runtime tokens

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

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.

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.

Glossary and profile rules

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

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.