chaffjs 0.31.0 → 0.33.0

package/rules/broken-link.yaml

@@ -39,7 +39,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: structure
 summary:
   ja: 行き先が空のリンク、文書に無い見出しを指すリンク、定義の無い参照の形のリンク
-  en: A link with no destination, a link to a heading the page does not have, or a reference-style link with no definition
+  en: "A link that goes nowhere: no address, a missing heading, or no definition"
 example:
   ja:
     before: |

package/rules/capacity-runtime-mismatch.yaml

@@ -29,7 +29,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: facts
 summary:
   ja: 「5000 mAh、500 mA、連続使用時間15時間」のように、容量を消費電流で割った時間より長い使用時間
-  en: A runtime longer than the capacity divided by the consumption, such as 5000 mAh at 500 mA stated as 15 hours
+  en: A runtime longer than the battery capacity divided by its consumption
 example:
   ja:
     before: |

package/rules/change-rate-mismatch.yaml

@@ -11,8 +11,8 @@ name:
   en: A rate of change the two values do not give
 
 why:
-  ja: 「前年同月の1,000社から20%増えて1,200社」のように、もとの値・今の値・増減率を一つの文に書くと、読み手は率を確かめずに信じます。数字を一つだけ更新したとき、率だけを去年の文書から写したときに食い違います。一つの文に、もとの値（「から」「に比べて」「前年の」の付いた値）、同じ単位の今の値、向きの語（増加、減少）の付いた百分率が一つずつあるとき、二つの値から率を計算して比べます。率のそばにもとの値が無くても、「昨年の100万円から今年は150万円になり、前年比50%の増加」「2025年度は100万円、2026年度は150万円で」のように二つの値が並んですぐ後に率が続くなら読みます（年が書いてあれば早い年の値がもとの値）。値は書いた桁までの丸めを認めます（12億円は11.5億円から12.5億円のどれか）。
-  en: When one sentence gives the earlier value, the current one and the rate of change ("1,200 companies, up 20% from 1,000"), readers trust the rate without checking it. It goes wrong when one figure is updated and the others are not, or when the rate is copied from last year's text. When a sentence has one earlier value (marked by "from" or "compared with"), one current value in the same unit, and one percentage with a word of direction (up, decline), chaff computes the rate from the two values and compares. The two values may also stand together right before the rate ("rose from $1.0 million last year to $1.5 million, an increase of 50%", "$1.0 million in 2025 and $1.5 million in 2026, up 50%"; with years, the earlier year's value is the earlier one). Each value may be rounded to its last written digit ($12 million is anything from $11.5 million to $12.5 million).
+  ja: 「前年同月の1,000社から20%増えて1,200社」のように、もとの値・今の値・増減率を一つの文に書くと、読み手は率を確かめずに信じます。数字を一つだけ更新したとき、率だけを去年の文書から写したときに食い違います。一つの文に、もとの値（「から」「に比べて」「前年の」の付いた値）、同じ単位の今の値、向きの語（増加、減少）の付いた百分率が一つずつあるとき、二つの値から率を計算して比べます。率のそばにもとの値が無くても、「昨年の100万円から今年は150万円になり、前年比50%の増加」「2025年度は100万円、2026年度は150万円で」のように二つの値が並んですぐ後に率が続くなら読みます（年が書いてあれば早い年の値がもとの値）。今の値は率の後ろでも、「前年同期の2,400百万円から10.0%増加し、2,640百万円となりました」のように動いた先と分かれば読みます。値は書いた桁までの丸めを認めます（12億円は11.5億円から12.5億円のどれか）。表も読みます。見出しの語で前期の列（前期、前年同期）、当期の列（当期、当第2四半期）、増減率の列（増減率、前年同期比）が一つずつ分かる表（見出しの語が無くても、二つの列の見出しに年が一つずつ書いてあれば早い年の列が前期）では、行ごとに二つの値から率を計算し、書いた率と比べます。△・▲・−の付いた率は減少です。「増減」の列は、升に % があるときだけ率と読みます。
+  en: When one sentence gives the earlier value, the current one and the rate of change ("1,200 companies, up 20% from 1,000"), readers trust the rate without checking it. It goes wrong when one figure is updated and the others are not, or when the rate is copied from last year's text. When a sentence has one earlier value (marked by "from" or "compared with"), one current value in the same unit, and one percentage with a word of direction (up, decline), chaff computes the rate from the two values and compares. The two values may also stand together right before the rate ("rose from $1.0 million last year to $1.5 million, an increase of 50%", "$1.0 million in 2025 and $1.5 million in 2026, up 50%"; with years, the earlier year's value is the earlier one). The rate may also come first, with the value reached and then the earlier one ("rose 10.0% to $2,640 million from $2,400 million"). Each value may be rounded to its last written digit ($12 million is anything from $11.5 million to $12.5 million). Tables are read too. When the headings name one column of the earlier value (Prior year), one of the current value (Current year) and one of the rate (YoY, Change (%)), or two columns are each headed by one year (FY2025, FY2026; the earlier year's column holds the earlier value), each row's rate is computed from its two values and compared. A rate marked -, −, ▲ or △ is a decrease. A column headed only "Change" or "Growth" is read as a rate only where its cells carry %.
 
 message:
   ja: 「{rate}%」と書いていますが、二つの値からは {computed}% です
@@ -30,8 +30,8 @@ off_for:
 
 group: facts
 summary:
-  ja: 「1,000社から20%増えて1,200社」のように、一つの文の二つの値と増減率が合わない所
-  en: A rate of change that the two values in the same sentence do not give
+  ja: 「1,000社から20%増えて1,200社」のように、一つの文や表の一行の二つの値と増減率が合わない所
+  en: A rate of change the two values in one sentence or table row do not give
 example:
   ja:
     before: 利用企業は1,300社となり、前年の1,000社から20%増えました。
@@ -41,5 +41,5 @@ example:
     after: Revenue was $1.0 million in 2025 and $1.5 million in 2026, up 50%.
 
 not_flagged:
-  ja: 向きの語の付いた率が二つある文、もとの値が「から」「に比べて」や年で名指されていない文、二つの値と率のあいだで主語が変わる文（「…に増え、利益は20%増えた」）、二つの値のあいだで主語が変わる文（"$1,000 in 2025 and costs were $1,500 in 2026"）、同じ単位の今の値が一つでない文、向きの語が率のそばに無い文は比べません。「前年比20%増」のように値が一つしか無いもの、ポイントの差、倍は見ません。丸めで届く範囲の率は言いません。
-  en: 'A sentence with two rates that each have a word of direction, with no value marked as the earlier one (by a word or a year), with another subject between the values and the rate ("…, and costs rose 20%") or between the two values ("$1,000 in 2025 and costs were $1,500 in 2026"), with no single current value in the same unit, or with no word of direction beside the rate is not compared. A change given with one value ("up 20% year on year"), percentage points and "times" are not read. A rate the rounding of the values can reach is not reported.'
+  ja: 向きの語の付いた率が二つある文、もとの値が「から」「に比べて」や年で名指されていない文、二つの値と率のあいだで主語が変わる文（「…に増え、利益は20%増えた」）、二つの値のあいだで主語が変わる文（"$1,000 in 2025 and costs were $1,500 in 2026"）、同じ単位の今の値が一つでない文、向きの語が率のそばに無い文は比べません。「前年比20%増」のように値が一つしか無いもの、ポイントの差、倍は見ません。丸めで届く範囲の率は言いません。表では、列の役割が見出しから一つずつ決まらない表、前期と当期の列の見出しが違う単位を書いた表（千円と百万円）、値や率の升が数でない行（—、1.0pt、0.5ポイント、(5.0)%）、値が負か百分率の行、二つの値の単位の書き方が違う行、前期の値が0の行は比べません。
+  en: 'A sentence with two rates that each have a word of direction, with no value marked as the earlier one (by a word or a year), with another subject between the values and the rate ("…, and costs rose 20%") or between the two values ("$1,000 in 2025 and costs were $1,500 in 2026"), with no single current value in the same unit, or with no word of direction beside the rate is not compared. A change given with one value ("up 20% year on year"), percentage points and "times" are not read. A rate the rounding of the values can reach is not reported. In a table, nothing is compared when the headings do not name one column for each part or name different units for the two periods (thousand yen, million yen); nor is a row whose value or rate cell is not a number (—, 1.0pt, (5.0)% in brackets), whose values are negative or percentages, whose two values are written with different units, or whose earlier value is zero.'

package/rules/chat-citation-residue.yaml

@@ -28,8 +28,8 @@ use_for: [blog, business, technical, legal, docs, academic, literature, speech]
 
 group: slips
 summary:
-  ja: 「?utm_source=chatgpt.com」の付いたリンクや「oaicite」のように、チャットの答えを貼ったときに残る印
-  en: 'Marks a pasted chat answer leaves behind: links ending in "?utm_source=chatgpt.com", ":contentReference[oaicite:0]"'
+  ja: 「?utm_source=chatgpt.com」の付いたリンクのように、チャットの答えを貼ったときに残る印
+  en: Marks a pasted chat answer leaves behind, such as "?utm_source=chatgpt.com"
 example:
   ja:
     before: |

package/rules/cliche.yaml

@@ -13,7 +13,7 @@ name:
 
 why:
   ja: 「今さら聞けない」「徹底解説」「〜の極意」や、英語の「at the end of the day」「low-hanging fruit」のような決まり文句は、使われすぎて中身が抜けた言い回しです。読み手は見慣れた形を読み飛ばし、この文書で何が言いたいのかが残りません。言い回しの一覧は言語ごとの語彙表にあり、それぞれに何を書けばよいかが付いています。
-  en: '"At the end of the day", "low-hanging fruit" and "move the needle" (今さら聞けない, 徹底解説) are figures of speech worn down to filler. The reader skims the familiar shape and learns nothing about this document. The phrases are listed in the lexicon, each with what to write instead.'
+  en: '"At the end of the day", "low-hanging fruit" and "move the needle" are figures of speech worn down to filler. The reader skims the familiar shape and learns nothing about this document. The phrases are listed in the lexicon, each with what to write instead.'
 
 message:
   ja: 「{matched}」は使い古された決まり文句です
@@ -33,7 +33,7 @@ off_for:
 group: wording
 summary:
   ja: 「今さら聞けない」「徹底解説」や「at the end of the day」のような、使い古された決まり文句
-  en: A worn phrase such as "at the end of the day" or "low-hanging fruit" (今さら聞けない, 徹底解説)
+  en: A worn phrase such as "at the end of the day" or "low-hanging fruit"
 example:
   ja:
     before: |

package/rules/closing-balance-mismatch.yaml

@@ -0,0 +1,63 @@
+id: closing-balance-mismatch
+layer: L3
+status: stable
+how_to_find: closing-balance-mismatch
+# The names are lexicon closing-balance-label (groups opening, inflow, outflow, closing); words of magnitude are
+# amount-multiplier. Tables and label lines are read as net-amount-mismatch reads them.
+extra_word_lists: [closing-balance-label]
+severity: warning
+
+name:
+  ja: 期末の残高が、期首の残高に入金を足し出金を引いた額と合わない
+  en: A closing balance that is not the opening balance plus deposits less withdrawals
+
+why:
+  ja: 預金の取引明細のまとめでは、当月末残高は、前月末残高にお預入れ合計を足し、お引出し合計を引いた額です。読む人は残高を見て、足し引きし直しません。取引を直したのに残高を直さなかったとき、前の月の明細から写したとき、数字を打ち間違えたときに食い違います。同じ表か同じ節に、初めの残高（前月末残高）、入金の合計（お預入れ合計）、出金の合計（お引出し合計）、終わりの残高（当月末残高）の名前が一つずつあり、それぞれに金額があれば、終わりの残高を足し引きと比べます。表では、見出しの行に四つの名前が並ぶ表は行ごとに、一列目に四つの名前が並ぶ表は列ごとに比べます。表の外では、節（見出しから次の見出しまで）の「前月末残高：412,350円」のような名前と金額だけの行を読みます。どの語が四つのどれかは、言語パッケージの語彙表 closing-balance-label にあります。通貨の印が付いた金額は一円（一セント）まで合わなければ言います。千円の単位の金額や印の無い数は丸めてあるかもしれないので、最後の桁の二つ分までのずれは言いません。
+  en: >-
+    On a statement summary the closing balance is the opening balance plus the total deposits less the total withdrawals. The reader takes the closing balance as given and does not add it up again. It goes wrong when a transaction is corrected and the balance is not, when the balance is copied from last month's statement, or when a digit is mistyped. When one table or one section names the balance at the start (Opening balance), the total paid in (Total deposits), the total paid out (Total withdrawals) and the balance at the end (Closing balance) once each, each with an amount, the closing balance is compared with the sum. A table whose header row has the four names is compared row by row, and one whose first column has them column by column. Outside tables, the lines of a section (from one heading to the next) that are only a name and an amount ("Opening balance: $2,418.36") are read. Which words name the four is in the language package's lexicon closing-balance-label. Amounts with a currency mark must agree to the cent. Amounts in thousands, and numbers without a mark, may be rounded, so a difference of up to two steps of their last digit is not reported.
+
+message:
+  ja: 「{written}」は、初めの残高に入金を足し出金を引くと {expected} です
+  en: '"{written}" is written, but the opening balance plus deposits less withdrawals is {expected}'
+
+how_to_fix:
+  ja: 初めの残高、入金と出金の合計、終わりの残高のどれが正しいかを確かめて、ほかを直してください。
+  en: Check which of the opening balance, the two totals and the closing balance is right, and correct the others.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, 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."
+
+group: facts
+summary:
+  ja: 当月末残高が、前月末残高 ＋ 入金合計 − 出金合計 と合わない所
+  en: A closing balance that is not the opening balance plus deposits less withdrawals
+example:
+  ja:
+    before: |
+      - 前月末残高：412,350円
+      - お預入れ合計：285,400円
+      - お引出し合計：245,530円
+      - 当月末残高：425,220円
+    after: |
+      - 前月末残高：412,350円
+      - お預入れ合計：285,400円
+      - お引出し合計：245,530円
+      - 当月末残高：452,220円
+  en:
+    before: |
+      - Opening balance: $2,418.36
+      - Total deposits: $2,941.80
+      - Total withdrawals: $3,203.60
+      - Closing balance: $2,165.56
+    after: |
+      - Opening balance: $2,418.36
+      - Total deposits: $2,941.80
+      - Total withdrawals: $3,203.60
+      - Closing balance: $2,156.56
+
+not_flagged:
+  ja: 四つの名前のどれかが無い表や節、同じ名前が二度ある表の列や節、名前が別々の表や節にあるもの、四つの単位が違うもの（円とドル、千円と円）、数でない金額（—、▲、マイナスや括弧の付いた値）は比べません。日付・お預入れ・お引出し・残高の列が並ぶ取引の表は、行ごとの残高を running-balance-mismatch が見るので、ここでは読みません。文の中の金額（「当月末残高は452,220円です」）や、語彙表に無い名前（前回ご請求額、ご利用残高）は読みません。足し引きがマイナスになるときも言いません。
+  en: 'A table or section without one of the four names, a table column or section that names one of them twice, names spread over separate tables or sections, amounts in different units (yen and dollars, thousands and units), and a value that is not a plain number (—, a negative or bracketed value) are not compared. A transaction table with Date, Deposit, Withdrawal and Balance columns is left to running-balance-mismatch, which checks it row by row. An amount inside a sentence ("The closing balance is $2,156.56") is not read, nor is a name not in the lexicon (Previous balance, New balance, Credits and Debits, which on a card statement move the other way). A sum below zero is not reported either.'

package/rules/colon-lead-in.yaml

@@ -36,7 +36,7 @@ off_for:
 group: ai-tells
 summary:
   ja: 「以下の通りです：」のように、コロンで終わる文から箇条書きへ渡す形が続き、説明が箇条書きの前置きだけになっている所
-  en: 'Sentences ending in a colon that hand off to a list ("Here''s what you need to know:"), section after section'
+  en: Section after section that opens with a sentence ending in a colon before a list
 example:
   ja:
     pad: true

package/rules/comparative-without-baseline.yaml

@@ -31,7 +31,7 @@ off_for:
 group: wording
 summary:
   ja: 「より良い」「さらに高速」のように、比べる相手が書かれていない比較
-  en: A comparative such as "is faster" or "is more efficient" with no "than" or other baseline nearby
+  en: A comparison such as "is faster" that never says faster than what
 
 example:
   ja:

package/rules/concrete-evidence-density.yaml

@@ -35,7 +35,7 @@ off_for:
 group: structure
 summary:
   ja: 数字もコードもリンクも無く、読み手が持ち帰れるものの無い節
-  en: A section with no number, no code and no link, so the reader has nothing to take away
+  en: "A section with no number, code or link: nothing for the reader to take away"
 example:
   ja:
     config: { rules: { concrete-evidence-density: strict } }

package/rules/connection-time-short.yaml

@@ -30,7 +30,7 @@ off_for:
 group: facts
 summary:
   ja: 旅程で、次の予定までの間が文書に書いた移動の時間より短い所
-  en: An itinerary that leaves less time for a connection than the travel time it states
+  en: An itinerary that leaves less time for a connection than the trip it states
 example:
   ja:
     before: |

package/rules/contact-variant.yaml

@@ -41,8 +41,8 @@ off_for:
 
 group: facts
 summary:
-  ja: 同じ文書で、メールアドレスや住所が一か所だけ違って書かれている所（hibari-lab と hibarilab、4番1号と1番4号）
-  en: One email address or postal address written elsewhere with a slip (hibari-lab and hibarilab, 2-4-1 and 2-1-4)
+  ja: 同じメールアドレスや住所が、一か所だけ違って書かれている所（hibari-lab と hibarilab）
+  en: An email or postal address written differently in one place
 example:
   ja:
     before: |
@@ -72,5 +72,5 @@ example:
       Questions about a change can be sent to support@hibari-lab.example.
 
 not_flagged:
-  ja: 別のメールアドレス（sales@ と support@）、数字だけが違うもの（support1@ と support2@）、5文字より短い語の違い（hr@ と pr@、sale@ と sales@）は指しません。住所は、同じ行で前に「住所」「本店所在地」のような語があるものだけを読みます。持ち主の違う住所（本店と支店）、町の違う住所、同じ名の町でも市や区の違う住所、番地の数の違う住所、二つ以上の番地が違う住所は比べません。都道府県・市・区・郡の無い住所は読みません。
-  en: Two different addresses (sales@ and support@), addresses that differ only in a digit (support1@ and support2@) and a difference in a word shorter than five letters (hr@ and pr@, sale@ and sales@) are not reported. Only a postal address with an address word (Address, head office) before it on its line is read. Addresses of different offices (a head office and a branch), on different streets, on a street of the same name in another town, with a different count of block numbers, or with two numbers changed are not compared.
+  ja: 別のメールアドレス（sales@ と support@）、数字だけが違うもの（support1@ と support2@）、5文字より短い語の違い（hr@ と pr@、sale@ と sales@）は指しません。住所は、同じ行で前に「住所」「本店所在地」のような語があるものと、二列の表でその語を名前にした行（| 所在地 | … |）だけを読みます。三列以上の表の住所は読みません。持ち主の違う住所（本店と支店）、町の違う住所、同じ名の町でも市や区の違う住所、番地の数の違う住所、二つ以上の番地が違う住所は比べません。都道府県・市・区・郡の無い住所は読みません。
+  en: Two different addresses (sales@ and support@), addresses that differ only in a digit (support1@ and support2@) and a difference in a word shorter than five letters (hr@ and pr@, sale@ and sales@) are not reported. Only a postal address with an address word (Address, head office) before it on its line, or in a two-column table row named by such a word (| Address | … |), is read; addresses in wider tables are not. Addresses of different offices (a head office and a branch), on different streets, on a street of the same name in another town, with a different count of block numbers, or with two numbers changed are not compared.

package/rules/contrast-framing.yaml

@@ -38,8 +38,8 @@ off_for:
 
 group: ai-tells
 summary:
-  ja: 「単なる X ではなく Y」「X だけでなく Y も」のような対比の枠が重なり、誰も言っていない X を打ち消し続けている所
-  en: 'Contrast frames piling up ("It''s not X, it''s Y", "not just X, but Y"), knocking down an X nobody said'
+  ja: 「単なる X ではなく Y」のような対比が重なり、誰も言っていない X を打ち消し続ける所
+  en: Contrasts piled up ("It's not X, it's Y"), knocking down an X nobody said
 example:
   ja:
     pad: true

package/rules/cross-doc-broken-link.yaml

@@ -45,7 +45,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: structure
 summary:
   ja: 一緒に見たほかのファイルへのリンクで、行き先のファイルか見出しが無いもの
-  en: A link to another of the files checked together whose file or heading is not there
+  en: A link to another of the files checked whose file or heading is not there
 example:
   ja:
     other: |

package/rules/cross-doc-fact-conflict.yaml

@@ -30,7 +30,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: facts
 summary:
   ja: 同じ項目（料金、版、締切、問い合わせ先）に、ファイルによって違う値を書いた所
-  en: The same item (a fee, a version, a deadline, a contact address) given different values in different files
+  en: The same item (a fee, a deadline, a contact) given different values in two files
 example:
   ja:
     other: |

package/rules/cross-doc-term-variant.yaml

@@ -41,7 +41,7 @@ off_for:
 group: consistency
 summary:
   ja: 同じ語を、ファイルによって違う書き方で書いている所（サーバ／サーバー、e-mail／email）
-  en: The same word spelled one way in some files and another way in the rest (サーバ / サーバー, e-mail / email)
+  en: The same word spelled one way in some files and another way in others
 example:
   ja:
     other: |

package/rules/cumulative-below-current.yaml

@@ -0,0 +1,59 @@
+id: cumulative-below-current
+layer: L3
+status: stable
+how_to_find: cumulative-below-current
+severity: warning
+
+name:
+  ja: 累計が当月の値より小さい
+  en: A cumulative figure lower than this period's
+
+why:
+  ja: 給与明細の「年初からの累計」、売上の月報の「累計」、予算の執行表の「累計実績」は、当月（今回、当期）の値を含んだ合計です。含んでいる部分より合計が小さいことはありません。累計の桁を一つ落としたとき、行を一つずらして写したとき、前の月の表の累計を直し忘れたときに起きます。どの列が当月でどの列が累計かは、列の見出しの語（当月、今回、当期、累計、年初来、This month、This period、Current、Year to date、YTD、Cumulative）だけで決めます。列の並びでは決めません。「前月までの累計」「前月累計」「Prior YTD」のように前の期間までを言う列は、当月を含まないので累計の列としては読みません。同じ単位で書いた0以上の数だけを比べ、書いた数の最後の桁の半分までの丸めを認めます。
+  en: 'The "year to date" of a payslip, the "cumulative" of a monthly sales report and the "YTD actual" of a budget report are totals that include this period''s figure. A total cannot be smaller than a part it includes. It goes wrong when a digit of the cumulative figure is dropped, when a row is copied one line off, or when last month''s table is reused and its cumulative figures are not updated. Which column is this period and which the cumulative one is decided by the heading words alone (This month, This period, Current, Year to date, YTD, Cumulative), never by where a column stands. A column up to an earlier period ("Prior YTD", "Brought forward") does not hold this period and is not read as the cumulative one. Only figures of zero or more written in the same unit are compared, and each may be rounded to half its last digit.'
+
+message:
+  ja: 累計「{cumulative}」が、当月の「{current}」より小さくなっています
+  en: 'The cumulative figure "{cumulative}" is lower than this period''s "{current}"'
+
+how_to_fix:
+  ja: 累計の値と当月の値のどちらが正しいかを確かめて、もう一方を直してください。
+  en: Check whether the cumulative figure or this period's figure is right, and correct the other.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, 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."
+
+group: facts
+summary:
+  ja: 給与明細や月報で、累計が当月の値より小さい所
+  en: A year-to-date figure lower than the same row's figure for this period
+example:
+  ja:
+    before: |
+      | 項目 | 当月 | 年初からの累計 |
+      | --- | --- | --- |
+      | 総支給額 | 327,200円 | 2,912,400円 |
+      | 所得税 | 7,750円 | 6,890円 |
+    after: |
+      | 項目 | 当月 | 年初からの累計 |
+      | --- | --- | --- |
+      | 総支給額 | 327,200円 | 2,912,400円 |
+      | 所得税 | 7,750円 | 68,900円 |
+  en:
+    before: |
+      | Item | This period | Year to date |
+      | --- | --- | --- |
+      | Gross pay | $1,661.00 | $14,820.00 |
+      | Federal income tax | $96.00 | $85.80 |
+    after: |
+      | Item | This period | Year to date |
+      | --- | --- | --- |
+      | Gross pay | $1,661.00 | $14,820.00 |
+      | Federal income tax | $96.00 | $858.00 |
+
+not_flagged:
+  ja: 当月の列か累計の列が無い表、どちらかが二つ以上ある表（「当月予算」と「当月実績」が並ぶ表）、見出しの括弧の単位（千円、百万円）が違う表は比べません。前の期間までを言う列（前月累計、前回までの累計）と、残高や平均を言う列（現在の残高）は、当月の列とも累計の列とも読みません。升が空、「-」「—」、マイナス（▲1,000、-1,000、(1,000)）の行は比べません。返金や年末調整で累計が当月より小さくなることがあるためです。単位の書き方が違う行、平均・単価・率・残高・在庫のように期間ごとに足し上げない値の行も比べません。累計と当月が同じ値（最初の月）は正しいので言いません。丸めで届く差も言いません。
+  en: "A table without a this-period column or a cumulative one, with two of either (This month budget and This month actual side by side), or whose two headings name different units in brackets (thousands, millions) is not compared. A column up to an earlier period (Prior YTD, Brought forward) or of a level (Current balance) is read as neither. A row with a blank cell, a dash or a negative figure (-1,000, (1,000)) is skipped, since a refund can make a year-to-date figure fall below this period's; so is a row written in different units, and a row of a figure that is not summed over periods (an average, a rate, a price, a balance). A cumulative figure equal to this period's (the first period) is right and is not reported, and neither is a difference the rounding can reach."

package/rules/currency-column-mix.yaml

@@ -0,0 +1,70 @@
+id: currency-column-mix
+layer: L3
+status: stable
+how_to_find: currency-column-mix
+# Which currency an amount is in is the language's currency-notation (¥ and 円 are one currency); currency-column names the
+# heading words of a column of currencies or exchange rates.
+word_list: currency-column
+extra_word_lists: [currency-notation, amount-multiplier]
+severity: warning
+
+name:
+  ja: 表の一つの列に、違う通貨の金額が一つだけある
+  en: One amount in another currency in a column of amounts
+
+why:
+  ja: 円の金額が並ぶ列に一つだけ「USD 45」があると、読み手はその行だけ通貨が違うことに気づかずに足したり比べたりします。別の見積書や外国の請求書から行を写したとき、換算するのを忘れたときに起きます。表の列ごとに、金額の通貨（¥ と 円 は同じ通貨と読みます）を数え、二つ以上の升が同じ通貨で、ほかの通貨の升がちょうど一つのとき、その升を指します。
+  en: When one cell of a column of dollar amounts reads "¥12,500", the reader adds or compares it with the others without noticing it is in another currency. It happens when a row is copied from another quotation or a foreign invoice, or when an amount is not converted. For each column of a table, the currencies of its amounts are counted (¥ and yen are one currency); when at least two cells are in one currency and exactly one cell is in another, that cell is pointed out.
+
+message:
+  ja: 「{item}」の「{written}」だけが、ほかの升（「{usual}」など）と違う通貨で書かれています
+  en: '"{item}" is written "{written}", in another currency than the rest of its column ("{usual}")'
+
+how_to_fix:
+  ja: 列のほかの金額と同じ通貨に換算して書くか、本当に違う通貨で払うなら、行の名前か列の見出しに通貨を書いてください（「海上保険料（USD）」）。
+  en: Convert the amount to the column's currency, or, if it really is paid in another currency, name the currency in the row's label or the column's heading ("Marine insurance (JPY)").
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, 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."
+
+group: facts
+summary:
+  ja: 円の金額が並ぶ列に一つだけある「USD 45」のような、違う通貨の升
+  en: A lone amount in another currency in a column, such as ¥12,500 among dollars
+example:
+  ja:
+    before: |
+      | 費目 | 金額 |
+      | --- | --- |
+      | 海上運賃 | 48,000円 |
+      | 海上保険料 | USD 45 |
+      | 書類作成費 | 3,000円 |
+    after: |
+      | 費目 | 金額 |
+      | --- | --- |
+      | 海上運賃 | 48,000円 |
+      | 海上保険料 | 6,500円 |
+      | 書類作成費 | 3,000円 |
+  en:
+    before: |
+      | Charge | Amount |
+      | --- | --- |
+      | Ocean freight | $640.00 |
+      | Marine insurance | ¥12,500 |
+      | Documentation fee | $40.00 |
+    after: |
+      | Charge | Amount |
+      | --- | --- |
+      | Ocean freight | $640.00 |
+      | Marine insurance | $85.00 |
+      | Documentation fee | $40.00 |
+
+not_flagged:
+  ja: 通貨の列や為替レートの列（通貨、為替、レート、換算、外貨）がある表、見出しに二つの通貨を書いた列（金額（円/USD））、一つの升に二つの通貨を書いた升（¥12,500（USD 85））がある列は言いません。同じ通貨の升が二つ未満の列、ほかの通貨の升が二つ以上ある列、三つ以上の通貨が並ぶ列、行の名前の括弧にその通貨を書いた行（送金手数料（USD））、通貨の付かない数だけの列も言いません。¥ が円か人民元かは見分けません。
+  en: A table with a column of currencies or of exchange rates (Currency, Exchange rate, FX, converted, equivalent), a column whose heading names two currencies ("Amount (JPY/USD)"), and a column with a cell that gives two currencies ("¥12,500 (USD 85)") are not reported. Neither is a column with fewer than two cells in one currency, with two or more cells in another, or with three currencies or more, a row whose label names that currency in brackets ("Transfer fee (JPY)"), or a column of bare figures with no currency. Whether ¥ is yen or yuan is not told apart.
+level_meaning:
+  ja: 表の一つの列に違う通貨の金額が一つだけあるとき指摘
+  en: reported when one amount of a column is in another currency

package/rules/currency-notation-consistency.yaml

@@ -27,8 +27,8 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
 group: consistency
 summary:
-  ja: 「1,000円」と「¥1,000」、「$20」と「USD 20」のように、一つの文書で同じ通貨の金額を二通りに書いている所
-  en: One currency written two ways in one document, such as "$20" and "USD 20", or "1,000円" and "¥1,000"
+  ja: 「1,000円」と「¥1,000」のように、一つの文書で同じ通貨の金額を二通りに書いた所
+  en: One currency written two ways in one document, such as "$20" and "USD 20"
 example:
   ja:
     before: |

package/rules/cushion-phrase-density.yaml

@@ -35,7 +35,7 @@ off_for:
 group: wording
 summary:
   ja: 「恐れ入りますが」「念のため」のようなクッション言葉が多く、用件が埋もれている所
-  en: So many softeners ("sorry to bother", "just wanted to") that the request gets lost
+  en: So many softeners ("sorry to bother", "just wanted to") that the ask gets lost
 example:
   ja:
     pad: true

package/rules/dangling-participle.yaml

@@ -31,8 +31,8 @@ off_for:
 
 group: wording
 summary:
-  ja: 英語で、「Having reviewed the code, it is ready.」のように、分詞の句の後ろの主語が形だけの it や there の文
-  en: 'A participle phrase followed by an empty "it" or "there", as in "Having reviewed the code, it is ready."'
+  ja: 英語で、分詞の句の後ろの主語が形だけの it や there になっている文
+  en: An opening participle followed by an empty "it" or "there" as the subject
 
 example:
   en:

package/rules/dangling-reference.yaml

@@ -32,7 +32,7 @@ sources: [jis-z8301-2019, femmer-2017]
 group: structure
 summary:
   ja: 「第5条に定める」と書いてあるのに、その第5条が文書に無い所
-  en: A reference such as "as set out in Article 5" to a provision the document does not have
+  en: A reference such as "see Article 5" to an article the document does not have
 example:
   ja:
     before: |

package/rules/date-format-consistency.yaml

@@ -39,7 +39,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: consistency
 summary:
   ja: 「2026-10-02」と「2026年10月2日」のように、一つの文書で日付を二通りに書いている所
-  en: Dates written two ways in one document, such as "2026-10-02" and "October 2, 2026"
+  en: Dates written two ways in one document, as "2026-10-02" and "October 2, 2026"
 example:
   ja:
     before: |

package/rules/date-outside-period.yaml

@@ -10,8 +10,8 @@ name:
   en: A date outside the stated period
 
 why:
-  ja: 「旅行期間：10月12日〜10月15日」と書いた旅程の中に10月17日の予定があると、期間と日程のどちらが正しいのかを読み手が問い合わせることになります。日付を書き写し間違えたときや、日程を動かして期間を直し忘れたときに起きます。期間は「旅行期間」「会期」のような期間の語で始まる一行から読み、その後ろの同じ節の箇条書き、表の行、見出しの日付と、地の文の年の無い日付を比べます。前泊や事後の予定、申込締切や予約の日、過去の回のように、期間の外に置く語がその行や文、節の見出しにある日付は比べません。年の無い期間（12月28日〜1月4日）は年をまたぐ期間として読みます。「開講期間」のように文書の仕事がその中で済む期間を、文書の頭か概要の節に書いたときは、後ろのどの節でも「提出」「締切」「課題：」のある項目や文の日付が期間の終わりより後なら指します（課題の提出期限が学期の後）。年の無い日付は、期間が一つの年に収まるときだけその年と読みます。
-  en: 'When an itinerary says "Trip dates: Oct 12–15" and then lists something on October 17, the reader has to ask whether the period or the schedule is right. It happens when a date is copied wrong, or when the schedule moves and the period is not updated. The period is read from one line that starts with a period word such as "Trip dates" or "Conference", and the dates after it in the same section are compared, in list items, table rows and headings, and in running text when the date has no year. A date whose item, sentence or section heading marks it as outside the period on purpose (a post-trip meeting, a booking deadline, a past edition) is not compared. A period without a year ("Dec 28 – Jan 4") is read as running into the new year. When the period the document''s work is done in ("Term") is stated at the top or in the overview section, a date after its end in an item or sentence of any later section that says "submit", "due", "deadline" or "Assignment:" is reported (an assignment due after the term). A date without a year takes the term''s year only when the term lies within one year.'
+  ja: 「旅行期間：10月12日〜10月15日」と書いた旅程の中に10月17日の予定があると、期間と日程のどちらが正しいのかを読み手が問い合わせることになります。日付を書き写し間違えたときや、日程を動かして期間を直し忘れたときに起きます。期間は「旅行期間」「会期」のような期間の語で始まる一行から読み、その後ろの同じ節の箇条書き、表の行、見出しの日付と、地の文の年の無い日付を比べます。前泊や事後の予定、申込締切や予約の日、過去の回のように、期間の外に置く語がその行や文、節の見出しにある日付は比べません。地の文で「9月18日までにお知らせください」のように締め切りの語（までに、必着）が付いた日付も、期間の後の返事の期限なので比べません。年の無い期間（12月28日〜1月4日）は年をまたぐ期間として読みます。「開講期間」のように文書の仕事がその中で済む期間を、文書の頭か概要の節に書いたときは、後ろのどの節でも「提出」「締切」「課題：」のある項目や文の日付が期間の終わりより後なら指します（課題の提出期限が学期の後）。年の無い日付は、期間が一つの年に収まるときだけその年と読みます。
+  en: 'When an itinerary says "Trip dates: Oct 12–15" and then lists something on October 17, the reader has to ask whether the period or the schedule is right. It happens when a date is copied wrong, or when the schedule moves and the period is not updated. The period is read from one line that starts with a period word such as "Trip dates" or "Conference", and the dates after it in the same section are compared, in list items, table rows and headings, and in running text when the date has no year. A date whose item, sentence or section heading marks it as outside the period on purpose (a post-trip meeting, a booking deadline, a past edition) is not compared. Nor is a date in running text that a deadline word is attached to ("let us know by September 18"): it is a reply-by date after the period. A period without a year ("Dec 28 – Jan 4") is read as running into the new year. When the period the document''s work is done in ("Term") is stated at the top or in the overview section, a date after its end in an item or sentence of any later section that says "submit", "due", "deadline" or "Assignment:" is reported (an assignment due after the term). A date without a year takes the term''s year only when the term lies within one year.'
 
 message:
   ja: 「{date}」が、書いた期間「{period}」の外です
@@ -30,7 +30,7 @@ off_for:
 group: facts
 summary:
   ja: 旅程や会期のように書いた期間の外にある、日程の日付
-  en: A dated item outside the period the document states, such as a trip's or a conference's dates
+  en: A dated item outside the period the document gives, such as a trip's dates
 example:
   ja:
     before: |
@@ -60,5 +60,5 @@ example:
       - May 5: closing session
 
 not_flagged:
-  ja: 期間を書いていない文書、期間の外に置く語（前泊、事後、申込締切、予約、前回）のある日付、年の無い期間が年をまたぐときの年明けの日付は比べません。旅行期間や会期の後の締め切り（精算書の提出）、支払の期限、成績発表や成績照会、再試験のように学期の後に来てよい日付、年をまたぐ開講期間に対する年の無い締め切りは指しません。
-  en: 'A document with no stated period, a date marked as outside on purpose ("post-trip", "follow-up", "book by", "deadline", "previous"), and the new-year dates of a period without a year that runs past December 31 are not compared. A deadline after a trip or a conference (an expense report), a payment deadline, work that may come after a term (grades released, grade appeals, resits), and a deadline without a year against a term that runs across two years are not reported.'
+  ja: 期間を書いていない文書、期間の外に置く語（前泊、事後、申込締切、予約、前回）のある日付、締め切りの語の付いた日付（9月18日までに）、年の無い期間が年をまたぐときの年明けの日付は比べません。旅行期間や会期の後の締め切り（精算書の提出）、支払の期限、成績発表や成績照会、再試験のように学期の後に来てよい日付、年をまたぐ開講期間に対する年の無い締め切りは指しません。
+  en: 'A document with no stated period, a date marked as outside on purpose ("post-trip", "follow-up", "book by", "deadline", "previous"), a reply-by date ("by September 18", "no later than September 18"), and the new-year dates of a period without a year that runs past December 31 are not compared. A deadline after a trip or a conference (an expense report), a payment deadline, work that may come after a term (grades released, grade appeals, resits), and a deadline without a year against a term that runs across two years are not reported.'

package/rules/date-range-reversed.yaml

@@ -10,8 +10,8 @@ name:
   en: A period that ends before it starts
 
 why:
-  ja: 「2026年4月1日〜2026年3月31日」のように、期間の終わりの日付が始まりより前だと、読み手はどちらの日付が正しいのかを問い合わせることになります。年を書き写し間違えたときや、日付を片方だけ直したときに起きます。二つの日付の間が範囲の記号（〜、–）だけのときと、「から」でつなぎ終わりの日付のあとに「まで」が続くときを期間として比べます。年の無い期間（12月28日〜1月4日）は年をまたぐかもしれないので比べません。
-  en: 'When a period such as "5 April 2026 – 2 April 2026" ends before it starts, the reader has to ask which date is right. It happens when a year is copied wrong, or when only one of the two dates is changed. Two dates are read as a period when only a range mark (–, —) or a word such as "through" or "until" stands between them, or when they are written "from … to …". A period without a year ("28 December – 4 January") may run into the next year and is not compared.'
+  ja: 「2026年4月1日〜2026年3月31日」のように、期間の終わりの日付が始まりより前だと、読み手はどちらの日付が正しいのかを問い合わせることになります。年を書き写し間違えたときや、日付を片方だけ直したときに起きます。二つの日付の間が範囲の記号（〜、–）だけのときと、「から」でつなぎ終わりの日付のあとに「まで」が続くときと、一つの文に始まりの語と終わりの語が一つずつあり二つの日付に付くとき（2026年4月1日から開始し、2027年3月31日に終了する）を期間として比べます。年の無い期間（12月28日〜1月4日）は年をまたぐかもしれないので比べません。年を片方にだけ書いた期間（2026年7月9日〜7月8日）は同じ年と読み、逆になるときは、年の無い側の曜日がその年に合うか、翌年（または前年）にまたぐと読むと一年近くになるときだけ言います（2026年12月28日〜1月4日は年をまたぐ期間です）。
+  en: 'When a period such as "5 April 2026 – 2 April 2026" ends before it starts, the reader has to ask which date is right. It happens when a year is copied wrong, or when only one of the two dates is changed. Two dates are read as a period when only a range mark (–, —) or a word such as "through" or "until" stands between them, or when they are written "from … to …", or when one sentence gives the start and the end with one start word and one end word on the two dates ("starts on 1 April 2026 and ends on 31 March 2027"). A period without a year ("28 December – 4 January") may run into the next year and is not compared. With the year on one end only ("July 9 – July 8, 2026"), both ends are read in that year; a reversed one is reported only when the weekday on the end without a year matches that reading, or when reading it across the year end would make the period nearly a year long ("December 28 – January 4, 2027" crosses the year end).'
 
 message:
   ja: 期間「{period}」の終わりが始まりより前です
@@ -44,5 +44,5 @@ example:
       Applications are open 1 April 2026 – 31 March 2027.
 
 not_flagged:
-  ja: 年の無い期間（12月28日〜1月4日）、「から」だけで「まで」の無いもの（10日から3日に変更）、日付の間に言葉のあるものは比べません。
-  en: 'A period without a year, "from … to …" in a sentence with a word that changes a date ("moved from March 10 to March 3", "… was postponed"), and two dates with words between them are not compared.'
+  ja: 年の無い期間（12月28日〜1月4日）、「から」だけで「まで」の無いもの（10日から3日に変更）、日付の間に言葉のあるもの、始まりの語か終わりの語が二つある文は比べません。
+  en: 'A period without a year, "from … to …" in a sentence with a word that changes a date ("moved from March 10 to March 3", "… was postponed"), two dates with words between them, and a sentence with two start words or two end words ("starts on … and phase 2 starts on …") are not compared.'

package/rules/date-stamp-order.yaml

@@ -18,12 +18,12 @@ why:
   en: 'The "Established: April 1, 2023" and "Last updated: September 1, 2026" lines of a policy or terms say when the document was first set and when it was last changed. An established date after an update means the document was changed before it existed, and the reader cannot tell which date is right or how old the current version is. It happens when the dates of the previous version are rewritten and one is missed. Lines holding only a date and an established or updated word are read, and when the established date is later than an update both lines are reported: nothing tells which of the two is wrong.'
 
 message:
-  ja: 制定の日付 {established} が、改定の日付 {updated} より後です
+  ja: 制定の日付（{established}）が、改定の日付（{updated}）より後です
   en: "The established date {established} is after the update {updated}"
 
 messages:
   updated:
-    ja: 改定の日付 {updated} が、制定の日付 {established} より前です
+    ja: 改定の日付（{updated}）が、制定の日付（{established}）より前です
     en: "The update {updated} is before the established date {established}"
 
 how_to_fix:

package/rules/date-without-year.yaml

@@ -12,12 +12,12 @@ name:
   en: Date without a year
 
 why:
-  ja: 文書のほかの日付には年があるのに、一つだけ年が無い日付は、読み手がどの年かを推し量ることになります。年をまたぐ日付が並ぶ文書（12月と1月）では、年の無い日付がどちらの年か決まりません。
-  en: When the document's other dates carry a year, a date without one leaves the reader to guess it. When the dates cross the turn of a year (December and January), a yearless date could be either year.
+  ja: 文書の日付が二つ以上の年にわたるとき（2025年の日付と2026年の日付）、年の無い日付はどの年のことか読み手には決まりません。年をまたぐ日付が並ぶ文書（12月と1月）でも、年の無い日付がどちらの年か決まりません。日付がみな同じ年なら、年が無くても読み手には分かります。
+  en: When the document's dates span more than one year (some in 2025, some in 2026), a date without a year leaves the reader unable to tell which year it means. The same holds where the dates cross the turn of a year (December and January). When every dated date is in one year, the reader can tell the year without it.
 
 message:
-  ja: 「{date}」には年がありません（この文書のほかの日付 {count} 個には年があります）
-  en: '"{date}" has no year (the document''s other {count} dates do)'
+  ja: 「{date}」には年がありません。この文書の日付は {from}年から{to}年にわたるので、どの年か決まりません
+  en: '"{date}" has no year, and the document''s dates run from {from} to {to}, so the year is unclear'
 messages:
   boundary:
     ja: 「{date}」には年がありません。年の変わり目をまたぐ日付が並んでいるので、どちらの年か決まりません
@@ -33,39 +33,39 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
 group: structure
 summary:
-  ja: ほかの日付には年があるのに年の無い日付と、年の変わり目をまたいで並ぶ年の無い日付
-  en: A date without a year where the document's other dates carry one, or where the dates cross the turn of a year
+  ja: 文書の日付が二つ以上の年にわたるときや年の変わり目をまたぐときの、年の無い日付
+  en: A date with no year where the document's dates span years or cross a new year
 example:
   ja:
     before: |
       # 日程
 
+      - 2025年10月15日（水）：前回の説明会
       - 2026年10月14日（水）：説明会
-      - 2026年10月21日（水）：申込の締め切り
       - 10月28日（水）：結果の連絡
     after: |
       # 日程
 
+      - 2025年10月15日（水）：前回の説明会
       - 2026年10月14日（水）：説明会
-      - 2026年10月21日（水）：申込の締め切り
       - 2026年10月28日（水）：結果の連絡
   en:
     before: |
       # Schedule
 
+      - October 15, 2025: last year's briefing
       - October 14, 2026: briefing
-      - October 21, 2026: applications close
       - October 28: results sent
     after: |
       # Schedule
 
+      - October 15, 2025: last year's briefing
       - October 14, 2026: briefing
-      - October 21, 2026: applications close
       - October 28, 2026: results sent
 
 not_flagged:
-  ja: 年を一度だけ書いて、あとの日付は月と日だけで書く文書（年の無い日付のほうが多い文書）は、書き方の選び方として指しません。ただしその場合も、年をまたぐ日付は指します。月だけ・年だけの日付は見ません。
-  en: A document that writes the year once and the rest as month and day (more yearless dates than dated ones) is a style, and not reported, except for a date across the turn of a year. Month-only and year-only dates are not checked.
+  ja: 年のある日付がみな同じ年の文書では、年の無い日付を指しません（どの年か読み手に分かるため）。年を一度だけ書いて、あとの日付は月と日だけで書く文書（年の無い日付のほうが多い文書）も、書き方の選び方として指しません。ただしどちらの場合も、年をまたぐ日付は指します。どの年のものでもない日付も指しません。毎年の日（毎年4月1日、年末年始閉庁日（12月29日～1月3日）、4月1日から翌年3月31日まで）と、例の日付（例えば…4月1日に届いた場合、例：のあとの日付）です。年のある日付が一つも無い文書、月だけ・年だけの日付は見ません。
+  en: A document whose dated dates are all in one year is not reported, since the reader can tell the year. A document that writes the year once and the rest as month and day (more yearless dates than dated ones) is a style, and not reported either. In both, a date across the turn of a year is still reported. Nor is a date of no one year, such as a day that comes round every year ("every year on April 1", "each December 31", "April 1 to March 31 of the following year") and a date in a worked example ("for example, a request received on April 1", the dates after "e.g."). A document with no dated date, and month-only and year-only dates, are not checked.
 rewrite:
   depth: light
   ja: