chaffjs 0.19.0 → 0.21.0

package/rules/modal-conflict.yaml

@@ -1,6 +1,6 @@
 id: modal-conflict
 layer: L3
-status: experimental
+status: stable
 how_to_find: modal-conflict
 requires: [structure, pos]
 severity: warning
@@ -80,6 +80,7 @@ not_flagged:
   ja: 中身の語（名詞・動詞・形容詞）がまったく同じ二つの文だけを比べます。様相の語を二つ以上持つ文と、中身の語が一つしか無い文は見ません。「しなければならない」と「することができる」は食い違いと見ません。
   en: Only two sentences with exactly the same content words (nouns, verbs, adjectives) are compared. A sentence with two or more modal markers, or with fewer than two content words, is not checked. "Must" and "may" are not counted as a conflict.
 rewrite:
+  depth: light
   ja:
     direction: どちらの文が正しいかを書き手に確かめてください。両方が正しいなら、それぞれの条件や例外を本文から書き足して範囲を分けます。本文に条件が無ければ作らず、書き手に聞きます。
     pairs:

package/rules/name-variant.yaml

@@ -1,9 +1,9 @@
 id: name-variant
 layer: L3
-status: experimental
+status: stable
 how_to_find: name-variant
 requires: [pos]
-severity: warning
+severity: info
 
 name:
   ja: 同じ名前の書き分け
@@ -40,7 +40,7 @@ placeholders:
     ja: 別の形
     en: another form
 
-levels: { strict: error, normal: warning, relaxed: info }
+levels: { strict: warning, normal: info, relaxed: info }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
@@ -64,6 +64,7 @@ not_flagged:
   ja: 品詞解析が固有名詞と読んだ語だけを見ます。大文字だけの名前（ACME INC、NASA）は見ません。一字違いの英字の名前は、6 字以上で、多いほうが二度以上、少ないほうが一度だけのときに限ります（Iran と Iraq は別の名前）。
   en: Only words the tagger reads as proper nouns are checked. Names in capitals only (ACME INC, NASA) are left out. Names one letter apart are reported only when six letters or longer, with the usual form used at least twice and the other once (Iran and Iraq are different names).
 rewrite:
+  depth: light
   ja:
     direction: 少ないほうの形を、多いほうの形に替えてください。どちらが正しいか本文から分からなければ、書き手に聞きます。別の人や会社なら替えません。
     pairs:

package/rules/ngram-repetition.yaml

@@ -25,6 +25,11 @@ how_to_fix:
 levels: { strict: 3, normal: 5, relaxed: 9 }
 
 use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive (shall be deemed), and joins long noun compounds (個人情報取扱事業者). This rule would only flag the form."
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+  docs/glossary: "A reader looks up one entry and reads only that. A definition is a noun phrase (風の吹いてくる方向。), and sibling entries share one wording on purpose (Portion of labor productivity change attributed to …), which no reader sees twice."
+  speech/transcript: "A transcript records what was said: its sentences, repeats and register are the speaker's, not the writer's to fix."
 
 group: readability
 summary:

package/rules/no-doubled-joshi.yaml

@@ -5,7 +5,7 @@ how_to_find: doubled-particle
 word_list: nesting-particle
 requires: [pos]
 languages: [ja]
-severity: warning
+severity: info
 
 name:
   ja: 同じ助詞が入れ子で続いている
@@ -26,6 +26,10 @@ how_to_fix:
 levels: { strict: 1, normal: 2, relaxed: 3 }
 
 use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive (shall be deemed), and joins long noun compounds (個人情報取扱事業者). This rule would only flag the form."
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+  speech/transcript: "A transcript records what was said: its sentences, repeats and register are the speaker's, not the writer's to fix."
 sources: [yamamoto-cheng-2015]
 
 group: readability

package/rules/no-em-dash.yaml

@@ -1,6 +1,6 @@
 id: no-em-dash
 layer: L1
-status: experimental
+status: stable
 how_to_find: dash-density
 
 # 記号の許容度は言語で違う。英語では正当な用法が多く、日本語の組版では扱いが難しい。spec §12.4。
