chaffjs 0.31.0 → 0.33.0

package/rules/empty-intensifier.yaml

@@ -35,7 +35,7 @@ off_for:
 group: wording
 summary:
   ja: 「非常に重要」「言うまでもなく」のように、何が大事かを言わずに強めるだけの言い方
-  en: Phrases such as "extremely important" that add weight without saying what matters
+  en: Words like "extremely important" that add weight without saying what matters
 example:
   ja:
     before: 期限を守ることは非常に重要です。

package/rules/empty-list-item.yaml

@@ -32,7 +32,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: structure
 summary:
   ja: 「担当：」のように見出しの語だけで値の無い項目と、記号だけの項目
-  en: A list item holding only a label ("Owner:") where its siblings give values, or an item with nothing in it
+  en: A list item with only a label ("Owner:") and no value, or with nothing in it
 example:
   ja:
     before: |

package/rules/empty-section.yaml

@@ -28,7 +28,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: structure
 summary:
   ja: 見出しのすぐ後ろに同じ深さか浅い見出しが来て、何も書かれていない節
-  en: A heading with nothing under it before the next heading of the same or a higher level
+  en: A heading with nothing under it before the next heading at its level or higher
 example:
   ja:
     before: |

package/rules/empty-table-cell.yaml

@@ -58,8 +58,8 @@ example:
       | Oct 28 | Takahashi | Set the briefing date |
 
 not_flagged:
-  ja: 一番左の列は見ません（空欄で「上と同じ」を表す書き方があるため）。同じ列に空欄が二つ以上ある列、本文の行が三つより少ない表、「—」「なし」と書いたセルは指しません。Markdown の表でだけ動きます。
-  en: The first column is not checked, since a blank there often means "same as above". A column with two or more blanks, a table with fewer than three body rows, and a cell holding "—" or "none" are not reported. Markdown tables only.
+  ja: 一番左の列は見ません（空欄で「上と同じ」を表す書き方があるため）。同じ列に空欄が二つ以上ある列、本文の行が三つより少ない表、「—」「なし」と書いたセルは指しません。合計・小計・税の行（「| 合計 | | | 48,400円 |」）、期間の合計の行（週計）、差し引きで決まる金額の行（総支給額）の数量や単価の空欄も指しません。金額の列（ほかの行がどれも数字を書いている一番右の列）の空欄は指します。Markdown の表でだけ動きます。
+  en: The first column is not checked, since a blank there often means "same as above". A column with two or more blanks, a table with fewer than three body rows, and a cell holding "—" or "none" are not reported. Nor are the quantity and unit-price blanks of a total, subtotal or tax row ("| Total | | | $612.00 |"), a period total ("Week total") or a computed amount ("Gross pay"); a blank in its amount column (the rightmost column every other row fills with a figure) still is. Markdown tables only.
 rewrite:
   depth: light
   ja:

package/rules/expletive-construction.yaml

@@ -35,7 +35,7 @@ off_for:
 group: readability
 summary:
   ja: 英語で、There is や It is ... that で主語を後ろへ押しやった文が多い所
-  en: Many sentences that open with "There is" or "It is ... that", pushing the subject to the back
+  en: Many sentences that open with "There is" or "It is ... that"
 example:
   en:
     config: { rules: { expletive-construction: strict } }

package/rules/fact-conflict.yaml

@@ -11,8 +11,8 @@ name:
   en: One item given two different values
 
 why:
