Mixed-Width Whitespace Check
The mixed-width whitespace check flags half-width spaces that appear inside continuous Japanese text where they are likely accidental.
Examples
{ "notice": "Settings saved", "cta": "Continue" }{ "notice": "設定 を保存しました", "cta": "次 へ" }notice: half-width space inside Japanese text run cta: half-width space splits a Japanese word-like label
The string may render with awkward spacing or line breaks, and reviewers may miss it when scanning JSON rather than UI.
What LocaleQA checks
LocaleQA looks for half-width spaces embedded in continuous Japanese text runs, such as 設定 を保存しました, where the space is often a copy/paste or editing artifact.
It is separate from general internal whitespace because Japanese text has different spacing conventions from English. A normal-looking English space can be visually disruptive in Japanese UI copy.
What appears in the report
The report shows the affected path and target string so reviewers can decide whether the space is intentional. PMs and vendors can fix obvious spacing artifacts before screenshots or client review.
The rule does not remove spaces automatically. It keeps the scan deterministic and leaves style decisions to the project owner.
When to keep or skip this check
Spaces around Latin product names, numbers, symbols, variables, or quoted UI labels may be intentional in Japanese copy. For example, Pro プラン or Version 2 may be correct depending on the style guide.
Disable this rule for projects whose Japanese style guide intentionally uses spaces in Japanese text. Keep it enabled for compact UI labels, mobile strings, and vendor deliveries where stray half-width spaces are a common cleanup issue.
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.
For Japanese projects, width, spacing, encoding, and katakana style often belong to the client style guide. Keep this check on when those conventions matter, and leave it off for projects where the pattern is not part of review.