@@ -30,6 +30,8 @@ levels:
   en: { strict: 3, normal: 8, relaxed: 20 }
 
 use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
 sources: [freeburg-2026]
 
 group: ai-tells
@@ -57,6 +59,7 @@ level_meaning:
   ja: 1000 字あたりダッシュ {limit} 個まで
   en: up to {limit} dashes per 1000 words
 rewrite:
+  depth: light
   ja:
     direction: 挟み込みのダッシュは括弧に、言い換えや補足のダッシュは読点に替えるか、二文に分けてください。
     pairs:

package/rules/no-lead.yaml

@@ -0,0 +1,100 @@
+id: no-lead
+layer: L1
+status: stable
+how_to_find: no-lead
+requires: [pos]
+severity: info
+
+name:
+  ja: 題の後の段落が題を言い直しているだけ
+  en: The lead only restates the title
+
+why:
+  ja: 題のすぐ後の段落（リード）は、読者がこの先を読むかを決める所です。そこが「この記事では〇〇について説明します」のように題を言い直すだけだと、読者は何も受け取らないまま本文へ進みます。chaff は、リードが題の文字の並びの半分以上を繰り返し、しかも題に無い内容語（名詞・動詞・形容詞・副詞・数）をわずかしか足していないときに言います。日付や書き手の名前だけの行は題を繰り返さないので言いません。
+  en: The paragraph right under the title (the lead) is where a reader decides whether to read on. When it only restates the title ("This article explains X"), the reader gets nothing before the body starts. chaff reports a lead that repeats at least half of the title's character sequence and adds only a few content words (nouns, verbs, adjectives, adverbs, numbers) the title does not have. A line with only a date or a byline does not repeat the title, so it is not reported.
+
+message:
+  ja: 題「{title}」の後の段落は、題に無い語を {count} 個しか足していません
+  en: 'The paragraph after the title "{title}" adds only {count} {count|word|words} the title does not have'
+
+how_to_fix:
+  ja: リードには、題だけでは分からないこと（結論、数字、誰に関係するか、いつからか）を書いてください。言うことが無ければ、リードを消して本文から始めます。
+  en: Put in the lead what the title alone does not say (the conclusion, a figure, who it affects, from when). If there is nothing to add, drop the lead and start with the body.
+
+# 題に無い内容語がこの数より少ないと指摘する。
+levels: { strict: 6, normal: 5, relaxed: 3 }
+
+use_for: [blog, business, technical, docs, academic, legal, literature, speech]
+off_for:
+  legal: "A statute or contract opens with its first article, and its titles are formal names."
+  literature: "A story or poem chooses its own opening and its own title."
+  speech: "An address or a transcript is titled by occasion (第221回国会における…演説) and opens as spoken."
+
+group: structure
+summary:
+  ja: 題のすぐ後の段落が、題を言い直すだけで何も足していない所
+  en: A first paragraph under the title that only says the title again
+example:
+  ja:
+    config: { genre: blog/tech }
+    before: |
+      # 新しい在庫システム
+
+      この記事では、新しい在庫システムについて紹介します。
+    after: |
+      # 新しい在庫システム
+
+      来月から全店の在庫を一つの画面で数えられるようになり、棚卸しは半日で終わります。
+  en:
+    config: { genre: blog/tech }
+    before: |
+      # The new inventory system
+
+      This article introduces the new inventory system.
+    after: |
+      # The new inventory system
+
+      From next month every store counts its stock on one screen, and a stocktake takes half a day.
+
+not_flagged:
+  ja: 題の文字の並びの半分以上を繰り返していない段落（日付、書き手の名前、別の話題で始まるリード）は言いません。題のすぐ下が箇条書き・表・画像なら、リードが無いものとして見ません。題（最初の # 見出し）だけを見ます。法務・文学・話し言葉のジャンルでは見ません。
+  en: A paragraph that repeats less than half of the title's character sequence (a date, a byline, a lead on another point) is not reported. When a list, a table or an image comes right under the title, there is no lead to check. Only the title (the first top-level heading) is checked. Legal, literary and speech genres do not run this rule.
+level_meaning:
+  ja: 題に無い内容語が {limit} 個より少ないとき指摘
+  en: reported when the lead adds fewer than {limit} content words the title does not have
+rewrite:
+  depth: structure
+  ja:
+    direction: リードを、題だけでは分からないことから書き直してください。結論・数字・対象・時期のうち、本文にあるものを一つか二つ前に出します。題の語を繰り返して「〜について説明します」と予告する文は消します。
+    pairs:
+      - before: |
+          この記事では、新しい在庫システムについて紹介します。
+        after: |
+          来月から全店の在庫を一つの画面で数えられるようになり、棚卸しは半日で終わります。
+      - before: |
+          本ページでは、窓口の受付時間の変更についてお知らせします。
+        after: |
+          4月1日から、窓口の受付は平日の午前9時から午後4時までになります。
+    keep:
+      - 本文にある数字・日付・名前
+      - 題の言葉づかい
+    avoid:
+      - 本文に無い事実をリードに足す
+      - 題をもう一度別の言葉で言い直す
+  en:
+    direction: Rewrite the lead from what the title alone does not tell the reader. Bring forward one or two of the conclusion, a figure, who it affects and when, taken from the body. Cut a sentence that repeats the title to announce what comes next.
+    pairs:
+      - before: |
+          This article introduces the new inventory system.
+        after: |
+          From next month every store counts its stock on one screen, and a stocktake takes half a day.
+      - before: |
+          This page explains the change to our office hours.
+        after: |
+          From April 1 the front desk is open 9 a.m. to 4 p.m. on weekdays.
+    keep:
+      - the figures, dates and names the body gives
+      - the title's wording
+    avoid:
+      - adding to the lead a fact the body does not have
+      - saying the title again in other words