-  ja: 同じ節の中で「締切：10月5日」と「締切：10月7日」のように、同じ項目に違う値を書くと、読み手はどちらを信じればよいか分かりません。日程や料金を直したときに、一か所だけ直し忘れると起きます。「項目：値」「項目は値です」と書いた所と表の升を読み、同じ節で同じ項目名（全角半角、大文字小文字は揃えて比べます）に、同じ単位で違う値があれば指します（単位の語彙表にある単位の量、410 g と 450 g も比べます）。保存期間は節をまたいで比べます。「個人情報を1年間保存します」と「3年間を経過した個人情報を削除します」のように、同じもの（同じ名詞句）に二通りの長さが書いてあれば指します。
-  en: 'When one section says "Deadline: May 3" and later "Deadline: May 5", the reader cannot tell which to trust. It happens when a date or a price is changed in one place and not in the other. Values written as "Item: value" or "The item is value", and table cells, are read; the same item name (case and width aside) with two different values in the same unit within one section is pointed out (measured quantities such as 410 g and 450 g included). A retention period is compared across the whole document: "we keep personal information for 1 year" and "we delete personal information 3 years after the account is closed" give one thing (the same noun phrase) two lengths.'
+  ja: 同じ節の中で「締切：10月5日」と「締切：10月7日」のように、同じ項目に違う値を書くと、読み手はどちらを信じればよいか分かりません。日程や料金を直したときに、一か所だけ直し忘れると起きます。「項目：値」「項目は値です」と書いた所と表の升を読み、同じ節で同じ項目名（全角半角、大文字小文字は揃えて比べます）に、同じ単位で違う値があれば指します（単位の語彙表にある単位の量、410 g と 450 g も、期間、3ヶ月 と 6か月 も比べます。年は月に直して比べ、1年 と 12ヶ月 は同じ長さです。1か月 と 30日 のように長さの決まらない組は比べません）。年齢も値として読みます（満70歳、満70歳まで、満20歳〜満70歳）。範囲と上限（まで）は上の端で比べ、一人の年齢は範囲とは比べません。保存期間は節をまたいで比べます。「個人情報を1年間保存します」と「3年間を経過した個人情報を削除します」のように、同じもの（同じ名詞句）に二通りの長さが書いてあれば指します。文書全体で一つの値を持つ項目（語彙表 fact-document-term の名前、試用期間など）も節をまたいで比べます。表の升に「試用期間 | 3ヶ月」とあり、別の節の文が「試用期間は6ヶ月で」と書いていれば指します。項目の名前を見出しにした節（「第2条（保証期間）」）の値も、表の升と同じく拠り所にします。その項目を主語にした文は、起算の句が付いていても読みます（「本製品の保証期間は、お買い上げ日から24か月です」）。1年 と 12ヶ月 のように大きさの違う期間は比べません）。表の行の見出しをそのまま主語にした文（「入院給付金は、入院1日につき10,000円をお支払いします」）の金額も、同じ節の表のその行の金額（日額5,000円）と比べます。文が全体の数として書いた数（「チケットは、合計4枚です」）も、表のその数を数える列（枚数）と比べます。表の数は、合計の行がその列に書いた数、書いていなければ行の数の和です（発券手数料のように同じチケットを数え直す行は足しません）。
+  en: 'When one section says "Deadline: May 3" and later "Deadline: May 5", the reader cannot tell which to trust. It happens when a date or a price is changed in one place and not in the other. Values written as "Item: value" or "The item is value", and table cells, are read; the same item name (case and width aside) with two different values in the same unit within one section is pointed out (measured quantities such as 410 g and 450 g included, and lengths of time such as 3 months and 6 months; years are compared in months, so 1 year and 12 months agree, while 1 month and 30 days are not compared). Ages are values too ("aged 40", "up to the age of 70", "aged 20 to 70"): a range and an upper limit are compared by their upper ends, and one age is not compared with a range. A retention period is compared across the whole document: "we keep personal information for 1 year" and "we delete personal information 3 years after the account is closed" give one thing (the same noun phrase) two lengths. An item that has one value for the whole document (a name in the fact-document-term lexicon, such as probation period) is compared across sections too: a table cell "Probation | 3 months" and a sentence in another section "The probation period is 6 months" disagree. The value in a section headed by the item''s name ("2. Warranty period") counts like a table cell, and a sentence with the item as its subject is read even with the point it counts from ("The warranty period for the product is 24 months from the date of purchase"). Values written as "Item: value" or "The item is value", and table cells, are read; the same item name (case and width aside) with two different values in the same unit within one section is pointed out (measured quantities such as 410 g and 450 g included, and lengths of time such as 3 months and 6 months; 1 year and 12 months are not compared). A sentence whose subject is exactly a table row''s heading ("Hospital cash is paid at $150 for each day") has its amount compared with that row''s amount in the same section ($100 a day). A count a sentence states as the whole ("Your order is for 4 tickets in total") is compared with the table column that counts it (Tickets): the count in the total row, or else the sum of the rows (a row that counts the same tickets again, such as a ticketing fee, is not added).'
 
 message:
   ja: 「{label}」が {value} と書かれていますが、同じ節の前の所では {other} です
@@ -22,6 +22,18 @@ messages:
   retention:
     ja: 「{label}」の保存期間が {value} と書かれていますが、前の所では {other} です
     en: 'The retention period of "{label}" is {value} here, but {other} earlier in the document'
+  term:
+    ja: 「{label}」が {value} と書かれていますが、表では {other} です
+    en: '"{label}" is {value} here, but {other} in the table'
+  term-section:
+    ja: 「{label}」が {value} と書かれていますが、「{section}」の節では {other} です
+    en: '"{label}" is {value} here, but {other} in the section "{section}"'
+  whole-count:
+    ja: 全体の数が {value} と書かれていますが、表の「{label}」の合計の行では {other} です
+    en: 'The whole count is {value} here, but the total row of the table''s "{label}" column gives {other}'
+  whole-count-sum:
+    ja: 全体の数が {value} と書かれていますが、表の「{label}」の行を足すと {other} です
+    en: 'The whole count is {value} here, but the rows of the table''s "{label}" column add up to {other}'
 
 how_to_fix:
   ja: どちらの値が正しいかを確かめて、もう一方を直してください。別のもの（別の回、別の対象）の値なら、項目名にそれを書き分けてください（「第2回の締切」）。
@@ -62,8 +74,8 @@ example:
       - Deadline: May 3, 2026
 
 not_flagged:
