chaffjs 0.30.0 → 0.32.0

package/rules/duration-mismatch.yaml

@@ -10,8 +10,8 @@ name:
   en: A start plus a length of time that does not reach the stated end
 
 why:
-  ja: 「4月1日から3か月間（7月31日まで）」のように、始まりと期間と終わりを一緒に書くと、読み手は三つのうちどれが正しいのか分かりません。期間か日付の片方だけを直したときに起きます。一つの文に日付が二つと期間が一つあるとき、始まりに期間を足した日を終わりと比べます。終わりの日を含めて数える書き方（4月1日から3か月間は6月30日まで）、含めない書き方（7月1日まで）、初日を数えずに期間が過ぎた日（「4月1日から2週間が経過した日（4月16日）」）のどれとも合わないときだけ指します。泊数は二つの日付の差の日数と比べます（10月12日から10月14日までは2泊）。一つの文に日付が二つと泊数が一つある所と、チェックイン・チェックアウト・泊数の列がそろった表の行を見ます。「2泊3日」のように泊数と日数を並べたら、日数は泊数より一つ多いはずです。勤務時間（9:00〜17:30、休憩1時間、実働8時間）は、終わりから始まりと休憩を引いた時間を実働と比べます。
-  en: 'When a start, a length and an end are written together ("for 3 months from April 1, 2026, until July 31, 2026"), the reader cannot tell which of the three is right. It happens when the length or one date is changed and not the other. In a sentence with two dates and one length of time, the start plus the length is compared with the end. Three ways of counting are accepted: with the last day included (April 1 plus 3 months is June 30), without it (July 1), and the day after the period has passed when the first day is not counted (July 2); it is pointed out only when the end matches none. A number of nights is compared with the days between two dates (Oct 12 to Oct 14 is 2 nights), in a sentence with two dates and one number of nights, and in each row of a table with check-in, check-out and nights columns. Where nights and days are written together ("2 days, 1 night"), the days must be one more than the nights. Working hours ("9:00–17:30 with a 1-hour break, 8 hours a day") are checked by taking the start and the break from the end and comparing what is left with the stated hours.'
+  ja: 「4月1日から3か月間（7月31日まで）」のように、始まりと期間と終わりを一緒に書くと、読み手は三つのうちどれが正しいのか分かりません。期間か日付の片方だけを直したときに起きます。一つの文に日付が二つと期間が一つあるとき、始まりに期間を足した日を終わりと比べます。終わりの日を含めて数える書き方（4月1日から3か月間は6月30日まで）、含めない書き方（7月1日まで）、初日を数えずに期間が過ぎた日（「4月1日から2週間が経過した日（4月16日）」）のどれとも合わないときだけ指します。泊数は二つの日付の差の日数と比べます（10月12日から10月14日までは2泊）。一つの文に日付が二つと泊数が一つある所と、チェックイン・チェックアウト・泊数の列がそろった表の行を見ます。「2泊3日」のように泊数と日数を並べたら、日数は泊数より一つ多いはずです。勤務時間（9:00〜17:30、休憩1時間、実働8時間）は、終わりから始まりと休憩を引いた時間を実働と比べます。勤務表（始業・終業・休憩・実働の列、または作業時間の範囲・休憩・稼働の列）は行ごとに同じように比べ、休憩が勤務より長い行も指します。
+  en: 'When a start, a length and an end are written together ("for 3 months from April 1, 2026, until July 31, 2026"), the reader cannot tell which of the three is right. It happens when the length or one date is changed and not the other. In a sentence with two dates and one length of time, the start plus the length is compared with the end. Three ways of counting are accepted: with the last day included (April 1 plus 3 months is June 30), without it (July 1), and the day after the period has passed when the first day is not counted (July 2); it is pointed out only when the end matches none. A number of nights is compared with the days between two dates (Oct 12 to Oct 14 is 2 nights), in a sentence with two dates and one number of nights, and in each row of a table with check-in, check-out and nights columns. Where nights and days are written together ("2 days, 1 night"), the days must be one more than the nights. Working hours ("9:00–17:30 with a 1-hour break, 8 hours a day") are checked by taking the start and the break from the end and comparing what is left with the stated hours. A timesheet (Start, End, Break and Hours columns, or one cell holding the time range beside Break and Hours) is checked row by row the same way, and a break longer than the shift is pointed out.'
 
 message:
   ja: "{start}から{duration}なら、終わりは{expected}ごろのはずですが、{end}と書かれています"