package/rules/no-mixed-desumasu.yaml

@@ -1,12 +1,12 @@
 id: no-mixed-desumasu
 layer: L3
-status: experimental
+status: stable
 how_to_find: sentence-ending
 word_list: polite-ending
 extra_word_lists: [neutral-ending]
 requires: [pos]
 languages: [ja]
-severity: warning
+severity: info
 
 name:
   ja: 文末の調子が混ざっている
@@ -34,6 +34,9 @@ how_to_fix:
 levels: { strict: 5, normal: 3, relaxed: 1 }
 
 use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+  speech/transcript: "A transcript records what was said: its sentences, repeats and register are the speaker's, not the writer's to fix."
 sources: [yasashii-nihongo-2020, koyobun-2022, jtf-style-guide]
 
 group: consistency

package/rules/no-nakaguro-parallel.yaml

@@ -25,6 +25,9 @@ how_to_fix:
 levels: { strict: 3, normal: 5, relaxed: 8 }
 
 use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+  speech/transcript: "A transcript records what was said: its sentences, repeats and register are the speaker's, not the writer's to fix."
 
 group: readability
 summary:

package/rules/nominalization.yaml

@@ -1,6 +1,6 @@
 id: nominalization
 layer: L3
-status: experimental
+status: stable
 how_to_find: nominalization
 # 動詞を名詞にして別の動詞に運ばせる言い方。英語は語の並び（nominalization-phrase）、日本語はサ変名詞（品詞の VerbForm=Vnoun）と、
 # その後ろの「を実施する」（nominalization-light-verb）で見る。片方しか持たない言語があるので word_list には書かない（書くと、無い言語で動かなくなる）。
@@ -34,6 +34,9 @@ placeholders:
 levels: { strict: 1, normal: 2, relaxed: 4 }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  legal: 'Legal drafting writes 「…を行う」 and "make a payment" as its register; the corpus statutes are full of them.'
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
 sources: [yasashii-nihongo-2020, plain-2011, gov-uk-clear-language, reinhart-2025]
 
 group: wording
@@ -61,6 +64,7 @@ level_meaning:
   ja: 1000 字あたり「〜を実施する」のような名詞化した動詞 {limit} 個まで
   en: up to {limit} nominalized verbs ("make a decision") per 1000 words
 rewrite:
+  depth: light
   ja:
     direction: 「〜を実施する」「〜を行う」の名詞を動詞に戻し、運び役の動詞を消してください。誰がしたのかが書かれていれば、その人を主語に残します。
     pairs:

package/rules/number-style-consistency.yaml

@@ -0,0 +1,110 @@
+id: number-style-consistency
+layer: L2
+status: stable
+how_to_find: number-style-consistency
+uses: [pos]
+severity: info
+
+name:
+  ja: 数の書き方が混ざっている
+  en: Numbers written two ways
+
+why:
+  ja: 数をどう書くか（3件か三件か、1,000 か 1000 か、10% か 10％ か 10パーセントか）は、どれでも読めます。困るのは一つの文書の中で混ざることで、読み手は違う書き方に違う意味があるのかと迷い、検索でも別の語になります。chaff はどれが正しいかを決めず、数え方の語の前の数（漢数字か算用数字か）、位取りのコンマ、百分率の書き方、英語の数（three か 3 か、10 未満と 10〜12 は別に）ごとに、文書の中で少ないほうを指摘します。
+  en: How a document writes numbers (1,000 or 1000; 10% or 10 percent; three files or 3 files) is a choice either way. What reads badly is mixing them in one document, which makes the reader wonder whether the difference means something. chaff does not decide which is right; for digit grouping, the percent unit and counts (below ten, and ten to twelve, separately, so that a style that spells out small numbers stays consistent) it points at whichever the document uses less.
+
+message:
+  ja: 「{written}」と書いています（この文書はふつう「{usual}」の書き方。{of} 箇所のうち {count} 箇所が違う）
+  en: '"{written}" here, where the document usually writes "{usual}" ({count} of {of})'
+
+messages:
+  count:
+    ja: 数え方の数を「{written}」と書いています（この文書はふつう「{usual}」の書き方。{of} 箇所のうち {count} 箇所が違う）
+    en: 'The count "{written}" here, where the document usually writes counts like "{usual}" ({count} of {of})'
+  grouping:
+    ja: 「{written}」と書いています（この文書は大きな数をふつう「{usual}」のように書きます。{of} 箇所のうち {count} 箇所が違う）
+    en: '"{written}" here, where the document usually writes large numbers like "{usual}" ({count} of {of})'
+  percent:
+    ja: 百分率を「{written}」と書いています（この文書はふつう「{usual}」の書き方。{of} 箇所のうち {count} 箇所が違う）
+    en: 'The percentage "{written}" here, where the document usually writes "{usual}" ({count} of {of})'
+  count-small:
+    ja: 数を「{written}」と書いています（この文書は 10 未満の数をふつう「{usual}」のように書きます。{of} 箇所のうち {count} 箇所が違う）
+    en: '"{written}" here, where the document usually writes numbers below ten like "{usual}" ({count} of {of})'
+  count-large:
+    ja: 数を「{written}」と書いています（この文書は 10 から 12 の数をふつう「{usual}」のように書きます。{of} 箇所のうち {count} 箇所が違う）
+    en: '"{written}" here, where the document usually writes ten to twelve like "{usual}" ({count} of {of})'
+
+how_to_fix:
+  ja: 文書の多いほうの書き方に合わせてください。チームで決めているなら、STYLE.md に書いておくと迷いません。
+  en: Match the way the rest of the document does it. If the team has decided, write it in the style guide.
+
+# 少ないほうが、その種類の数の何パーセントまでなら「混ざっている」と見るか。これを超えたら、文書が使い分けている。
+levels: { strict: 49, normal: 34, relaxed: 20 }
+
+use_for: [blog, business, technical, docs, academic, legal, literature, speech]
+off_for:
+  legal: "Drafting writes a number twice on purpose: thirty (30) days."
+  literature: "A narrator spells out numbers in dialogue and writes figures in a date."
+  speech: "Spoken numbers are transcribed as heard."
+
+group: consistency
+summary:
+  ja: 3件と三件、1,000 と 1000、10% と 10％ のように、一つの文書で数の書き方が混ざっている所
+  en: One document writing numbers two ways, such as 1,000 and 1000, 10% and 10 percent, or three files and 3 files
+
+example:
+  ja:
+    config: { genre: blog/tech }
+    before: |
+      今月の問い合わせは 12件、先月は 9件、先々月は 7件でした。うち三件は同じ内容です。
+    after: |
+      今月の問い合わせは 12件、先月は 9件、先々月は 7件でした。うち 3件は同じ内容です。
+  en:
+    config: { genre: blog/tech }
+    before: |
+      We fixed three bugs, closed four issues and merged two pull requests. The release also adds 5 tests.
+    after: |
+      We fixed three bugs, closed four issues and merged two pull requests. The release also adds five tests.
+
+not_flagged:
+  ja: 鉤括弧や引用符の中の数、注や URL を含む文、日本語の中の英文は数えません。「一つ」「一人」のような一だけの漢数字と、「万人」「千人」のような位の字だけの漢数字、「第三回」「統一」のように漢字の後ろの数、日付の日・月・年は数えません。位取りは、通貨の記号か数え方の語・単位が付いた大きな数だけを見て、年に見える 4 桁の数（2019 年）、番号（H.R. 5376）、版や電話番号は見ません。全角と半角の違いは fullwidth-alnum-consistency が見ます。法務・文学・話し言葉のジャンルでは見ません。
+  en: 'Numbers inside quotation marks, sentences with a note mark or a URL, and text in another language are not counted. A number word that opens a sentence (spelt out by every style), "one", and a number before a unit of measure (6 months, 3 miles) are not counts. Grouping is checked only for large numbers with a currency sign or a word after them; a four-digit number that looks like a year, a label number (H.R. 5376, Form 1040), versions and phone numbers are left out. Legal, literary and speech genres do not run this rule.'
+level_meaning:
+  ja: 少ないほうの書き方が、その種類の数の {limit}% 以下のとき指摘
+  en: reported when the less common style is {limit}% of its kind or less
+rewrite:
+  depth: light
+  ja:
+    direction: 少ないほうの書き方の数を、文書の多いほうの書き方に直してください。数そのものと単位は変えません。
+    pairs:
+      - before: |
+          今月の問い合わせは 12件、先月は 9件でした。うち三件は同じ内容です。
+        after: |
+          今月の問い合わせは 12件、先月は 9件でした。うち 3件は同じ内容です。
+      - before: |
+          参加費は 1,500円、資料代は 2,000円、懇親会は 3000円です。
+        after: |
+          参加費は 1,500円、資料代は 2,000円、懇親会は 3,000円です。
+    keep:
+      - 数の値と単位
+      - 引用した文の中の数
+    avoid:
+      - 多いほうの書き方を少ないほうに合わせる
+      - 数え方の語や単位を言い換える
+  en:
+    direction: Rewrite each number in the less common style the way the rest of the document writes that kind of number. Keep the value and the unit.
+    pairs:
+      - before: |
+          We fixed three bugs, closed four issues and merged two pull requests. The release also adds 5 tests.
+        after: |
+          We fixed three bugs, closed four issues and merged two pull requests. The release also adds five tests.
+      - before: |
+          Turnout rose 12% in March and 9% in April, and fell 3 percent in May.
+        after: |
+          Turnout rose 12% in March and 9% in April, and fell 3% in May.
+    keep:
+      - the value and the unit of every number
+      - numbers inside a quotation
+    avoid:
+      - changing the many numbers to match the odd one
+      - rewording the unit or the counted noun