-  ja: 違う見出しの下、違う親の項目の下、太字だけの行や「第2回：」のような行の後ろの値は、別のものの値として比べません。値の後ろに条件が続くもの（「3,000円から」「10月5日に開催」）、読点のあとから始まる項目名（「大人は、参加費は」）、単位の違う値（単位の食い違いは別に見ます）も比べません。同じ項目に三通り以上の値があれば、一覧として何も言いません。保存期間は、別のもの（ログは90日、個人情報は1年）や、上限・下限・目安の長さ（最長、以上、約）とは比べません。
-  en: Values under different headings, under different parent list items, or after a bold-only line or a line like "Session 2:" are taken as values of different things. A value followed by a condition ("$300 per person", "May 3 at noon"), a name that starts after a comma ("For adults, the fee"), and values in different units are not compared. An item with three or more different values is read as a list and left alone. A retention period is not compared with that of another thing (logs 90 days, account data 1 year) or with a bound or an estimate (up to, at least, about).
+  ja: 違う見出しの下、違う親の項目の下、太字だけの行や「第2回：」のような行の後ろの値は、別のものの値として比べません。値の後ろに条件が続くもの（「3,000円から」「10月5日に開催」）、読点のあとから始まる項目名（「大人は、参加費は」）、単位の違う値（単位の食い違いは別に見ます）も比べません。同じ項目に三通り以上の値があれば、一覧として何も言いません。保存期間は、別のもの（ログは90日、個人情報は1年）や、上限・下限・目安の長さ（最長、以上、約）とは比べません。文書全体の項目は、拠り所（表の升、項目の名前を見出しにした節）と文のあいだだけで比べます。表どうしや、拠り所の無い文どうし（雇用形態ごとの節）、拠り所が二通りの値を書いた項目、条件の句の後ろの値（「製品登録をされた場合、保証期間は24か月です」）、名前に条件を書いた値（正社員の試用期間）は比べません。文書全体の項目は、表の升と文のあいだだけで比べます。表どうしや文どうし（雇用形態ごとの節）、表が二通りの値を書いた項目、名前に条件を書いた値（正社員の試用期間）は比べません。表の行と主語の文の金額は、行か文に同じ通貨の金額が二つ以上あるとき（日額と上限）、期間の違う金額（日額と月額）、主語が見出しより長いとき（入院給付金の上限は）、文に条件の語（場合、ただし）があるときは比べません。全体の数は、全体の印（合計、全部で）と数える語（枚、名）の両方が付いた数だけを読みます。一部の数（うち2枚は）、上限（合計4枚まで）、表の行の名前を書いた文（S席は合計2枚）、数える列が二つ以上ある文書は比べません。人の数は行を足しません（同じ人が参加と交流会の両方の行に載ります）。
+  en: Values under different headings, under different parent list items, or after a bold-only line or a line like "Session 2:" are taken as values of different things. A value followed by a condition ("$300 per person", "May 3 at noon"), a name that starts after a comma ("For adults, the fee"), and values in different units are not compared. An item with three or more different values is read as a list and left alone. A retention period is not compared with that of another thing (logs 90 days, account data 1 year) or with a bound or an estimate (up to, at least, about). A whole-document item is compared only between its source (a table cell, or a section headed by its name) and a sentence; two tables, two sentences with no source (sections per type of employment), an item its sources give two values, a value after a condition ("If you register the product, the warranty runs for 24 months"), and a qualified name (part-time probation period) are left alone. A whole-document item is compared only between a table cell and a sentence; two tables or two sentences (sections per type of employment), an item the tables give two values, and a qualified name (part-time probation period) are left alone. A table row and a sentence naming it are not compared when either holds two amounts in the currency (a daily amount and a cap), when the amounts are for different periods (a day, a month), when the subject is longer than the heading ("Hospital cash cover is"), or when the sentence puts a condition on its amount (if, unless). A whole count is read only with a whole mark (in total, a total of) and a counting word (tickets, attendees). A part ("2 of the tickets"), a limit ("up to a total of 4 tickets"), a sentence naming a table row ("Stalls are 2 tickets in total"), and a document with two columns counting the same thing are left alone. Rows counting people are not summed, because the same guest is on the admission row and the dinner row.
 rewrite:
   depth: light
   ja:

package/rules/figurative-density.yaml

@@ -33,7 +33,7 @@ off_for:
 group: ai-tells
 summary:
   ja: 「まるで魔法のように」「呪文のような」「おまじない」のような、仕組みの代わりのたとえが多い所
-  en: Decorative figures such as "like magic", "incantation" and "secret sauce" piled up in place of the mechanism
+  en: Figures such as "like magic" or "secret sauce" piled up instead of the mechanism
 
 example:
   ja:

package/rules/figure-reference-order.yaml

@@ -43,7 +43,7 @@ off_for:
 group: structure
 summary:
   ja: 図2を図1より先に参照する、図を載せた節より後で初めて参照する、一度も参照しない図や表
-  en: A figure or table referred to before a lower-numbered one, first referred to only after its section, or never referred to
+  en: A figure or table referred to out of order, too late, or never
 example:
   ja:
     config: { genre: academic/paper }

package/rules/footnote-mismatch.yaml

@@ -35,7 +35,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: structure
 summary:
   ja: 本文の「※3」「[^3]」に対応する注が無い所と、本文のどこも指さない注
-  en: A note mark ("[^3]", "※3") with no note, or a note that nothing in the text points to
+  en: A note mark ("[^3]") with no note, or a note nothing points to
 example:
   ja:
     before: |

package/rules/formula-amount-mismatch.yaml

