Leading Whitespace Check
The leading whitespace check flags strings where target leading whitespace differs from source.
Examples
{ "indent": " Item" }
{ "indent": "Item" }Why this matters
Leading whitespace can be meaningful in CLI output, plain text email, Markdown-like text, or tests that compare exact strings.
How the check works
LocaleQA counts leading whitespace on matching source and target strings and reports drift.
Where judgment still matters
Not every leading-space change is wrong. The report identifies differences that should be reviewed before release.
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.