package/rules/number-without-unit.yaml

@@ -0,0 +1,97 @@
+id: number-without-unit
+layer: L1
+status: stable
+how_to_find: number-without-unit
+severity: warning
+
+name:
+  ja: 単位の無い数
+  en: Number without its unit
+
+why:
+  ja: 表の同じ列や、同じ見出しの語（「予算：」）のほかの値には単位があるのに、一つだけ数しか書いていない所です。円なのか千円なのか、分なのか時間なのかを、読み手が推し量ることになります。
+  en: Every other value in the same table column, or under the same label ("Budget:"), carries a unit, and this one is a bare number. The reader has to guess whether it is dollars or thousands, minutes or hours.
+
+message:
+  ja: 「{value}」に単位がありません（「{name}」のほかの値には「{unit}」が付いています）
+  en: '"{value}" has no unit (the other "{name}" values carry "{unit}")'
+
+how_to_fix:
+  ja: 単位を書いてください。列のすべての値が同じ単位なら、見出しに書いて（「金額（円）」）値から外す書き方もあります。
+  en: Write the unit. If every value in a column shares it, you can move it to the header ("Amount ($)") and drop it from the values.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 同じ列や同じ見出しの語のほかの値には単位があるのに、数だけを書いた値
+  en: A bare number where the other values of the same column or label all carry one unit
+example:
+  ja:
+    before: |
+      # 費用
+
+      | 品目 | 金額 |
+      | --- | --- |
+      | 設計 | 300,000円 |
+      | 開発 | 1,200,000 |
+      | 試験 | 250,000円 |
+    after: |
+      # 費用
+
+      | 品目 | 金額 |
+      | --- | --- |
+      | 設計 | 300,000円 |
+      | 開発 | 1,200,000円 |
+      | 試験 | 250,000円 |
+  en:
+    before: |
+      # Costs
+
+      | Item | Cost |
+      | --- | --- |
+      | Train | $600 |
+      | Hotel | 960 |
+      | Taxi | $100 |
+    after: |
+      # Costs
+
+      | Item | Cost |
+      | --- | --- |
+      | Train | $600 |
+      | Hotel | $960 |
+      | Taxi | $100 |
+
+not_flagged:
+  ja: ほかの値に二つ以上、同じ一つの単位が付いているときだけ指します。単位の無い値のほうが多い列、単位が混ざる列（分と時間）、数でない値（未定）は見ません。表の見出しの単位（「金額（円）」）は読みません。
+  en: Reported only when at least two other values carry one and the same unit. A column where bare numbers are the majority, one that mixes units (minutes and hours), and values that are not numbers (TBD) are not checked. A unit written in the header ("Amount ($)") is not read.
+rewrite:
+  depth: light
+  ja:
+    direction: 指摘された数に、同じ列や同じ見出しの語のほかの値と同じ単位を付けてください。単位が違うはずなら、作らずに書き手に聞きます。
+    pairs:
+      - before: "| 開発 | 1,200,000 |"
+        after: "| 開発 | 1,200,000円 |"
+      - before: "- 所要時間：45"
+        after: "- 所要時間：45分"
+    keep:
+      - 数そのもの
+      - ほかの値と、列の並び
+    avoid:
+      - 単位に合わせて数を換算する
+      - 違う単位を推して書く（千円の列に円）
+  en:
+    direction: Give the bare number the unit the other values in its column or under its label carry. If it should be a different unit, do not guess; ask the writer.
+    pairs:
+      - before: "- Train: 120"
+        after: "- Train: $120"
+      - before: "| Build | 1,200,000 |"
+        after: "| Build | $1,200,000 |"
+    keep:
+      - the number itself
+      - the other values and the order of the columns
+    avoid:
+      - converting the number to match a unit
+      - guessing a different unit (thousands in a column of dollars)