@@ -0,0 +1,67 @@
+id: formula-amount-mismatch
+layer: L3
+status: stable
+how_to_find: formula-amount
+# The words of a formula come from formula-amount-word and percent-unit; a tax-included word and a stated tax rate are read
+# with tax-price-column, as tax-mismatch reads them, and a tax's name with a word of inclusion (消費税8%込み) with tax-label
+# and tax-included-word. The amounts are currency-notation's. A document profile may give the
+# tax rate a label means when the document states none (tax_rate).
+extra_word_lists: [formula-amount-word, percent-unit, tax-price-column, tax-label, tax-included-word]
+severity: warning
+
+name:
+  ja: 見出しに書いた計算と合わない金額
+  en: An amount that is not what its label's formula gives
+
+why:
+  ja: 精算書や請求書で「仲介手数料（売買代金の3%＋60,000円、消費税込み）」のように見出しに計算のしかたを書くと、読み手は金額を確かめずに払います。売買代金を直して手数料を直し忘れたとき、決まった額や税を足し忘れたとき、桁を打ち間違えたときに食い違います。見出しに「名前の率%」（売買代金の3%）か「率% of 名前」（5% of the sale price）があり、行の終わりに金額が一つあるとき、文書がその名前の見出しで書いた金額（売買代金 | 48,000,000円）に率を掛け、「＋」の後の額を足して比べます。見出しが税込みと言えば、見出しの税率、無ければ文書が「消費税10%」のように書いた税率、それも無ければ文書の種類の税率を足します。
+  en: 'When a statement writes how a fee is worked out in its label ("Commission (5% of the sale price)"), readers pay it without checking. It goes wrong when the price is changed and the fee is not, when a fixed part or the tax is left out, or when a digit is mistyped. When a label holds "rate% of name" (or "name × rate%") and its line ends in one amount, the rate is applied to the amount the document labels with that name (Sale price | $324,000.00), a fixed amount after "plus" is added, and the result is compared with the line''s amount. A label saying tax is included adds the rate it states, else the one rate the document states beside a tax word.'
+
+message:
+  ja: 「{written}」が、{name}「{base}」で「{formula}」を計算した額（{expected}）と合いません
+  en: '{written} is not "{formula}" worked out on the {name} {base} ({expected})'
+
+how_to_fix:
+  ja: 元の金額と率、足す額を確かめて、金額か見出しの計算を直してください。
+  en: Check the amount it is worked out from, the rate and any fixed part, and correct the amount or the label.
+
+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: 「売買代金の3%」のような見出しの計算と合わない金額
+  en: An amount that is not what its label's formula ("5% of the sale price") gives
+example:
+  ja:
+    before: |
+      | 項目 | 金額 |
+      | --- | --- |
+      | 売買代金 | 30,000,000円 |
+      | 仲介手数料（売買代金の3%＋60,000円、消費税10%込み） | 990,000円 |
+    after: |
+      | 項目 | 金額 |
+      | --- | --- |
+      | 売買代金 | 30,000,000円 |
+      | 仲介手数料（売買代金の3%＋60,000円、消費税10%込み） | 1,056,000円 |
+  en:
+    before: |
+      | Item | Amount |
+      | --- | --- |
+      | Sale price | $250,000.00 |
+      | Commission (5% of the sale price) | $12,000.00 |
+    after: |
+      | Item | Amount |
+      | --- | --- |
+      | Sale price | $250,000.00 |
+      | Commission (5% of the sale price) | $12,500.00 |
+
+not_flagged:
+  ja: 端数は切り捨て・四捨五入・切り上げのどれでも、税の前でも後でも、円やドルの位で合っていると読みます。その名前の見出しの金額が無いもの、名前の見出しが二つあって額が違うもの、見出しに率と名前の組が二つあるもの、見出しに足す額のほかの金額があるもの、通貨が違うもの、行の金額が「165万円」のように桁の語で書いたものは比べません。税込みと書いて、見出しにも文書にも文書の種類にも税率が無いもの、文書が違う税率を二つ書いたものも比べません。文の中に書いた計算は読みません。
+  en: "Rounding down, to the nearest or up, before or after the tax, to the cent or to the unit, is read as right. Nothing is compared when no line labels the named amount, when two such lines give different amounts, when the label holds two rates with names or an amount other than the fixed part, when the currencies differ, or when the line's amount is written with a word of scale. A label saying tax is included is not compared when no rate is stated in it, in the document or in the document's profile, or when the document states two rates. A formula written in a sentence is not read."
+level_meaning:
+  ja: 金額が、見出しに書いた計算で出した額と合わないとき指摘
+  en: reported when an amount is not what its label's formula gives

package/rules/fullwidth-alnum-consistency.yaml

@@ -37,7 +37,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: consistency
 summary:
   ja: 英字や数字を、全角（ＡＢＣ１２３）と半角（ABC123）で混ぜて書いている所
-  en: Letters and digits written both full-width (ＡＢＣ１２３) and half-width (ABC123) in one Japanese document
+  en: Letters and digits both full-width (ＡＢＣ１２３) and half-width (ABC123)
 example:
   ja:
     before: |

package/rules/gpa-mismatch.yaml

@@ -0,0 +1,80 @@
+id: gpa-mismatch
+layer: L3
+status: stable
+how_to_find: gpa-mismatch
+word_list: gpa-label
+extra_word_lists: [transcript-column, grade-point]
+# The course table's columns are found by transcript-column, each grade's points by the document's own grading key or by
+# grade-point (one scale per group, weight is the points), and the written GPA by gpa-label.
+languages: [ja, en]
+severity: warning
+
+name:
+  ja: GPA が科目の評価と単位数から出る値と合わない
+  en: A grade-point average the course rows do not give
+
+why:
+  ja: 成績証明書の「GPA：3.00」は、科目ごとの評価の点（GP）に単位数を掛けた和を、単位数の和で割った値です。読み手は計算し直さずに信じます。一つの科目の評価だけを直したとき、別の学期や別の人の値を写したときに食い違います。どの列が科目・単位数・評価かは、列の見出しの語（科目、単位、評価、成績）だけで決めます。評価の点は、評価の語（評価、成績）のある行に「S（4）、A（3）」のような対応が書いてあればそれを使い、無ければ言語パッケージの語彙表 grade-point の尺度（秀・優・良・可・不可、S〜D、A〜F）を使います。文書の評価がすべて入る尺度が複数あって点が違うとき（S も D も無い A・B・C だけの表）は決まらないので比べません。認定・合・履修中のような点の無い評価の科目は、両方の和から外します。書いた GPA は、その桁までの四捨五入か切り捨てで届く差なら言いません。
+  en: 'The "GPA: 3.00" of a transcript is the sum of each course''s grade points times its credits, divided by the sum of the credits. Readers trust it without working it out again. It goes wrong when one course''s grade is corrected and the average is not, or when the average is copied from another term or another student. Which column is the course, the credits and the grade is decided by the heading words alone (Course, Credits, Grade). A grade''s points come from the document''s own grading key, a line naming grades with "A (4), B (3)", when it writes one, and otherwise from a scale of the language package''s grade-point lexicon (A to F, S to D, plus and minus grades). When the document''s grades fit several scales that give them different points (only A, B and C, with no S and no D), nothing is compared. A course with a grade that carries no points (Pass, W, In progress) is left out of both sums. A difference that rounding or cutting off to the written decimals can reach is not reported.'
+
+message:
+  ja: GPA「{gpa}」は、科目の評価と単位数からは {computed} です
+  en: 'The GPA "{gpa}" is written, but the course grades and credits give {computed}'
+
+how_to_fix:
+  ja: 科目の評価と単位数、GPA のどれが正しいかを確かめて、ほかを直してください。
+  en: Check which of the course grades, their credits and the GPA 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: GPA が、科目の評価と単位数から計算した値と合わない所
+  en: A grade-point average that is not what the course grades and credits give
+example:
+  ja:
+    before: |
+      | 科目 | 単位数 | 評価 |
+      | --- | --- | --- |
+      | 経済学入門 | 2 | S |
+      | 統計学 | 2 | A |
+      | ミクロ経済学 | 4 | B |
+
+      GPA：3.20
+    after: |
+      | 科目 | 単位数 | 評価 |
+      | --- | --- | --- |
+      | 経済学入門 | 2 | S |
+      | 統計学 | 2 | A |
+      | ミクロ経済学 | 4 | B |
+
+      GPA：2.75
+  en:
+    before: |
+      | Course | Credits | Grade |
+      | --- | --- | --- |
+      | Food Safety | 4 | B |
+      | Nutrition | 2 | C |
+      | Pastry Practicum | 6 | A |
+
+      Grades are A (4), B (3), C (2) and D (1).
+
+      GPA: 3.52
+    after: |
+      | Course | Credits | Grade |
+      | --- | --- | --- |
+      | Food Safety | 4 | B |
+      | Nutrition | 2 | C |
+      | Pastry Practicum | 6 | A |
+
+      Grades are A (4), B (3), C (2) and D (1).
+
+      GPA: 3.33
+
+not_flagged:
+  ja: GPA の見出しの行が無い文書、科目・単位数・評価の列のそろった表が無い文書は比べません。評価が尺度に無い科目、単位数が数でない科目が一つでもあれば比べません。文書の評価がすべて入る尺度で点が一つに決まらないとき、文書に書いた評価と点の対応が同じ評価に二つの点を付けるとき、使った評価の一部にしか点を付けず、その点が尺度の点と違うときも比べません。「前期GPA」のように一部の期間の GPA を書いた文書、見出しの違う GPA を書いた文書、値の違う GPA を二つ書いた文書は、どの科目の平均か分からないので比べません。合計の行は科目として数えません。四捨五入か切り捨てで届く差は言いません。
+  en: 'A document with no GPA line, or with no table that has course, credits and grade columns, is not compared; nor is one with a course whose grade is on no scale or whose credits are not a number. Nothing is compared when the grades fit scales that give them different points, when the document''s grading key gives one grade two different points, or when it gives points to only some of the grades used and those differ from the scale''s. A document that writes the GPA of one period ("Term GPA"), a GPA under another label, or two different GPAs is not compared, since it cannot be told which courses the average is of. A total row is not counted as a course. A difference that rounding or cutting off can reach is not reported.'

