All rules

並びに or 若しくは with no inner level

connective-hierarchyon by defaultJapanese

並びに in a sentence with no 及び, or 若しくは in one with no 又は

Example

Flagged
申請書並びに添付書類を提出する。
What chaff prints
1:4 「並びに」の文に、段の組になる語がありません(一段なら「及び」)
Fixed
申請書及び添付書類を提出する。
What chaff prints
no finding

How to fix

For a one-level list, write 及び for 並びに and 又は for 若しくは. If the list has two levels, write the other level's word too.

Why it matters

Japanese statutes and official writing join lists by level. A one-level list uses 及び (and) or 又は (or); only a two-level list uses 並びに for the outer "and" (A及びB並びにC) and 若しくは for the inner "or" (A若しくはB又はC). 並びに in a sentence with no 及び, or 若しくは in one with no 又は, uses the word for a level the sentence does not have, and the reader looks for the other level.

What it does not flag

Only in Japanese documents. The kana forms ならびに and もしくは, which plain writing also uses for a one-level list, are not read. A clause holding 及び, および, 又は or または is read as having the other level (a condition clause ending in ときは、 and the main clause are separate clauses). A phrase inside 「」 or 『』 quotes half of a list and is not read. Only a word joining two nouns is read (文字の並びに, 正しい並びに and 縦並びに, the noun 並び with に, are not).

Turning it off or relaxing it

Silence this one spot (in the document)
<!-- stet: connective-hierarchy — reason -->
Relax it for the team (the reason is kept as a comment in chaff.yaml)
npx chaffjs relax connective-hierarchy --why "reason"
Turn it off for the team (chaff.yaml)
rules: connective-hierarchy: off
Technical details
Layer
L2
Status
stable
Severity
warning
Languages
ja
Suited to
business, technical, blog, 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).

stricterror
normalwarning
relaxedinfo

This rule has no limit to count to. A level sets how a finding is marked: relaxed keeps the finding and marks it a step lower.

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
Turned off by the genre in
literature/fiction, literature/essay, literature/poetry, literature/play, speech/address, speech/transcript

Genres

Message

"{written}" with no other level of the list in the sentence (a one-level list uses "{usual}")

Rewrite depth (chaff fix-plan --depth): light — words and sentences; the structure and the voice stay

Sources

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