All rules

Stray space inside a phrase

stray-spaceon by default (info)Japanese

A stray space inside a Japanese phrase, usually left over from retyping

Example

Flagged
資料を確認しました。担当者が払いました。会議で決めました。見積もりを 送りました。
What chaff prints
1:35 助詞「を」と「送り」のあいだに空白があります(この文書は文節のあいだをふつう詰めて書く。4 箇所のうち 1 箇所が空いている)
Fixed
資料を確認しました。担当者が払いました。会議で決めました。見積もりを送りました。
What chaff prints
no finding

How to fix

Delete the space. If the document spaces its phrases on purpose, do so throughout.

Why it matters

A space inside what reads as one phrase in Japanese (こころさんが 払った, 確認 しました) makes the reader wonder whether the phrase breaks there. It is typically left over from retyping or pasting and is easy to miss by eye. chaff counts two kinds of joint separately, after a particle (が 払った, the break between phrases) and before a word that cannot start a phrase (a particle as in アプリ が, an auxiliary as in 行き ます, する after a noun as in 確認 しました, or kana cut off from its word as in 例 えば). Spacing every phrase (分かち書き, as in text for children or for learners of Japanese) is a way of writing, so chaff does not decide which is right; it reports the spaces only when the document spaces less often than it does not. A space between two nouns (a label and its value as in 担当 田中, a name as in 赤坂 文弥, a compound as in サムネイル キャッシュ) is often written on purpose and is not counted. Neither are lines that do not end with a full stop (verse, labels and values, table-like lines), headings, tables, a full-width indent at the start of a line, the space after an item mark at the start of a line (イ ), a Markdown line break, the inside of a quotation in 「」 or 『』, or a boundary with Latin letters or digits (latin-spacing looks at those).

What it does not flag

Spaces between two nouns, lines that do not end with a full stop, headings, tables, quotations and boundaries with Latin letters are not checked. A document that spaces every phrase on purpose is not reported.

Turning it off or relaxing it

Silence this one spot (in the document)
<!-- stet: stray-space — reason -->
Relax it for the team (the reason is kept as a comment in chaff.yaml)
npx chaffjs relax stray-space --why "reason"
Turn it off for the team (chaff.yaml)
rules: stray-space: off
Technical details
Layer
L3
Status
stable
Severity
info
Languages
ja
Suited to
business, blog, technical, legal, docs, academic, literature, speech
Reads from the document
pos

Levels

Set a level for this rule under rules in chaff.yaml. With nothing set, it runs at the level its genre gives it (see By genre below).

strictreported once 1 spaces go against the document's habit
normalreported once 1 spaces go against the document's habit
relaxedreported once 3 spaces go against the document's habit

By genre

Runs by default in
technical/spec, technical/readme, blog/tech, blog/essay, blog/owned-media, business/proposal, business/report, business/email, business/press-release, business/meeting-notes, legal/contract, legal/statute, legal/judgment, legal/patent, docs/manual, docs/faq, docs/glossary, academic/paper, literature/fiction, literature/essay, literature/poetry, literature/play, speech/address, speech/transcript

Genres

Message

Space between "{before}" and "{after}" ({count} of {of} in this document are spaced)

Space after the particle "{before}" before "{after}" (this document usually writes phrases without a space; {count} of {of} are spaced)

"{before}" and "{after}" read as one phrase but are separated by a space ({count} of {of} are spaced)

This page is built from the rule's definition file:packages/chaff/rules/stray-space.yaml