package/rules/heading-end-punctuation-mix.yaml

@@ -50,7 +50,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: consistency
 summary:
   ja: 記号なしの見出しの中に「準備：」「確認。」のように記号で終わる見出しが混ざっている所（またはその逆）
-  en: A heading ending with a colon or a full stop among headings that end bare, or the other way round
+  en: Headings that end with a colon or full stop mixed with headings that do not
 example:
   ja:
     before: |

package/rules/heading-level-skip.yaml

@@ -28,7 +28,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: structure
 summary:
   ja: 「##」の次に「####」が来るように、見出しの深さが一段以上飛んでいる所
-  en: A heading two or more levels deeper than the one before it, as "####" right after "##"
+  en: A heading that skips a level, such as "####" right after "##"
 example:
   ja:
     before: |

package/rules/heading-numbering-mix.yaml

@@ -49,7 +49,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: structure
 summary:
   ja: 「1. 概要」「2. 手順」「まとめ」や「1.」「2.」「3）」のように、兄弟の見出しで番号の付け方が混ざっている所
-  en: Sibling headings numbered in mixed ways, such as "1. Overview", "2. Steps", "Summary"
+  en: 'Sibling headings numbered in mixed ways: "1. Overview", "2. Steps", "Summary"'
 example:
   ja:
     before: |
@@ -111,8 +111,8 @@ example:
       The summary.
 
 not_flagged:
-  ja: 兄弟が三つ未満の所、少ないほうと多いほうが同じ数の所、深さや親の違う見出しどうし（「1.」の下の「1.1」）は比べません。前後の見出し（目次、参考文献、付録）は兄弟に数えません。見出しの頭の数でも、区切りの記号の無い数（「2026年の計画」「3つの理由」）は番号と読みません。
-  en: Fewer than three siblings, a tie between the two sides, and headings at different depths or under different parents ("1." and "1.1") are not compared. Front and back matter (Contents, References, Appendix) is not counted among the siblings. A number at the head of a heading without a separator ("2026 roadmap", "3 reasons") is not read as a heading number.
+  ja: 兄弟が三つ未満の所、少ないほうと多いほうが同じ数の所、深さや親の違う見出しどうし（「1.」の下の「1.1」）は比べません。前後の見出し（目次、参考文献、付録）は兄弟に数えません。見出しの頭の数でも、区切りの記号の無い数（「2026年の計画」「3つの理由」）は番号と読みません。期間や催しを名指す番号（「第1週」「1日目」「第3回」「Week 1」）も番号と読みません。
+  en: Fewer than three siblings, a tie between the two sides, and headings at different depths or under different parents ("1." and "1.1") are not compared. Front and back matter (Contents, References, Appendix) is not counted among the siblings. A number at the head of a heading without a separator ("2026 roadmap", "3 reasons") is not read as a heading number. Nor is a number that names a period or an event ("Week 1", "Day 2", "Phase 3", "第3回").
 rewrite:
   depth: light
   ja:

package/rules/homophone-slip.yaml

@@ -33,7 +33,7 @@ off_for:
 group: slips
 summary:
   ja: 英語で、「it's own」「their are」のように、次の語から見て取り違えたと決まる同音語
-  en: '"It''s own", "their are" and other homophones the next word shows were typed for another'
+  en: A sound-alike typed for another word, such as "it's own" or "their are"
 example:
   en:
     before: |

