chaffjs 0.30.0 → 0.32.0

package/rules/installment-total-mismatch.yaml

@@ -0,0 +1,58 @@
+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回」のような回数と額の組があれば、それを足して比べます。毎回の額は、書いた桁の半分までの丸めが回数分たまることを認めます。
+  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.'
+
+message:
+  ja: 支払額を足すと {payments} = {sum} で、お支払総額 {total} と合いません
+  en: "The payments add up to {sum} ({payments}), not the total of payments {total}"
+
+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円」のように繰り返す支払いが二つある（選べる支払い方を並べた）記載は比べません。ボーナス払い・頭金・残価・据置のある文書と、「端数は初回で調整」のように端数の扱いを書いて初回・最終回の額を書いていない文書も比べません。通貨の違う額は比べません。表の列見出しだけに「回数」「総額」とある表は読みません。
+  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.'

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

@@ -0,0 +1,54 @@
+id: interval-count-mismatch
+layer: L3
+status: stable
+how_to_find: interval-count-mismatch
+# The interval is a length (unit-time) marked as a minimum and named an interval by use-interval-word; the count and its
+# limit come from use-count-word; the table column headings from use-interval-word (column).
+severity: warning
+
+name:
+  ja: 使う間隔の下限と回数の上限が両立しない、または表の回数と合わない
+  en: A minimum interval and a maximum count of uses that cannot both hold, or a count that differs from the table
+
+why:
+  ja: 「8時間以上あけ、1日4回まで」と書くと、4回を8時間ずつあけるには最初から最後まで24時間かかり、4回目は次の日になります。どちらかの数を書き間違えています。n回を少なくともh時間ずつあけて使うと、1回目からn回目までに(n−1)×h時間かかります。これが期間の長さ（1日なら24時間）以上なら、その期間にn回は使えません。一つの段落に、下限の間隔（4時間以上あけ、at least 4 hours between doses）と、上限のある期間あたりの回数（1日6回を超えて、no more than 6 doses a day）がちょうど一つずつあるときに計算します。両立するときは、同じ見出しの下の表に期間あたりの回数の列（1日の服用回数）があれば、その列のいちばん大きい回数と上限の回数を比べ、違えば知らせます。表が「1日3回」なのに上限が「1日6回」だと、読み手はどちらに従うか決められません。
+  en: 'Written "leave at least 8 hours between doses, no more than 4 doses a day", four doses 8 hours apart take 24 hours from the first to the last, so the fourth falls on the next day: one of the numbers is wrong. n uses at least h hours apart take (n − 1) × h hours from the first to the last; when that is the length of the period (24 hours for a day) or more, n uses do not fit in it. This is worked out in a paragraph holding exactly one minimum interval ("at least 4 hours between doses") and exactly one count of uses in a period with a limit ("no more than 6 doses a day"). When the two can hold, a table under the same heading with a column of uses in a period ("Times a day") is read too, and its largest count is compared with the limit; a table of 3 times a day beside a limit of 6 leaves the reader unable to tell which to follow.'
+
+message:
+  ja: 「{count}」を{interval}以上ずつあけて使うと、最初から最後まで{needed}時間かかり、{hours}時間に収まりません
+  en: "{count} at least {interval} apart take {needed} hours from the first to the last, which does not fit in {hours} hours"
+
+messages:
+  table:
+    ja: 表の「{column}」はいちばん多くて{table}回ですが、ここでは「{count}」と書かれています
+    en: 'The table gives at most {table} under "{column}", but "{count}" is written here'
+
+how_to_fix:
+  ja: 間隔・回数・表のどれが正しいかを確かめて、残りを直してください。
+  en: Check which of the interval, the count and the table is right and correct the rest.
+
+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: 「8時間以上あけ、1日4回まで」のように、間隔の下限と回数の上限が両立しない所と、上限の回数が表の回数と違う所
+  en: A minimum gap and maximum count that conflict, or a maximum unlike the table's
+example:
+  ja:
+    before: |
+      与える間隔は8時間以上あけ、1日4回を超えて与えないでください。
+    after: |
+      与える間隔は8時間以上あけ、1日2回を超えて与えないでください。
+  en:
+    before: |
+      Leave at least 8 hours between feedings, and do not give more than 4 feedings a day.
+    after: |
+      Leave at least 8 hours between feedings, and do not give more than 2 feedings a day.
+
+not_flagged:
+  ja: 間隔に「以上」のような下限の印が無い所、間隔の語（間隔、あけ）が同じ文に無い所、回数に上限の語（まで、を超えて）が無い所、段落に間隔か回数が二つ以上ある所、ちょうど収まる所（4時間以上あけて1日6回）は言いません。表とは、同じ見出しの下に回数の列が一つだけあり、期間が同じときだけ比べます。
+  en: 'A length with no mark of a minimum ("at least"), no interval word ("between", "apart") in its sentence, a count with no limit word ("no more than", "up to"), a paragraph with two intervals or two counts, and a count that just fits (at least 4 hours apart, 6 a day) are not reported. A table is compared only when exactly one count column for the same period stands under the same heading.'

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: |

package/rules/katakana-long-vowel.yaml

@@ -82,8 +82,8 @@ sources: [koyobun-2022, gairaigo-1991, jis-z8301-2019, jtf-style-guide]
 
 group: consistency
 summary:
-  ja: カタカナ語の語末の「ー」を、同じ語で付けたり省いたりしている所（コンピューターとコンピュータ）。options で省く・付けるを決めることもできます
-  en: A katakana word written both with and without its final ー in one document (コンピューター and コンピュータ); options can set which way
+  ja: カタカナ語の語末の「ー」を、同じ語で付けたり省いたりしている所（コンピューター、コンピュータ）
+  en: A katakana word written both with and without its final ー (コンピューター, コンピュータ)
 example:
   ja:
     before: |

package/rules/kutoten-consistency.yaml

@@ -37,7 +37,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: consistency
 summary:
   ja: 読点の「、」と「，」、句点の「。」と「．」が、一つの文書の中で混ざっている所
-  en: Japanese commas written both 、 and ，, or periods written both 。 and ．, in one document
+  en: Japanese commas or periods written two ways (、 and ，, 。 and ．)
 example:
   ja:
     before: |

package/rules/latin-spacing.yaml

@@ -10,15 +10,29 @@ uses: [pos]
 # 日付・時刻（9月、2026年、令和8年、10時5分）を、長さ（3ヶ月、3 時間）と分ける。
 # 番号と組んで名前を付ける語（問3、第1節）を見分ける。
 # 建物の名前の後ろに空白で区切った階・部屋の番号（本社 5階）を見分ける。
-extra_word_lists: [prefecture-unit, date-time-unit, calendar-unit, calendar-year-unit, calendar-era, numbered-label, item-number, floor-unit, floor-level]
+# 名前だけを並べた行で、組織の名前と名前のあいだの空白（経営企画部 IR担当）を見分ける。
+extra_word_lists:
+  [
+    prefecture-unit,
+    date-time-unit,
+    calendar-unit,
+    calendar-year-unit,
+    calendar-era,
+    numbered-label,
+    item-number,
+    floor-unit,
+    floor-level,
+    organization-unit,
+    company-form,
+  ]
 
 name:
   ja: 英数字の前後の空白がそろっていない
   en: Spacing around Latin text is inconsistent
 
 why:
-  ja: 日本語と英字・数字のあいだを空けるか詰めるかは、どちらでも読めます。困るのは一つの文書の中で混ざることで、読み手には違いに意味があるように見えます。chaff はどちらが正しいかを決めず、文書の中で少ないほうを指摘します。英字と、数字の前、数字の後ろは別々に数えます。「を 3回」のように、数字の前は空けて助数詞とは詰める書き方がふつうにあるからです。「3GBの」のように数字に続く単位は、英字ではなく数字の側として数えます。逆に「H30 等」「EC2 で」「Phase 1 は」のように英字で始まって数字で終わる名前は、英字の側として数えます。「073-489-5909」「2026-06-02」のような番号や、「1.0.0」のような版番号は数量ではないので数えません。日付・時刻（「9月」「2026年」「令和8年」「10月1日」「3時」「10時5分」）も、数と単位を詰めて書く決まりなので、その中の境目も、前の境目（「は 9月」「午後3時」）も数えません。長さ（「3ヶ月」「3 時間」「5日で」「3年」）は数量として数えます。題や注の番号として書かれた数（「3.1 リサーチの原則」の節番号、※1 の注番号、行の頭に続き番号で並べた注の番号、番号が増えていく箇条書きの頭の番号、「問3」「図2」のように語のすぐ後ろに書いた番号）、0 で始まる組を含む番号（102-0094）、〒の後ろの郵便番号（〒100-8916）、市・区・町まで下りた地名のすぐ後ろの番地（千代田区紀尾井町1-3）も、後ろの空白が番号と題・項目の区切りなので数えません。建物の名前の後ろに空白で区切って書いた階や部屋の番号（「本社 5階 第2会議室」「研究所 3階 セミナー室」）の前の空白も、所在の組の区切りなので数えません。「第1節 AI の…」の「第1節」の後ろの空白も同じです。鉤括弧（「」『』）で引いた題名や発言の中も、リンクの文字の中も、空け方は引いた元のものなので数えません。
-  en: Whether to put a space between Japanese and Latin letters or digits is a choice either way. What reads badly is mixing both in one document, which suggests the difference means something. chaff does not decide which is right; it points at whichever the document uses less. Letters, the space before a digit and the space after one are counted separately, since spacing before a number but not before its counter is common. A unit after a number (3GB) counts with the number; a name that starts with a letter and ends in a digit (H30, EC2, Phase 1) counts with the letters. A code such as a phone number, a date or a version (073-489-5909, 2026-06-02, 1.0.0) is not a quantity and is not counted. Nor is a date or a time written with units (9月, 2026年, 令和8年, 10月1日, 3時, 10時5分), which is packed by convention; neither its inside nor the space before it (は 9月, 午後3時) counts. A length of time (3ヶ月, 3 時間, 5日で, 3年) is a quantity and counts. Neither is a number written as the label of a title or a note (a section number such as 3.1 before its title, a note number after ※, the numbers of notes listed one per line in sequence, numbers opening the items of a list that go up, a number written right after a word such as 問 or 図), a code with a part starting with 0 (102-0094), a postal code after 〒 (〒100-8916), or a hyphenated address number right after a city, ward or town (千代田区紀尾井町1-3), since the space after it separates the label from its title or the next item. Nor is the space before a floor or room number written after the name of a building (本社 5階 第2会議室), which separates the parts of a location. The same goes for the space after a division such as 第1節. Nor is the spacing inside a title or a quotation in 「」 or 『』, or inside the text of a link, which is the source's, not the writer's.
+  ja: 日本語と英字・数字のあいだを空けるか詰めるかは、どちらでも読めます。困るのは一つの文書の中で混ざることで、読み手には違いに意味があるように見えます。chaff はどちらが正しいかを決めず、文書の中で少ないほうを指摘します。英字と、数字の前、数字の後ろは別々に数えます。「を 3回」のように、数字の前は空けて助数詞とは詰める書き方がふつうにあるからです。「3GBの」のように数字に続く単位は、英字ではなく数字の側として数えます。逆に「H30 等」「EC2 で」「Phase 1 は」のように英字で始まって数字で終わる名前は、英字の側として数えます。「073-489-5909」「2026-06-02」のような番号や、「1.0.0」のような版番号は数量ではないので数えません。日付・時刻（「9月」「2026年」「令和8年」「10月1日」「3時」「10時5分」）も、数と単位を詰めて書く決まりなので、その中の境目も、前の境目（「は 9月」「午後3時」）も数えません。コロンで書いた時刻（「13:30」「後の17:15から」）も同じです。メールアドレスや URL（「privacy@example.com で」）の前後の空白は、アドレスの終わりを示す区切りなので数えません。予約番号や型番のような番号（「予約番号 MN-48215 を」「型番 SB-210 と」）の前後の空白も、番号を文から区切るものなので数えません。長さ（「3ヶ月」「3 時間」「5日で」「3年」）は数量として数えます。題や注の番号として書かれた数（「3.1 リサーチの原則」の節番号、※1 の注番号、行の頭に続き番号で並べた注の番号、番号が増えていく箇条書きの頭の番号、「問3」「図2」のように語のすぐ後ろに書いた番号）、0 で始まる組を含む番号（102-0094）、〒の後ろの郵便番号（〒100-8916）、市・区・町まで下りた地名のすぐ後ろの番地（千代田区紀尾井町1-3）も、後ろの空白が番号と題・項目の区切りなので数えません。建物の名前の後ろに空白で区切って書いた階や部屋の番号（「本社 5階 第2会議室」「研究所 3階 セミナー室」）の前の空白も、所在の組の区切りなので数えません。名前だけを空白で並べた行（「株式会社あおば電子 経営企画部 IR担当」「東京本社 PR室」）で、空白の両側が部署・拠点・役目や会社の名前のときの空白も、名前と名前の区切りなので数えません。「第1節 AI の…」の「第1節」の後ろの空白も同じです。鉤括弧（「」『』）で引いた題名や発言の中も、リンクの文字の中も、空け方は引いた元のものなので数えません。
+  en: Whether to put a space between Japanese and Latin letters or digits is a choice either way. What reads badly is mixing both in one document, which suggests the difference means something. chaff does not decide which is right; it points at whichever the document uses less. Letters, the space before a digit and the space after one are counted separately, since spacing before a number but not before its counter is common. A unit after a number (3GB) counts with the number; a name that starts with a letter and ends in a digit (H30, EC2, Phase 1) counts with the letters. A code such as a phone number, a date or a version (073-489-5909, 2026-06-02, 1.0.0) is not a quantity and is not counted. Nor is a date or a time written with units (9月, 2026年, 令和8年, 10月1日, 3時, 10時5分), which is packed by convention; neither its inside nor the space before it (は 9月, 午後3時) counts. The same goes for a clock time written with a colon (13:30). Nor is the space beside an e-mail address or a URL (privacy@example.com で), which marks where the address ends, or beside a booking or model number (予約番号 MN-48215 を, 型番 SB-210 と), which sets the number off from the sentence. A length of time (3ヶ月, 3 時間, 5日で, 3年) is a quantity and counts. Neither is a number written as the label of a title or a note (a section number such as 3.1 before its title, a note number after ※, the numbers of notes listed one per line in sequence, numbers opening the items of a list that go up, a number written right after a word such as 問 or 図), a code with a part starting with 0 (102-0094), a postal code after 〒 (〒100-8916), or a hyphenated address number right after a city, ward or town (千代田区紀尾井町1-3), since the space after it separates the label from its title or the next item. Nor is the space before a floor or room number written after the name of a building (本社 5階 第2会議室), which separates the parts of a location. Nor is the space between names on a line of names alone (株式会社あおば電子 経営企画部 IR担当, 東京本社 PR室), when both sides are names of a department, an office, a role or a company, since it separates one name from the next. The same goes for the space after a division such as 第1節. Nor is the spacing inside a title or a quotation in 「」 or 『』, or inside the text of a link, which is the source's, not the writer's.
 
 message:
   ja: "日本語と{kind}のあいだを{style}（この文書はふつう{usual}。{of} 箇所のうち {count} 箇所が違う）"
@@ -47,7 +61,7 @@ sources: [koyobun-2022, jtf-style-guide]
 group: consistency
 summary:
   ja: 日本語と英数字のあいだの空白が、文書の中で付いたり付かなかったりしている所
-  en: Spacing between Japanese and Latin letters or digits that is done both ways in one document
+  en: A space between Japanese and Latin letters in some places and not others
 example:
   ja:
     before: |
@@ -56,8 +70,8 @@ example:
       表は Excel で作り、Word に貼ります。図は PowerPoint で描きます。最後に PDF にします。
 
 not_flagged:
-  ja: 電話番号や日付のような番号、版番号（1.0.0）、単位つきの日付や時刻（9月、10時5分）、建物の名前の後ろに空白で区切った階や部屋の番号（本社 5階）の前、見出しの番号、行の頭の項目の番号（「一 JIS…」の一、イ）の後ろ、「」の中、リンクの文字の中は数えません。どちらの空け方が正しいかは決めません。少ないほうが全体の 2 割を超えるほど多ければ（5 箇所以上）、1 箇所ずつではなく、書き方が二通りあることを 1 件で言います。
-  en: Codes such as phone numbers, dates and version numbers (1.0.0), dates and times with units (9月, 10時5分), the space before a floor or room number after the name of a building (本社 5階), heading numbers, the space after an item number at the head of a line (一 JIS…), quotations and the text of links are not counted. Neither way is called right. When the less common way is more than a fifth of the places (and at least five), it is reported once, as a document written two ways, rather than place by place.
+  ja: 電話番号や日付のような番号、版番号（1.0.0）、予約番号や型番（MN-48215）の前後、単位つきの日付や時刻（9月、10時5分）、建物の名前の後ろに空白で区切った階や部屋の番号（本社 5階）の前、名前だけを並べた行の名前と名前のあいだ（経営企画部 IR担当）、見出しの番号、行の頭の項目の番号（「一 JIS…」の一、イ）の後ろ、「」の中、リンクの文字の中は数えません。どちらの空け方が正しいかは決めません。少ないほうが全体の 2 割を超えるほど多ければ（5 箇所以上）、1 箇所ずつではなく、書き方が二通りあることを 1 件で言います。
+  en: Codes such as phone numbers, dates and version numbers (1.0.0), the spaces beside a booking or model number (MN-48215), dates and times with units (9月, 10時5分), the space before a floor or room number after the name of a building (本社 5階), the space between names on a line of names alone (経営企画部 IR担当), heading numbers, the space after an item number at the head of a line (一 JIS…), quotations and the text of links are not counted. Neither way is called right. When the less common way is more than a fifth of the places (and at least five), it is reported once, as a document written two ways, rather than place by place.
 level_meaning:
   ja: 少ないほうの空け方が {limit} 箇所あれば指摘
   en: reported once {limit} places go against the document's habit