@@ -25,8 +25,17 @@ messages:
     ja: "{nights}なら日数は{expected}日のはずですが、{days}と書かれています"
     en: "{nights} makes {expected} days, but {days} is written"
   working-hours:
-    ja: "{start}から{end}まで、休憩{break}を除くと{expected}時間のはずですが、{total}と書かれています"
-    en: "{start} to {end} less a break of {break} makes {expected} hours, but {total} is written"
+    ja: "{start}から{end}まで、休憩{break}を除くと{hours}時間{minutes}分のはずですが、{total}と書かれています"
+    en: "{start} to {end} less the break ({break}) makes {hours} {hours|hour|hours} {minutes} {minutes|minute|minutes}, but {total} is written"
+  working-hours-hours:
+    ja: "{start}から{end}まで、休憩{break}を除くと{hours}時間のはずですが、{total}と書かれています"
+    en: "{start} to {end} less the break ({break}) makes {hours} {hours|hour|hours}, but {total} is written"
+  working-hours-minutes:
+    ja: "{start}から{end}まで、休憩{break}を除くと{minutes}分のはずですが、{total}と書かれています"
+    en: "{start} to {end} less the break ({break}) makes {minutes} {minutes|minute|minutes}, but {total} is written"
+  working-hours-break-longer:
+    ja: "休憩{break}が、{start}から{end}までの勤務より長くなっています"
+    en: "The break ({break}) is longer than the shift from {start} to {end}"
 
 how_to_fix:
   ja: 期間と終わりの日付のどちらが正しいかを確かめて、もう一方を直してください。
@@ -39,7 +48,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: facts
 summary:
   ja: 「4月1日から3か月間（7月31日まで）」のように、始まりに期間を足しても書いた終わりにならない所
-  en: A start date plus a length of time that does not reach the end date written beside them
+  en: A start date plus a length of time that does not reach the end date given
 example:
   ja:
     before: |
@@ -53,8 +62,8 @@ example:
       The trial runs for 3 months from April 1, 2026 (until June 30, 2026).
 
 not_flagged:
-  ja: 三通りの数え方（終わりを含める、含めない、初日を数えずに過ぎた日）のどれとも合わないときだけ指します。「約3か月」「3か月程度」のような目安の期間、日付が三つ以上か期間が二つ以上ある文、年を書いた日付と書かない日付の組は見ません。「最大3泊」のような目安の泊数と、日付の無い泊数も見ません。勤務時間は、実働の書いていない所、長さの無い休憩（休憩あり）、一行に時間の範囲が二つ以上ある所（シフト表は行ごとに実働を書いた行だけ）、「翌」などの印の無い日をまたぐ範囲を見ません。
-  en: Only an end that matches none of the three ways of counting is pointed out. A rough length ("about 3 months"), a sentence with three or more dates or two or more lengths, and a pair of one date with a year and one without are left alone. So are a rough number of nights ("up to 3 nights") and nights written without dates. Working hours are left alone without a stated total, with a break of no length ("breaks provided"), with two or more ranges of time on a line (a shift table only on rows that state their own hours), and across midnight without a next-day mark.
+  ja: 三通りの数え方（終わりを含める、含めない、初日を数えずに過ぎた日）のどれとも合わないときだけ指します。「約3か月」「3か月程度」のような目安の期間、日付が三つ以上か期間が二つ以上ある文、年を書いた日付と書かない日付の組は見ません。「最大3泊」のような目安の泊数と、日付の無い泊数も見ません。勤務時間は、実働の書いていない所、長さの無い休憩（休憩あり）、一行に時間の範囲が二つ以上ある所（シフト表は行ごとに実働を書いた行だけ）、「翌」などの印の無い日をまたぐ範囲を見ません。勤務表は、休憩か実働の列の無い表、読めない升（休憩なし、単位の無い休憩の数、片方にだけ午前・午後を書いた時刻）のある行、夜勤などの印の無い文書で日をまたぐ行を見ません。
+  en: Only an end that matches none of the three ways of counting is pointed out. A rough length ("about 3 months"), a sentence with three or more dates or two or more lengths, and a pair of one date with a year and one without are left alone. So are a rough number of nights ("up to 3 nights") and nights written without dates. Working hours are left alone without a stated total, with a break of no length ("breaks provided"), with two or more ranges of time on a line (a shift table only on rows that state their own hours), and across midnight without a next-day mark. In a timesheet, a table without a Break or an Hours column, a row with a cell that cannot be read exactly (no break, a bare number of break, a.m. or p.m. on only one time), and a row across midnight in a document that does not mention night work are left alone.
 rewrite:
   depth: light
   ja:

package/rules/duration-product-mismatch.yaml

@@ -15,8 +15,16 @@ why:
   en: 'When a count of sessions, the length of one and the total are written together ("90 minutes per session, 15 sessions, 24 hours in total"), the reader cannot tell which of the three is right (15 sessions of 90 minutes make 22.5 hours). It happens when the count or the length is changed and the total is not. In one line, or one list, holding exactly one count, one length and one total, the count times the length is compared with the total.'
 
 message:
-  ja: "{length}×{count}なら合計は{expected}時間のはずですが、{total}と書かれています"
-  en: "{count} of {length} make {expected} hours, but the total is given as {total}"
+  ja: "{length}×{count}なら合計は{hours}時間{minutes}分のはずですが、{total}と書かれています"
+  en: "{count} of {length} make {hours} {hours|hour|hours} {minutes} {minutes|minute|minutes}, but the total is given as {total}"
+
+messages:
+  hours:
+    ja: "{length}×{count}なら合計は{hours}時間のはずですが、{total}と書かれています"
+    en: "{count} of {length} make {hours} {hours|hour|hours}, but the total is given as {total}"
+  minutes:
+    ja: "{length}×{count}なら合計は{minutes}分のはずですが、{total}と書かれています"
+    en: "{count} of {length} make {minutes} {minutes|minute|minutes}, but the total is given as {total}"
 
 how_to_fix:
   ja: 回数・1回の長さ・合計のどれが正しいかを確かめて、残りを直してください。
@@ -29,7 +37,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: facts
 summary:
   ja: 「90分×15回（計24時間）」のように、回数と1回の長さを掛けても書いた合計にならない所
-  en: A count of sessions times the length of one that does not make the total written beside them
+  en: Sessions times the length of each that does not make the total given
 example:
   ja:
     before: |

package/rules/elapsed-years-mismatch.yaml

@@ -10,13 +10,18 @@ name:
   en: A count of years that does not match its starting year
 
 why:
-  ja: 「2015年創業」と書いた文書の「創業5年」や、「1980年生まれ（30歳）」は、どちらかが古いままです。去年の文書を写して日付だけ直したときによく起きます。文書の日付（日付だけの段落や「更新日：」の段落）の年から起点の年を引き、書いた年数と比べます。誕生日の前後や「10年目」の数え方があるので、一年までの違いは指しません。英語の文書で語で書いた年数（ten years since its founding）も読みます。
-  en: 'A document that says "founded in 2015" and "5 years since its founding", or "born in 1980 (aged 30)", has kept one figure from an older version. It happens when last year''s document is copied and only the date is changed. The starting year is taken from the document''s own date (a paragraph holding only a date, or "Updated:") and compared with the count of years. A difference of one year is not pointed out, because of birthdays and of counting the tenth year as 10. A count written as a word ("ten years since its founding") is read as well.'
+  ja: 「2015年創業」と書いた文書の「創業5年」や、「1980年生まれ（30歳）」は、どちらかが古いままです。去年の文書を写して日付だけ直したときによく起きます。文書の日付（日付だけの段落や「更新日：」の段落）の年から起点の年を引き、書いた年数と比べます。誕生日の前後や「10年目」の数え方があるので、一年までの違いは指しません。英語の文書で語で書いた年数（ten years since its founding）も読みます。「生年月日：1978年4月12日（受診時 48歳）」のように生年月日のラベルの横に書いた年齢は、受診日・報告日などラベルの付いた日の満年齢を計算して比べます（誕生日の前日までは一つ少なく数えます）。「受診時」と書いてあれば受診日で数えます。
+  en: 'A document that says "founded in 2015" and "5 years since its founding", or "born in 1980 (aged 30)", has kept one figure from an older version. It happens when last year''s document is copied and only the date is changed. The starting year is taken from the document''s own date (a paragraph holding only a date, or "Updated:") and compared with the count of years. A difference of one year is not pointed out, because of birthdays and of counting the tenth year as 10. A count written as a word ("ten years since its founding") is read as well. An age written beside a labelled date of birth ("Date of birth: March 2, 1969 (age 57)") is compared exactly with the age on a labelled date such as "Examination date" or "Report date", one less before the birthday; "at examination" picks the examination date.'
 
 message:
   ja: "{origin}から{reference}年までは{expected}年ですが、「{written}」と書かれています"
   en: 'From {origin} to {reference} is {expected} years, but the text says "{written}"'
 
+messages:
+  birth-date:
+    ja: "{birth}生まれは{reference}に満{expected}歳ですが、「{written}」と書かれています"
+    en: 'Someone born on {birth} is {expected} on {reference}, but the text says "{written}"'
+
 how_to_fix:
   ja: 年数と起点の年のどちらが正しいかを確かめて、もう一方を直してください。毎年変わる年数は、起点の年だけを書く手もあります。
   en: Check whether the count or the starting year is right and correct the other. A count that changes every year can be replaced by the starting year alone.
@@ -29,8 +34,8 @@ off_for:
 
 group: facts
 summary:
-  ja: 「2015年創業」と「創業5年」、「1980年生まれ」と「30歳」のように、文書の日付から計算した年数と合わない所
-  en: A count of years ("10 years since its founding", "aged 30") that does not match its starting year and the document's date
+  ja: 「2015年創業」と「創業5年」のように、起点の年や生年月日から計算した年数・年齢と合わない所
+  en: A count of years or an age that does not match its starting year or birth date
 example:
   ja:
     before: |
@@ -52,8 +57,8 @@ example:
       Jane Doe (born in 1980, aged 46) leads the team.
 
 not_flagged:
-  ja: 文書に日付（日付だけの段落か「更新日：」の段落）が無ければ、比べる年が無いので見ません。一年までの違い、起点の語に直接付いていない年数（「創業後3年で上場」）、生まれた年と年齢が一つの文に一つずつでないものも見ません。
-  en: A document with no date of its own (a paragraph holding only a date, or "Updated:") has no year to count to and is not checked. A difference of one year, a count not attached to the origin word ("listed 3 years after its founding"), and a sentence without exactly one year of birth and one age are left alone.
+  ja: 文書に日付（日付だけの段落か「更新日：」の段落）が無ければ、比べる年が無いので見ません。一年までの違い、起点の語に直接付いていない年数（「創業後3年で上場」）、生まれた年と年齢が一つの文に一つずつでないものも見ません。生年月日の横の年齢は、数える日（受診日、報告日、時点など）が無いか一つに決まらないとき（受診日が二つ）、年齢が目安（約48歳）のとき、生年月日に年が無いときは見ません。
+  en: A document with no date of its own (a paragraph holding only a date, or "Updated:") has no year to count to and is not checked. A difference of one year, a count not attached to the origin word ("listed 3 years after its founding"), and a sentence without exactly one year of birth and one age are left alone. An age beside a date of birth is left alone when the date to count to (Examination date, Report date, As of) is missing or not one date (two examination dates), when the age is approximate, or when the date of birth has no year.
 rewrite:
   depth: light
   ja:

package/rules/email-greeting-closing.yaml

@@ -76,8 +76,8 @@ example:
       Best regards,
       Ichiro
 not_flagged:
-  ja: 引用した返信（「>」の行）と、ヘッダーと署名（「-- 」の後ろ）は見ません。挨拶と結びの言い方は決めず、語彙表のどれかがあれば足ります。メール・手紙のジャンルでだけ見ます。
-  en: 'Quoted replies (lines starting with ">"), the header and the signature after "-- " are not read. Which greeting or closing is used is not decided; any word in the lexicon will do. Only the email and letter genre runs this rule.'
+  ja: 引用した返信（「>」の行）と、ヘッダーと署名（「-- 」の後ろ）は見ません。手紙の頭（日付、「保護者各位」のような宛名、差出人、表題）のように文で終わらない行が続くときは、挨拶をその後ろの最初の文までに探します。挨拶と結びの言い方は決めず、語彙表のどれかがあれば足ります。メール・手紙のジャンルでだけ見ます。
+  en: 'Quoted replies (lines starting with ">"), the header and the signature after "-- " are not read. When a letter opens with lines that end no sentence (the date, the address block, the sender, a title), the greeting is looked for up to the first sentence after them. Which greeting or closing is used is not decided; any word in the lexicon will do. Only the email and letter genre runs this rule.'
 rewrite:
   depth: light
   ja:

package/rules/empty-conclusion.yaml

@@ -41,7 +41,7 @@ use_for: [blog, business/report, business/proposal]
 group: wording
 summary:
   ja: 本文をなぞるだけで、読み手に何も残さない結び（AI に読ませる検査）
-  en: A conclusion that only restates the body and leaves the reader nothing (checked by an AI)
+  en: A conclusion that only repeats the body and leaves nothing (read by an AI)
 example:
   ja:
     before: |

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,13 +11,30 @@ name:
   en: One item given two different values
 
 why:
-  ja: 同じ節の中で「締切：10月5日」と「締切：10月7日」のように、同じ項目に違う値を書くと、読み手はどちらを信じればよいか分かりません。日程や料金を直したときに、一か所だけ直し忘れると起きます。「項目：値」「項目は値です」と書いた所と表の升を読み、同じ節で同じ項目名（全角半角、大文字小文字は揃えて比べます）に、同じ単位で違う値があれば指します。
-  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.'
+  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} です
   en: '"{label}" is {value} here, but {other} earlier in the same section'
 
+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回の締切」）。
   en: Check which value is right and correct the other. If they are values of different things (another session, another group), say so in the item name ("Second session deadline").
@@ -57,8 +74,8 @@ example:
       - Deadline: May 3, 2026
 
 not_flagged:
-  ja: 違う見出しの下、違う親の項目の下、太字だけの行や「第2回：」のような行の後ろの値は、別のものの値として比べません。値の後ろに条件が続くもの（「3,000円から」「10月5日に開催」）、読点のあとから始まる項目名（「大人は、参加費は」）、単位の違う値（単位の食い違いは別に見ます）も比べません。同じ項目に三通り以上の値があれば、一覧として何も言いません。
-  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.
+  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/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-echo.yaml

@@ -10,8 +10,8 @@ name:
   en: Heading echoed
 
 why:
-  ja: 見出しで言ったことを次の文が繰り返すと、読者はそこで何も受け取れません。
-  en: When the first sentence repeats the heading, the reader gains nothing by reading on.
+  ja: 見出しで言ったことを次の文が繰り返すと、読者はそこで何も受け取れません。見出しに無い数（金額・番号・日付）を述べる文は、見出しの語を繰り返していても中身を渡しているので指摘しません。
+  en: When the first sentence repeats the heading, the reader gains nothing by reading on. A sentence that states a figure the heading does not have (an amount, a number, a date) gives the content even when it repeats the heading, and is not reported.
 
 message:
   ja: 見出し「{heading}」を直後の文がほぼそのまま繰り返しています

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