package/rules/humble-for-others.yaml

@@ -32,7 +32,7 @@ off_for:
 group: wording
 summary:
   ja: 「伺ってください」「拝見してください」「申される」のように、謙譲語を読み手や第三者の動作に使った所
-  en: A Japanese humble verb used for the reader's or a third party's action (伺ってください, 申される)
+  en: A Japanese humble verb used for what the reader or others do (伺ってください)
 example:
   ja:
     before: 資料は受付で拝見してください。

package/rules/idiom-misuse.yaml

@@ -32,7 +32,7 @@ off_for:
 group: wording
 summary:
   ja: 「的を得る」「汚名挽回」のように、取り違えたと決まっている慣用句
-  en: A Japanese idiom in a form dictionaries and style guides list as a mistake (的を得る for 的を射る)
+  en: A Japanese idiom in a form dictionaries list as a mistake (的を得る)
 example:
   ja:
     before: 課長の指摘は的を得ていました。

package/rules/ime-residue.yaml

@@ -28,7 +28,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: slips
 summary:
   ja: 「おもしrおい」「対応sた」のような、日本語の語の中に一字だけ残った英字
-  en: A single Latin letter left inside a Japanese word by the input method, as in おもしrおい
+  en: A stray Latin letter left inside a Japanese word by the input method
 example:
   ja:
     before: |

package/rules/impossible-date.yaml

@@ -2,6 +2,7 @@ id: impossible-date
 layer: L3
 status: stable
 how_to_find: impossible-date
+requires: [dates]
 severity: error
 
 name:
@@ -9,8 +10,8 @@ name:
   en: A date the calendar does not have
 
 why:
-  ja: 「2月30日」「4月31日」「2023年2月29日」のような日付は暦にありません。読み手は前の日か次の日か、月の書き違いかを確かめに行くことになり、予定や期限なら誰かが間違った日に動きます。月末を「31日」と決め打ちしたときや、うるう年の予定を使い回したときに起きます。月の長さとうるう年は暦で決まるので、機械で言えます。
-  en: A date such as "February 30", "April 31" or "2023-02-29" is not on the calendar. The reader has to find out whether the day before, the day after or another month was meant, and for a deadline someone acts on the wrong day. It happens when the end of a month is taken to be the 31st, or a leap-year schedule is reused. Month lengths and leap years are fixed by the calendar, so a machine can tell.
+  ja: 「2月30日」「4月31日」「2023年2月29日」のような日付は暦にありません。読み手は前の日か次の日か、月の書き違いかを確かめに行くことになり、予定や期限なら誰かが間違った日に動きます。月末を「31日」と決め打ちしたときや、うるう年の予定を使い回したときに起きます。和暦に西暦を括弧で添えた年（令和6年（2023年））が食い違えば、読み手はどちらの年か決められません。月の長さとうるう年、元号の元年は暦で決まるので、機械で言えます。
+  en: A date such as "February 30", "April 31" or "2023-02-29" is not on the calendar. The reader has to find out whether the day before, the day after or another month was meant, and for a deadline someone acts on the wrong day. It happens when the end of a month is taken to be the 31st, or a leap-year schedule is reused. When a Japanese era year and the Western year in brackets beside it disagree (令和6年（2023年）, where 令和6 is 2024), the reader cannot tell which year is meant. Month lengths, leap years and the first year of an era are fixed by the calendar, so a machine can tell.
 
 message:
   ja: 「{written}」は暦にありません（{month}月は{days}日まで）
@@ -26,6 +27,9 @@ messages:
   month:
     ja: 「{written}」は暦にありません（月は1から12まで）
     en: '"{written}" is not on the calendar (months run from 1 to 12)'
+  years:
+    ja: 「{written}」は和暦と西暦が違う年を指しています（括弧の外は{year}年、中は{glossYear}年）
+    en: '"{written}" names two different years (outside the brackets {year}, inside {glossYear})'
 
 how_to_fix:
   ja: 正しい日付を確かめて直してください。月末のつもりなら、その月の最後の日（4月30日、2月28日）を書きます。
@@ -37,8 +41,8 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
 group: facts
 summary:
-  ja: 「2月30日」「4月31日」「2023年2月29日」のように、暦に無い日付
-  en: A date the calendar does not have, such as "February 30", "April 31" or "2023-02-29"
+  ja: 「2月30日」「2023年2月29日」のような暦に無い日付と、和暦と西暦の年が食い違う日付
+  en: A date not on the calendar ("February 30"), or a year two calendars disagree on
 example:
   ja:
     before: 申込みの締切は 4月31日 です。
@@ -48,8 +52,8 @@ example:
     after: Applications close on April 30.
 
 not_flagged:
-  ja: 元号の年（令和5年）と年を書いていない日付は、うるう年を決められないので 2月29日を言いません。2026-13-45 や 2026/10/45 のような数字だけの並びは、番号や版のこともあるので、月が 1〜12、日が 31 までのときだけ月の長さと比べます。英語の月の名前の日付も、日が 31 までのときだけ見ます。コードの中は読みません。
-  en: For a year in a Japanese era, and for a date without a year, February 29 is not reported, since the leap year cannot be decided. A bare run of numbers such as 2026-13-45 may be an identifier or a version, so it is compared with the month's length only when the month is 1 to 12 and the day at most 31; a date with a month's name is likewise checked only up to the 31st. Code is not read.
+  ja: 元号の年（令和5年）と年を書いていない日付は、うるう年を決められないので 2月29日を言いません。2026-13-45 や 2026/10/45 のような数字だけの並びは、番号や版のこともあるので、月が 1〜12、日が 31 までのときだけ月の長さと比べます。英語の月の名前の日付も、日が 31 までのときだけ見ます。和暦と西暦の食い違いは暦の年だけを比べ、年度（令和6年度（2023年度））や、語彙表に元年の無い元号は読みません。コードの中は読みません。
+  en: For a year in a Japanese era, and for a date without a year, February 29 is not reported, since the leap year cannot be decided. A bare run of numbers such as 2026-13-45 may be an identifier or a version, so it is compared with the month's length only when the month is 1 to 12 and the day at most 31; a date with a month's name is likewise checked only up to the 31st. An era year and a Western year in brackets are compared only as calendar years; a fiscal year (令和6年度（2023年度）) and an era whose first year the lexicon does not give are not read. Code is not read.
 
 rewrite:
   depth: light