package/rules/layout-code-mismatch.yaml

@@ -0,0 +1,68 @@
+id: layout-code-mismatch
+layer: L3
+status: stable
+how_to_find: layout-code-mismatch
+# The code is read with layout-code (the letters of 2LDK, the words of "2 bedrooms"), the rooms with layout-room, and the
+# fields that hold them with layout-label.
+severity: warning
+
+name:
+  ja: 部屋の内訳と合わない間取り
+  en: A layout that does not match the rooms listed
+
+why:
+  ja: 物件の「間取り 3LDK」の頭の数は、L・D・K と納戸（S）を除いた居室の数です。同じ物件の間取り詳細が「LDK 11.5帖、洋室 6帖、洋室 5帖」なら居室は二つで、3LDK か内訳のどちらかが間違っています。別の部屋の情報を写したときや、間取りの記号だけを書き換えたときに起きます。内訳に LDK を挙げたのに間取りが 2DK のように、記号に無い L・D・K を内訳が挙げるときも言います。
+  en: 'In a property listing, "3 bedrooms" and a room list of "Bedroom 1, Bedroom 2" cannot both be right, and a Japanese layout code such as 3LDK counts its rooms besides the living room, dining area, kitchen and any storage room (S). It happens when the details of another unit are copied, or when only the code is edited. A Japanese code is also checked for an L, D or K part the room list names and the code lacks (an LDK listed under a 2DK).'
+
+message:
+  ja: 間取り「{code}」の居室は{stated}室ですが、内訳に挙げた居室は{listed}室です
+  en: 'The layout "{code}" has {stated} rooms, but the room list names {listed}'
+messages:
+  part:
+    ja: 内訳の「{part}」に当たる部分が、間取り「{code}」にありません
+    en: 'The room list names "{part}", which the layout "{code}" does not have'
+
+how_to_fix:
+  ja: 間取りの記号と部屋の内訳を物件の図面と見比べて、間違っているほうを直してください。
+  en: Compare the layout and the room list with the floor plan, and correct the wrong one.
+
+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: 「間取り 3LDK」と、間取り詳細に挙げた居室の数（洋室二つ）のように、間取りの記号と部屋の内訳が合わない所
+  en: A room layout such as "3 bedrooms" that does not match the rooms listed
+example:
+  ja:
+    before: |
+      | 項目 | 内容 |
+      | --- | --- |
+      | 間取り | 3LDK |
+      | 間取り詳細 | LDK 11.5帖、洋室 6帖、洋室 5帖 |
+    after: |
+      | 項目 | 内容 |
+      | --- | --- |
+      | 間取り | 2LDK |
+      | 間取り詳細 | LDK 11.5帖、洋室 6帖、洋室 5帖 |
+  en:
+    before: |
+      | Item | Details |
+      | --- | --- |
+      | Layout | 3 bedrooms, 1 bathroom |
+      | Rooms | Living room, Bedroom 1, Bedroom 2, Bathroom |
+    after: |
+      | Item | Details |
+      | --- | --- |
+      | Layout | 2 bedrooms, 1 bathroom |
+      | Rooms | Living room, Bedroom 1, Bedroom 2, Bathroom |
+
+not_flagged:
+  ja: 間取りの記号は「間取り」の項目（表の行、表の列、「間取り：」の行）だけを、部屋の内訳は「間取り詳細」の項目、部屋ごとの表、記号の後ろの括弧（2LDK（洋室6帖・洋室5帖・LDK12帖））だけを読みます。内訳の無い物件は言いません。納戸・S・サービスルームは居室に数えず、書斎のように物件で数え方の違う部屋が内訳にあれば数を比べません。一つの節に物件が複数あるときは、記号と内訳の数が同じときだけ順に組にします。内訳が居室を一つも挙げないときと、1R の台所は比べません。
+  en: 'Only the layout field (a table row, a table column, or a "Layout:" line) is read for the code, and only the rooms field, a table of rooms, or a bracket after the code for the room list. A listing without a room list is not reported. A den, a study and a box room are not counted as bedrooms, and a list that names a room some listings count and others do not (an office, a nursery) is not compared. With several listings in one section, codes and room lists are paired in order only when there are as many of each. A room list that names no bedroom is not compared.'
+level_meaning:
+  ja: 間取りの記号と部屋の内訳の居室の数が合わないとき指摘
+  en: reported when a layout and the room list of the same listing disagree

package/rules/less-for-fewer.yaml