package/rules/numbering-gap.yaml

@@ -1,6 +1,6 @@
 id: numbering-gap
 layer: L3
-status: experimental
+status: stable
 how_to_find: numbering-gap
 requires: [structure]
 severity: error

package/rules/one-sentence-paragraph-run.yaml

@@ -0,0 +1,99 @@
+id: one-sentence-paragraph-run
+layer: L3
+status: stable
+how_to_find: one-sentence-paragraph-run
+severity: info
+
+name:
+  ja: 一文だけの段落が続いている
+  en: Run of one-sentence paragraphs
+
+why:
+  ja: 段落は、一つの話題にまとまった文の組です。一文ごとに段落を分けると、どの文とどの文が同じ話なのかが見えなくなり、読み手は文の関係を自分で組み立てることになります。一文の段落は強調として効きますが、続くと効かなくなります。見出し・箇条書き・表・コードを挟んだ所で数え直します。
+  en: A paragraph groups the sentences that belong to one point. Setting every sentence apart as its own paragraph hides which sentences go together, and leaves the reader to work out how they relate. A one-sentence paragraph works as emphasis; a run of them does not. A heading, a list, a table or code between paragraphs starts the count again.
+
+message:
+  ja: 一文だけの段落が {count} 個続いています（{limit} 個まで）
+  en: "{count} one-sentence paragraphs in a row (limit {limit})"
+
+how_to_fix:
+  ja: 同じ話の文を一つの段落にまとめてください。並べたい項目なら箇条書きにします。
+  en: Join the sentences that make one point into one paragraph. If they are items, make them a list.
+
+levels: { strict: 3, normal: 4, relaxed: 6 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  legal: "A clause, a definition or a claim is a paragraph of one sentence by form."
+  literature: "Dialogue and verse set each line apart."
+
+group: readability
+summary:
+  ja: 一文ごとに段落を分けた所が続き、どの文が同じ話なのかが見えない所
+  en: Paragraph after paragraph of a single sentence, so nothing is grouped
+example:
+  ja:
+    before: |
+      新しい会議室が来月から使えます。
+
+      予約は総務部の画面から入れてください。
+
+      一回の予約は二時間までです。
+
+      飲食はできません。
+
+      使い終わったら机を元に戻してください。
+    after: |
+      新しい会議室が来月から使えます。予約は総務部の画面から入れてください。一回の予約は二時間までです。
+
+      使うときは、飲食はしないでください。使い終わったら机を元に戻してください。
+  en:
+    before: |
+      The new meeting room opens next month.
+
+      Book it through the facilities page.
+
+      A booking can last two hours.
+
+      No food or drink is allowed.
+
+      Put the desks back when you leave.
+    after: |
+      The new meeting room opens next month. Book it through the facilities page; a booking can last two hours.
+
+      In the room, no food or drink is allowed. Put the desks back when you leave.
+
+not_flagged:
+  ja: 上限までの一文の段落、見出し・箇条書き・表・コードを挟んだ段落、改行一つでつないだ行は数えません。法務と文学のジャンルでは既定で止めています（条項や定義、台詞や詩の行は、一文ずつ立てるのが形のため）。
+  en: One-sentence paragraphs up to the limit, paragraphs separated by a heading, a list, a table or code, and lines joined by a single line break are not counted together. The legal and literature presets turn it off, since a clause, a definition, a line of dialogue or of verse stands alone by form.
+level_meaning:
+  ja: 一文だけの段落の連続 {limit} 個まで
+  en: up to {limit} one-sentence paragraphs in a row
+rewrite:
+  depth: structure
+  ja:
+    direction: 同じ話の文を一つの段落にまとめてください。並べた項目なら箇条書きにします。文の中身と順序は変えません。
+    pairs:
+      - before: "新しい会議室が来月から使えます。\n\n予約は総務部の画面から入れてください。\n\n一回の予約は二時間までです。"
+        after: 新しい会議室が来月から使えます。予約は総務部の画面から入れてください。一回の予約は二時間までです。
+      - before: "障害は直りました。\n\n原因は設定の誤りでした。\n\n同じ設定の機器も直しました。"
+        after: 障害は直りました。原因は設定の誤りで、同じ設定の機器も直しました。
+    keep:
+      - 文の中身と順序
+      - 強調のために一文で立てた段落（一つなら残す）
+    avoid:
+      - 話題の違う文を一つの段落に詰める
+      - 文を削る
+  en:
+    direction: Join the sentences that make one point into one paragraph; if they are items, make a list. Keep what each sentence says, in order.
+    pairs:
+      - before: "The new meeting room opens next month.\n\nBook it through the facilities page.\n\nA booking can last two hours."
+        after: The new meeting room opens next month. Book it through the facilities page; a booking can last two hours.
+      - before: "The outage is over.\n\nThe cause was a wrong setting.\n\nWe fixed the other servers with the same setting."
+        after: The outage is over. The cause was a wrong setting, and we fixed the other servers that had it.
+    keep:
+      - what each sentence says, in order
+      - a single one-sentence paragraph kept for emphasis
+    avoid:
+      - packing different points into one paragraph
+      - deleting sentences