package/rules/installment-total-mismatch.yaml

@@ -0,0 +1,63 @@
+id: installment-total-mismatch
+layer: L3
+status: stable
+how_to_find: installment-total-mismatch
+# The amounts are read with currency-notation and amount-multiplier; the labels are installment-label, the words
+# installment-word, rough amounts approximate-marker, counts written as words number-word (digit), and ranges
+# range-connector and amount-range-word.
+severity: warning
+
+name:
+  ja: 回数×毎回の額と合わないお支払総額
+  en: A total of payments that is not the payments added up
+
+why:
+  ja: ローンや分割払いの案内で「お支払回数 60回、毎月のお支払額 32,800円、お支払総額 1,968,000円」と並べて書くと、読み手は掛け算を確かめずに総額を信じます。金利や回数を変えて作り直したときに、毎回の額か総額のどちらかが古いまま残って食い違います。支払回数・毎回のお支払額・お支払総額の見出しにそれぞれ一つの額があるとき、回数×毎回の額をお支払総額と比べます。初回や最終回の額が別に書いてあれば「初回 + 毎回の額 ×（残りの回数）+ 最終回」で比べます。見出しが無くても、一つの文に「32,800円×59回」のような回数と額の組があれば、それを足して比べます。毎回の額は、書いた桁の半分までの丸めが回数分たまることを認めます。修学旅行や林間学校の案内のように「第1回：32,000円」「第2回：30,000円」と分納を表の行や箇条書きで並べ、同じ節に「旅行代金は、1人あたり62,000円」と費用を書いたときは、分納の額を足して費用と比べます。
+  en: 'When a loan or installment plan says "48 monthly payments of $537.50; total of payments $25,800", readers trust the total without multiplying. It goes wrong when the plan is redone with another rate or term and the payment or the total is left as it was. When the number of payments, the regular payment and the total of payments are each stated once, the number times the payment is compared with the total; a first or final payment stated apart is added as written (first + payment × the rest + final). Without labels, the payments of one sentence ("47 payments of $550.53 and 1 payment of $550.71") are added up. Each regular payment may be rounded by half its last written digit. When a school trip or camp notice lists numbered instalments as table rows or list items ("1st payment: £150", "Final payment: $60") and states the cost in the same section ("The trip costs £300 per student"), the instalments are added up and compared with the cost.'
+
+message:
+  ja: 支払額を足すと {payments} = {sum} で、お支払総額 {total} と合いません
+  en: "The payments add up to {sum} ({payments}), not the total of payments {total}"
+
+messages:
+  fee:
+    ja: 分納の額を足すと {payments} = {sum} で、同じ節に書いた費用 {total} と合いません
+    en: "The instalments add up to {sum} ({payments}), not the cost {total} stated with them"
+
+how_to_fix:
+  ja: 回数・毎回の額・総額のどれが正しいかを確かめて、ほかを直してください。端数を初回や最終回で調整するなら、その回の額を書いてください。
+  en: Check which of the number of payments, the payment and the total is right, and correct the others. If a first or final payment absorbs the rounding, state its amount.
+
+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: 「60回、毎月32,800円」とお支払総額が合わない支払いの案内
+  en: A total of payments that is not the number of payments times the payment
+example:
+  ja:
+    before: |
+      - お支払回数：24回
+      - 毎月のお支払額：10,600円
+      - お支払総額：249,600円
+    after: |
+      - お支払回数：24回
+      - 毎月のお支払額：10,400円
+      - お支払総額：249,600円
+  en:
+    before: |
+      - Number of payments: 24
+      - Monthly payment: $106.00
+      - Total of payments: $2,496.00
+    after: |
+      - Number of payments: 24
+      - Monthly payment: $104.00
+      - Total of payments: $2,496.00
+
+not_flagged:
+  ja: 総額の書いていない文書、「約」「程度」の付いた額、「32,800円〜33,000円」のような幅、同じ見出しに違う値が二度ある（いくつかの支払い方を並べた）文書、回数と額の組が文ごとに違う文書、一つの文に「12回×10,000円または24回×6,000円」のように繰り返す支払いが二つある（選べる支払い方を並べた）記載は比べません。ボーナス払い・頭金・残価・据置のある文書と、「端数は初回で調整」のように端数の扱いを書いて初回・最終回の額を書いていない文書も比べません。通貨の違う額は比べません。表の列見出しだけに「回数」「総額」とある表は読みません。分納の並びは、費用が節に一つだけ書いてあり、第1回から番号が抜けも重なりもなく続き、どの回も額が一つだけ読め、節に積立金・分納などの語があるときだけ比べます。申込金は分納の一つとして並べたときだけ足し、ほかの所に書いてあれば比べません。
+  en: 'A document with no total of payments, an amount marked "about" or "up to", a range ("$540 to $560"), a label stated twice with different values (plans side by side), sentences of payments that differ from one another, and a sentence with two repeated payments ("12 payments of $100 or 24 payments of $60", a choice) are not compared. Neither is a document with a bonus, balloon, down payment, deposit or deferred payment, nor one that says a payment absorbs the rounding ("the final payment may vary") without stating that payment. Amounts in different currencies are not compared. A table that names the count and the total only in its column headings is not read. Numbered instalments are compared only when their section states one cost, they run from the first with no gap or repeat, each has one amount, and the section speaks of payments or instalments. A deposit is added only when listed as one of the instalments; named anywhere else, nothing is compared.'