@@ -33,7 +33,7 @@ off_for:
 group: slips
 summary:
   ja: 英語で、「less errors」のように数えられる名詞の複数に less を付けた所
-  en: '"Less" before a countable plural, as in "less errors", where written English uses "fewer"'
+  en: '"Less" before a countable plural, as in "less errors" for "fewer errors"'
 example:
   en:
     before: The new parser reports less errors on long files.

package/rules/line-amount-mismatch.yaml

@@ -2,8 +2,9 @@ id: line-amount-mismatch
 layer: L3
 status: stable
 how_to_find: line-amount
-# The column names come from the language's quantity-column, unit-price-column and line-amount-column lexicons; the units
-# of a quantity and of a per-unit price from rate-unit and per-unit-mark.
+# The column names come from the language's quantity-column, unit-price-column and line-amount-column lexicons, and a
+# catalog's from pack-count-column and pack-price-column; the units of a quantity and of a per-unit price from rate-unit
+# and per-unit-mark.
 languages: [ja, en]
 severity: error
 
@@ -12,8 +13,8 @@ name:
   en: Quantity times unit price is not the line amount
 
 why:
-  ja: 見積書や請求書の明細で、数量と単価を掛けた額がその行の金額と合わないと、読み手はどれが正しいのかを問い合わせることになります。数量か単価だけを直して金額を直し忘れたときに起きます。見出しに数量・単価・金額の列がある表で、行ごとに数量の升の頭の数と単価を掛け、金額の升と比べます。
-  en: When quantity times unit price in a line of a quote or an invoice is not the line's amount, the reader has to ask which one is right. It happens when the quantity or the price is changed and the amount is not. In a table with quantity, unit price and amount columns, each row's quantity (the number its cell starts with) times its unit price is compared with its amount.
+  ja: 見積書や請求書の明細で、数量と単価を掛けた額がその行の金額と合わないと、読み手はどれが正しいのかを問い合わせることになります。数量か単価だけを直して金額を直し忘れたときに起きます。見出しに数量・単価・金額の列がある表で、行ごとに数量の升の頭の数と単価を掛け、金額の升と比べます。商品カタログの入数・単価・1箱の価格の列がある表では、入数 × 単価を1箱の価格と比べます。項目の升の括弧に書いた掛け算（会費（3,000円×24名））も、名や世帯で数えた数と金額の一つずつなら掛けて、その行のただ一つの金額と比べます。
+  en: When quantity times unit price in a line of a quote or an invoice is not the line's amount, the reader has to ask which one is right. It happens when the quantity or the price is changed and the amount is not. In a table with quantity, unit price and amount columns, each row's quantity (the number its cell starts with) times its unit price is compared with its amount. In a catalog with count per pack, unit price and pack price columns, count per pack × unit price is compared with the pack price. A product written in brackets in the item cell (Membership dues (24 members × $40)), one amount of money and one count in a counting word, is compared with the row's one amount too.
 
 message:
   ja: 金額「{written}」が、数量×単価（{quantity} × {price} = {expected}）と合いません
@@ -32,7 +33,7 @@ off_for:
 group: facts
 summary:
   ja: 見積書や請求書の明細で、数量×単価がその行の金額と合わない所
-  en: A line of a quote or an invoice whose quantity times unit price is not its amount
+  en: A line of a quote or invoice whose quantity times price is not its amount
 example:
   ja:
     before: |
@@ -54,5 +55,5 @@ example:
       | Screens | 4 | $1,500 | $6,000 |
 
 not_flagged:
-  ja: 端数は切り捨て・四捨五入・切り上げのどれでも合っていると読みます。単価と金額の書き方（円、万円、$）が違う行、単価が何かあたり（10,000円/時、月額、英語の Rate の列）で数量が別の単位で書かれた行（「2日」と月額）、ほかの列にも数のある行（値引き、税率）、升に数が二つ以上あるか負の印のある行、数量の升が数で始まらない行（「1式」は 1 と読みます）は比べません。見出しに三つの列がそろわない表と、コードの中は読みません。
-  en: Rounding down, to the nearest or up are all read as right. A row whose price and amount are written with different marks ($ and USD, 円 and 万円), a row whose price is per a unit ($100/hour, $300 per month, a Rate column) and whose quantity is written in another unit (2 days at $100/hour), a row with a number in another column (a discount, a tax rate), a cell with two numbers or a negative sign, and a quantity cell that does not start with a number are not compared. A table without all three columns, and code, are not read.
+  ja: 端数は切り捨て・四捨五入・切り上げのどれでも合っていると読みます。納品書のように発注・納品・残の数量の列が並ぶ表では、どれか一つの数量×単価が金額になれば合っていると読みます。同じ役割の数量の列が二つある表（前回納品数と今回納品数）は読みません。単価と金額の書き方（円、万円、$）が違う行、単価が何かあたり（10,000円/時、月額、英語の Rate の列）で数量が別の単位で書かれた行（「2日」と月額）、ほかの列にも数のある行（値引き、税率。品名の列の数と、金額を税込で言い直す列は除きます）、升に数が二つ以上あるか負の印のある行、数量の升が数で始まらない行（「1式」は 1 と読みます）は比べません。年額の列（月額 × 月数）は、数量が「12か月」や月数の列のように月で数える行だけ比べます。英語の一人あたりの単価の列（Per student、Per person）は、日数や時間の列とは掛けません。入数は注文の数量ではないので、1箱の価格の列と並ぶときだけ読みます。見出しに三つの列がそろわない表と、コードの中は読みません。項目の升の括弧の掛け算は、×が二つ以上あるもの、% のあるもの、金額と数える語の数の組でないもの（12m×4m、3,000円×24日）と、金額のほかにも数のある行（予算と決算）は読みません。
+  en: Rounding down, to the nearest or up are all read as right. In a table with ordered, delivered and backordered quantity columns (a delivery note), a row is right when any one of them times the price is the amount; a table with two quantity columns of one kind (previously and now delivered) is not read. A row whose price and amount are written with different marks ($ and USD, 円 and 万円), a row whose price is per a unit ($100/hour, $300 per month, a Rate column) and whose quantity is written in another unit (2 days at $100/hour), a row with a number in another column (a discount, a tax rate; not a number in the item's name, nor the amount restated with tax), a cell with two numbers or a negative sign, and a quantity cell that does not start with a number are not compared. An annual amount (monthly × months) is compared only in a row whose quantity counts months (12 months, a Months column). A cost per head (Per student, Per person) is not multiplied by days or hours, and a head count (Students, Guests) is not multiplied by a Rate whose period is unstated. A count per pack is no order quantity, so it is read only beside a pack price column. A table without all three columns, and code, are not read. A product in an item cell's brackets with two times marks, a %, or factors that are not one amount and one count in a counting word (12m × 4m, $40 × 24 days), and a row with another number besides its amount (budget and actual), are not read.

package/rules/link-text-url-mismatch.yaml

@@ -27,7 +27,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
 group: slips
 summary:
-  ja: 「[https://a.example](https://b.example)」のように、言葉に見える URL と行き先のサイトが違うリンク
+  ja: 見えている URL と、実際の行き先のサイトが違うリンク
   en: A link whose text is a URL on one site and whose target is on another
 example:
   ja:

package/rules/list-item-form-mix.yaml

@@ -48,7 +48,7 @@ off_for:
 group: consistency
 summary:
   ja: 一つの箇条書きの中で、名詞で終わる項目と文で終わる項目（英語では動詞で始まる項目と名詞で始まる項目）が混ざっている所
-  en: One list mixing phrases with sentences, or items that open with a verb with items that open with a noun
+  en: One list mixing phrases with sentences, or verb-first items with noun-first ones
 
 example:
   ja:

package/rules/lookalike-character.yaml

@@ -41,7 +41,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: slips
 summary:
   ja: 部首の字（⼈）、互換漢字、字と分かれた濁点（か＋゛）のような、ふつうの字と同じに見える別の字
-  en: A character that looks like an ordinary one but is another, such as a Kangxi radical (⼈ for 人) or a letter and a separate combining mark
+  en: A character that looks like an ordinary one but is a different one
 example:
   ja:
     before: "申込書は総務課の⼭田さんへ送ってください。\n"

package/rules/max-kanji-continuous.yaml

@@ -42,7 +42,7 @@ sources: [shibasaki-tamaoka-2010, lee-2016]
 group: readability
 summary:
   ja: 「新規顧客獲得施策検討会議」のように、漢字だけが長く続く所
-  en: A long run of kanji with no kana between them, which Japanese readers have to take apart
+  en: A long run of kanji with no kana between them, hard for readers to take apart
 example:
   ja:
     before: 来週、新規顧客獲得施策検討会議を開きます。

package/rules/meter-usage-mismatch.yaml

@@ -0,0 +1,64 @@
+id: meter-usage-mismatch
+layer: L3
+status: stable
+how_to_find: meter-usage
+# The names of the readings come from the language's meter-reading-label lexicon, their units from meter-unit, and a stated
+# rollover or meter replacement from meter-event.
+languages: [ja, en]
+severity: error
+
+name:
+  ja: 指示数の差が使用量と合わない
+  en: The meter readings' difference is not the usage
+
+why:
+  ja: 電気や水道の検針票では、今回の指示数から前回の指示数を引いた値（乗率があればそれを掛けた値）が使用量で、料金はその使用量から計算します。指示数を写し間違えると、使用量と料金のどちらが正しいのか読み手には分かりません。同じ見出しの下に今回指示数・前回指示数・使用量が一つずつあれば、「今回指示数：12,640」の行、行の見出しが名前の表、列の見出しが名前の表のどれに書いてあっても読み、差と使用量を比べます。名前は言語パッケージの語彙表 meter-reading-label にあります。
+  en: 'On an electricity or water bill the usage is the current meter reading minus the previous one (times the multiplier, when there is one), and the charges are worked out from it. When a reading is copied wrong, the reader cannot tell whether the usage or the charges are right. When one section has one current reading, one previous reading and one usage, written as "Current reading: 48,650" lines or in a table with the names as row or column headings, the difference is compared with the usage. The names are in the language package''s meter-reading-label lexicon.'
+
+message:
+  ja: 指示数の差（{current} − {previous}{times} = {expected}）が、使用量「{usage}」と合いません
+  en: "The readings' difference ({current} − {previous}{times} = {expected}) is not the usage {usage}"
+
+how_to_fix:
+  ja: 今回と前回の指示数をメーターの記録と照らし、指示数か使用量のどちらかを直してください。使用量を直したら料金も直します。
+  en: Check both readings against the meter record and correct the readings or the usage. If the usage changes, correct the charges with it.
+
+levels: { normal: error, relaxed: warning }
+
+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 utility bill whose current minus previous meter reading is not the usage
+example:
+  ja:
+    before: |
+      | 区分 | 指示数 |
+      | --- | --- |
+      | 今回指示数 | 12,660 |
+      | 前回指示数 | 12,290 |
+
+      ご使用量：350kWh
+    after: |
+      | 区分 | 指示数 |
+      | --- | --- |
+      | 今回指示数 | 12,640 |
+      | 前回指示数 | 12,290 |
+
+      ご使用量：350kWh
+  en:
+    before: |
+      Current reading: 48,650 kWh
+      Previous reading: 47,900 kWh
+      Electricity used: 720 kWh
+    after: |
+      Current reading: 48,620 kWh
+      Previous reading: 47,900 kWh
+      Electricity used: 720 kWh
+
+not_flagged:
+  ja: 使用量は書いた桁までの丸めを認めます。今回・前回・使用量のどれかが無いか二つ以上ある見出しの下（昼と夜の二つのメーター）、単位が食い違う値（kWh と m³）、語彙表 meter-unit に無い語の付いた値、読めない乗率は比べません。今回が前回より小さいときは、同じ見出しの下にメーターが一巡したと書いてあれば前回の桁数の上限を足して比べ、書いていないか、「一巡していません」のように同じ節で打ち消していれば比べません。メーターを取り替えたと書いてあれば比べません。列の見出しが名前の表で本体が二行以上あれば、行ごとに別のメーターとして比べ、一巡や取り替えはその行に書いたものだけを見ます。
+  en: The usage may be rounded to its last digit. A section with no current reading, previous reading or usage, or with two of one (a day and a night meter), values in different units (kWh and m³), a value with a word that is not in the meter-unit lexicon, and a multiplier that cannot be read are not compared. A current reading below the previous one is compared, with the previous reading's next power of ten added, only when the section says the meter rolled over and the same clause does not deny it ("has not rolled over"). A section that says the meter was replaced is not compared. A table with the names as column headings and two or more rows is compared row by row, each row a meter of its own, and only what that row says about a rollover or a replacement counts.

package/rules/misconversion.yaml

@@ -38,7 +38,7 @@ use_for: [blog, business, technical, legal, docs, academic, literature, speech]
 group: slips
 summary:
   ja: 「以外と簡単」「始めて会う」「不可決」のような、仮名漢字変換の取り違え
-  en: A Japanese homophone picked by the input method in the wrong place, such as 以外と簡単 for 意外と簡単
+  en: A wrong Japanese sound-alike picked by the input method (以外と for 意外と)
 example:
   ja:
     before: 設定は以外と簡単でした。

package/rules/modal-conflict.yaml

@@ -39,7 +39,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: structure
 summary:
   ja: 同じ主語の同じ行為を、ある文では義務や許可に、別の文では禁止にしている所
-  en: The same act by the same party required or allowed in one sentence and forbidden in another
+  en: The same act required or allowed in one sentence and forbidden in another
 example:
   ja:
     before: |