package/rules/interest-mismatch.yaml

@@ -0,0 +1,50 @@
+id: interest-mismatch
+layer: L3
+status: stable
+how_to_find: interest
+# The interest, balance, rate, after-tax and period words come from the language's interest-label lexicon. The arithmetic
+# (balance × rate, rounded down, to nearest or up) is tax-mismatch's.
+extra_word_lists: [interest-label]
+severity: warning
+
+name:
+  ja: 利息が残高に利率を掛けた額と合わない
+  en: An interest amount that is not the stated balance times the stated rate
+
+why:
+  ja: 預金の明細に「対象残高400,000円 × 利率0.10% ＝ 400円」と利息の計算を書いたなら、読み手は残高と利率から利息を確かめられます。利率を打ち間違えたとき、残高だけを直したとき、別の月の額を写したときに、書いた利息と計算が合わなくなります。一つの行に、残高の語（残高、元本）の後の金額、×、利率の語（利率、年利）の後の率、＝、利息の額と書いた行を読み、利息の語（利息、利子）がある行だけを比べます。利率は書いたとおりの率で掛けます。年利のように期間を書いた利率は、利息の期間（年間）も同じと書いた行だけで比べ、日割りや月割りには直しません。
+  en: 'When a deposit statement writes the interest out as "average balance $3,600.00 × rate 0.05% = $1.80", a reader can check the interest from the balance and the rate. It goes wrong when the rate is mistyped, when only the balance is corrected, or when another month''s amount is copied. A line is read when it writes an amount after a balance word (balance, principal), ×, a percentage after a rate word (rate, APR), =, and the interest, and names the interest (interest). The rate is used as written. A rate marked for a period (APR, annual) is used only on a line that names the same period for the interest (for the year): it is never converted to a month or a day.'
+
+message:
+  ja: 利息「{written}」が、残高「{base}」に利率{rate}を掛けた額（{expected}）と合いません
+  en: "The interest {written} is not the balance {base} at {rate} ({expected})"
+
+how_to_fix:
+  ja: 残高と利率を確かめて、利息を計算し直してください。
+  en: Check the balance and the rate, and work the interest out again.
+
+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: Interest on a statement that is not the stated balance times the stated rate
+example:
+  ja:
+    before: |
+      お利息の計算：対象残高400,000円 × 利率0.01% ＝ 400円
+    after: |
+      お利息の計算：対象残高400,000円 × 利率0.10% ＝ 400円
+  en:
+    before: |
+      Interest for the month: average balance $3,600.00 × rate 0.50% = $1.80
+    after: |
+      Interest for the month: average balance $3,600.00 × rate 0.05% = $1.80
+
+not_flagged:
+  ja: 端数は切り捨て・四捨五入・切り上げのどれでも、円の位でも合っていると読みます。×と＝が一つずつでない行（日数を掛ける行など）、利率が読めないもの、残高と利息の単位が違うもの、税引後・手取りの利息の行は比べません。年利など期間を書いた利率で、利息の期間を書いていない行や違う期間の行も比べません。表の中の数や、文の中に別々に書いた残高と利率は読みません。
+  en: "Rounding down, to the nearest or up, to the cent or (for an amount written without cents) to the unit, is read as right. Nothing is compared on a line without exactly one × and one = (one that also multiplies by days), with no rate to read, with the balance and the interest in different units, or that names interest after tax (after tax, net interest). A rate marked for a period (APR) is not compared on a line that names no period, or another one, for the interest. Figures in a table, and a balance and a rate written apart in sentences, are not read."

package/rules/interval-count-mismatch.yaml

@@ -36,7 +36,7 @@ off_for:
 group: facts
 summary:
   ja: 「8時間以上あけ、1日4回まで」のように、間隔の下限と回数の上限が両立しない所と、上限の回数が表の回数と違う所
-  en: A minimum interval and a maximum count that cannot both hold, and a maximum count that differs from the table's
+  en: A minimum gap and maximum count that conflict, or a maximum unlike the table's
 example:
   ja:
     before: |

package/rules/invisible-character.yaml

@@ -47,7 +47,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: slips
 summary:
   ja: ゼロ幅の空白、途中の BOM、ソフトハイフン、文字の向きの指定、制御文字、隠れたタグ文字のような、画面に出ない字
-  en: Characters that do not show on screen, such as a zero-width space, a stray byte order mark, a soft hyphen, a direction mark or hidden tag characters
+  en: Characters that do not show on screen, such as a zero-width space
 example:
   ja:
     before: "申込書は\u200B総務課へ送ってください。\n"

package/rules/kana-function-word.yaml

@@ -40,8 +40,8 @@ sources: [koyobun-2022]
 
 group: wording
 summary:
-  ja: 公用文でかなで書く補助動詞・形式名詞（〜て下さい、〜て置く、〜する事）を漢字で書いた所。style が koyobun のときだけ
-  en: A Japanese helper verb or formal noun written in kanji where official style writes kana (〜て下さい, 〜て置く, 〜する事); only with the koyobun style
+  ja: 公用文でかなで書く語（〜て下さい、〜する事）を漢字で書いた所（style が koyobun のとき）
+  en: Kanji where Japanese official style writes kana (〜て下さい); koyobun style only
 example:
   ja:
     config: { style: koyobun }

package/rules/katakana-density.yaml

@@ -31,7 +31,7 @@ use_for: [blog, business, legal, docs, academic, literature, speech]
 group: wording
 summary:
   ja: 「アジェンダ」「エビデンス」のようなカタカナ語が、人の書いた技術記事より多い文書
-  en: A Japanese document with more katakana loanwords per 1000 characters than human-written technical articles
+  en: A Japanese document with more katakana loanwords than human-written articles
 example:
   ja:
     before: |