chaffjs 0.30.0 → 0.32.0

package/rules/period-part-exceeds-whole.yaml

@@ -0,0 +1,62 @@
+id: period-part-exceeds-whole
+layer: L3
+status: stable
+how_to_find: period-part-exceeds-whole
+requires: [dates, quantities]
+# The words that make one period a part of another are period-part-marker; the word that ends a period's name period-part-word;
+# words for a period after the whole period-part-after; words joining the ends of a range period-part-range; the word between a
+# length and the whole's name period-part-inline-joiner; and words stating a length after a name period-part-length-verb.
+severity: warning
+
+name:
+  ja: 全体の期間より長い、その一部の期間
+  en: A part of a period that is longer than the period
+
+why:
+  ja: 「保証期間（12か月）のうち、無料交換期間は18か月」と書くと、読み手は無料交換を13か月目から18か月目まで受けられるのかを問い合わせることになります。期間の長さを片方だけ直したとき、別の製品の文書から一部の期間を写したときに起きます。「のうち」「の中で」「期間内の」の前に書いた期間を全体とし、同じ文のもう一つの期間を部分として、部分が全体より長ければ指します。全体の長さは、その名前の括弧の中か直前（12か月の保証期間）に書いたものを読みます。無ければ同じ節で全体の名前（保証期間）に書いた長さを読みます（表の行も読みます）。節の中に違う長さが並べば一番長いものと比べます。「このうち」は前の文の長さを全体にします。年は月に、週は日に換算して比べます。
+  en: 'When a card says "Within the 12-month warranty period, the free replacement period is 18 months", the reader has to ask whether replacement is free in months 13 to 18. It happens when one of the two lengths is updated and the other is not, or when a part is copied from another product''s terms. The period after "within the", or before "of the", is the whole, and the one other length in the sentence is the part; the part is reported when it is longer. The whole''s length is read where it is named (the 12-month warranty period, the warranty period (12 months)); otherwise from the same section, in a sentence or table row that names the whole ("The warranty period is 1 year", "the warranty runs for 12 months"). When the section gives several lengths, the longest is used. "Within it" takes the length in the sentence before. Years are converted to months and weeks to days.'
+
+message:
+  ja: 「{part}」は、それを含む全体の期間「{whole}」より長くなっています
+  en: '"{part}" is longer than the period it is part of, "{whole}"'
+
+how_to_fix:
+  ja: 部分の期間か全体の期間のどちらかを正しい長さに直してください。全体の後に続く期間（延長保証）なら、「保証期間の終了後」のようにそう分かる書き方にしてください。
+  en: Correct whichever length is wrong. If the period follows the whole (an extended warranty), say so ("after the warranty period ends").
+
+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: 「保証期間（12か月）のうち無料交換期間は18か月」のような全体より長い一部の期間
+  en: "A part of a period longer than the whole: 18 months within a 12-month warranty"
+example:
+  ja:
+    before: |
+      # 保証規定
+
+      保証期間（12か月）のうち、無料交換期間はお買い上げ日から18か月です。
+    after: |
+      # 保証規定
+
+      保証期間（12か月）のうち、無料交換期間はお買い上げ日から3か月です。
+  en:
+    before: |
+      # Limited Warranty
+
+      Within the 12-month warranty period, the free replacement period is 18 months.
+    after: |
+      # Limited Warranty
+
+      Within the 12-month warranty period, the free replacement period is 3 months.
+
+not_flagged:
+  ja: 「約」「最長」「以内」「程度」の付いた長さ、「12〜18か月」のような幅は比べません。延長、追加、更新後の語のある文は、全体の後に続く期間のことがあるので読みません（延長保証期間は保証期間の長さとして読みません）。「のうち」の後ろが読点か期間の名前でないとき（保証期間のうちに起きた故障）、文に部分の長さが二つ以上あるとき、部分の側に全体と別の「〜期間」の名前が無いとき、全体の長さが同じ節に無いときは読みません。全体の名前を書いた文に長さが二つ以上あれば、その文から全体の長さは読みません。月と日、月と週は、月の日数が決まらないので比べません。
+  en: 'A length with "about", "up to" or "at least", and a range ("12 to 18 months"), is not compared. A sentence with "extended", "extension", "additional", "extra" or "renewal" may describe a period after the whole and is not read, and an "extended warranty period" is not read as the warranty period''s length. "Within the" is read only when it opens the sentence and its phrase ends with a comma ("Claims arising within the warranty period are subject to a limitation period of ..." is not read). A sentence with more than one other length, or whose part is not a named period other than the whole, or whose whole has no length in the same section, is not read; nor is a length from a sentence that gives the whole''s name more than one length. Months are not compared with days or weeks, since a month''s days vary.'
+level_meaning:
+  ja: 一部として書いた期間が、全体の期間より長いとき指摘
+  en: reported when a period described as part of another is longer than it

package/rules/person-consistency.yaml

@@ -41,7 +41,7 @@ off_for:
 group: consistency
 summary:
   ja: 「私たち」と「弊社」、「私」と「筆者」のように、一つの文書が自分や読み手を二通りに呼んでいる所
-  en: 'One document naming itself two ways (私たち and 弊社) or its reader two ways ("you" and "one")'
+  en: One document calling itself or its reader two ways ("you" and "one")
 example:
   ja:
     before: |

package/rules/phone-number-variant.yaml

@@ -34,7 +34,7 @@ off_for:
 group: facts
 summary:
   ja: 同じ文書で、電話番号の隣り合う数字が一か所だけ入れ違っている所（0120-123-456 と 0120-123-465）
-  en: One phone number written elsewhere with two neighbouring digits swapped (0120-123-456 and 0120-123-465)
+  en: A phone number written elsewhere with two digits swapped
 example:
   ja:
     before: |
@@ -64,5 +64,5 @@ example:
       Contact, phone: 0120-123-456
 
 not_flagged:
-  ja: 番号と同じ行で、前に「電話」「TEL」「お問合せ」のような語がある番号だけを読みます。語の無い数字の並び、種類の違う番号（電話とFAX）、数字が一つだけ違う番号（代表と直通、本店と支店の番号はよくそうなります）、離れた数字の入れ違いは指しません。数字が9桁から13桁で、ハイフンか括弧で区切ったものだけを番号と見ます。
-  en: "Only numbers with a label (phone, tel, call) before them on their line are read. Unlabelled runs of digits, numbers of different kinds (a phone and a fax number), numbers that differ in one digit (a main line and a direct line often do) and swaps of digits that are not neighbours are not reported. A number is 9 to 13 digits, grouped by hyphens or brackets."
+  ja: 番号と同じ行で、前に「電話」「TEL」「お問合せ」のような語か、「お客様窓口」「サポートセンター」のような窓口の名前がある番号だけを読みます（「FAX窓口」の番号はFAXの番号）。「受付番号」の後ろの数字、語の無い数字の並び、種類の違う番号（電話とFAX）、数字が一つだけ違う番号（代表と直通、本店と支店の番号はよくそうなります）、離れた数字の入れ違いは指しません。数字が9桁から13桁で、ハイフンか括弧で区切ったものだけを番号と見ます。
+  en: "Only numbers with a label (phone, tel, call) or a desk's name (Recall Line, Customer Care, Help Desk) before them on their line are read; a fax line's number is a fax number. Unlabelled runs of digits, numbers of different kinds (a phone and a fax number), numbers that differ in one digit (a main line and a direct line often do) and swaps of digits that are not neighbours are not reported. A number is 9 to 13 digits, grouped by hyphens or brackets."

package/rules/preamble-length.yaml

@@ -10,8 +10,8 @@ name:
   en: Too long before the point
 
 why:
-  ja: 業務文書の読み手は結論を探しに来ています。最初の見出しまでに段落が重なると、探す手間だけが増えます。
-  en: A reader of a business document is looking for the decision. Paragraphs before the first heading only delay it.
+  ja: 業務文書の読み手は結論を探しに来ています。最初の見出しまでに段落が重なると、探す手間だけが増えます。文の閉じない段落（分類の札、著者の行）と、値が会社名だけの宛先・差出人の欄（英語の To 欄）は数えません。
+  en: A reader of a business document is looking for the decision. Paragraphs before the first heading only delay it. A paragraph with no closed sentence (a category label, an author line) and an address field whose value is only a name ("To" followed by a company name) are not counted.
 
 message:
   ja: 最初の見出しまでに {count} 段落あります（{limit} 段落まで）

package/rules/preferred-term.yaml

@@ -35,8 +35,8 @@ sources: [plain-2011, kyodo-2022]
 
 group: team
 summary:
-  ja: チームで決めた表記と違う書き方（「サーバー」と決めたのに「サーバ」と書いた、など）。chaff.yaml の prefer に書いた組だけを見ます
-  en: A spelling the team has chosen not to use ("e-mail" where the team writes "email"), from prefer in chaff.yaml
+  ja: チームで決めた表記と違う書き方（「サーバー」と決めたのに「サーバ」）。chaff.yaml の prefer で決めます
+  en: A spelling the team chose not to use ("e-mail" for "email"), from chaff.yaml
 example:
   ja:
     config: { prefer: { サーバ: サーバー } }

package/rules/prerequisite-after-step.yaml

@@ -34,7 +34,7 @@ off_for:
 group: structure
 summary:
   ja: 節の番号付きの手順より後にある、「作業を始める前に」「始める前に」で始まる文
-  en: A sentence opening with "Before you begin" after the numbered steps of its section
+  en: '"Before you begin" written after the numbered steps it should come before'
 example:
   ja:
     config: { genre: docs/manual }

package/rules/product-exceeds-maximum.yaml

@@ -0,0 +1,49 @@
+id: product-exceeds-maximum
+layer: L3
+status: stable
+how_to_find: product-exceeds-maximum
+# The amount of one use is labelled by use-amount-word (1回2錠, 2 tablets at a time) or followed by its count; counts and
+# periods come from use-count-word (period, counter, alone), the maximum from its limit words.
+severity: warning
+
+name:
+  ja: 1回の量と回数を掛けると、書いた上限を超える
+  en: An amount per use times the uses that goes over the stated maximum
+
+why:
+  ja: 「1回2錠を1日3回まで」と「1日の最大量は4錠」を一緒に書くと、書いたとおりに使えば1日6錠になり、上限の4錠を超えます。読み手はどちらに従えばよいか分からず、上限を超えて使うおそれもあります。量か回数か上限のどれかを変えて、残りを直し忘れたときに起きます。一つの段落に、印の付いた1回の量（1回2錠、2 tablets at a time）、期間あたりの回数（1日3回、3 times a day）、同じ期間の上限（1日の最大量は4錠、no more than 4 tablets in 24 hours）がちょうど一つずつあり、量と上限の単位が同じときだけ、1回の量×回数を上限と比べます。料金（1回500円、1日10回、1日の上限3000円）は比べません。駐車料金の1日の上限のように、上限を合計より低く決めてあるのがふつうだからです。
+  en: 'When "2 tablets at a time, up to 3 times a day" and "the maximum daily dose is 4 tablets" are written together, following the directions gives 6 tablets a day, over the stated maximum of 4. The reader cannot tell which to follow and may go over the limit. It happens when the amount, the count or the maximum is changed and the rest is not. In one paragraph holding exactly one labelled amount of one use ("2 tablets at a time", 1回2錠), one count of uses in a period ("3 times a day") and one maximum for the same period ("no more than 4 tablets in 24 hours"), in the same unit as the amount, the amount times the count is compared with the maximum. Fees are not compared (500 yen per use, 10 uses a day, a daily cap of 3,000 yen): a daily cap such as a parking fee cap is usually set below the total on purpose.'
+
+message:
+  ja: 1回{amount}を{count}では{expected}{unit}になり、上限の{maximum}を超えます
+  en: "{amount} each, {count}, makes {expected} {unit}, more than the stated maximum of {maximum}"
+
+how_to_fix:
+  ja: 1回の量・回数・上限のどれが正しいかを確かめて、残りを直してください。
+  en: Check which of the amount, the count and the maximum 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: 「1回2錠を1日3回」なのに「1日の最大量は4錠」のように、1回の量×回数が上限を超える所
+  en: An amount per use times the uses per period that is over that period's maximum
+example:
+  ja:
+    before: |
+      1回2錠を1日3回まで服用できます。1日の最大量は4錠です。
+    after: |
+      1回2錠を1日3回まで服用できます。1日の最大量は6錠です。
+  en:
+    before: |
+      Take 2 tablets at a time, up to 3 times a day. The maximum daily dose is 4 tablets.
+    after: |
+      Take 2 tablets at a time, up to 3 times a day. The maximum daily dose is 6 tablets.
+
+not_flagged:
+  ja: 1回の量に印が無い所（2錠を服用）、範囲で書いた量（1回1〜2錠）、回数と上限の期間が違う所（1日3回と1週間の上限）、量と上限の単位が違う所（錠とmg）、段落に量・回数・上限のどれかが二つ以上ある所、表の中は見ません。
+  en: 'An amount with no mark of one use ("take 2 tablets"), a range ("1 to 2 tablets"), a count and a maximum for different periods (a day and a week), an amount and a maximum in different units (tablets and mg), a paragraph with two of any of the three, and tables are left alone.'

package/rules/proper-noun-density.yaml

@@ -40,7 +40,7 @@ off_for:
 group: readability
 summary:
   ja: 製品名・会社名・人名が詰まりすぎて、知らない人には文の形が見えない所
-  en: So many product, company and personal names that a newcomer cannot see the sentence
+  en: So many product, company and personal names that a newcomer gets lost
 example:
   ja:
     config: { rules: { proper-noun-density: strict } }

package/rules/quantity-range-reversed.yaml

@@ -0,0 +1,53 @@
+id: quantity-range-reversed
+layer: L3
+status: stable
+how_to_find: quantity-range
+# The quantities are read with the unit lexicons (unit-length, unit-mass, unit-time, unit-volume, unit-data, unit-temperature,
+# unit-pressure, unit-concentration, with unit-context); the joints are range-connector, range-opener, range-closer and quantity-range-word;
+# quantity-change-word and quantity-bound-label come next.
+severity: warning
+
+name:
+  ja: 量の範囲の上限が下限より小さい
+  en: A measured range whose upper end is below its lower end
+
+why:
+  ja: 「使用温度範囲：-10〜-40℃」「重さ 5〜2 kg」のように、測った量の範囲の終わりが始まりより小さいと、読み手はどちらの値が正しいのか、範囲がどこからどこまでなのかを確かめることになります。仕様書の温度や寸法で、片方の値だけを書き換えたときや、負の符号を書き足したとき、二つを入れ替えて書いたときに起きます。同じ単位の二つの量の間が範囲の記号（〜、–）だけのときと、「から」でつなぎ終わりの量のあとに「まで」が続くときを範囲として比べます。単位を一度だけ書いた範囲（30〜10 cm）も読みます。負の数は符号ごと読むので、-10〜-40℃ は終わりが小さく、-40〜-10℃ はそのままです。数の直後のハイフン（5-10 kg）は負の符号ではなく範囲の記号と読みます。同じ行に下限と上限を書いた二つの量も比べます。
+  en: 'When a measured range ends below where it starts ("Operating temperature: -10 to -40 °C", "Weight: 5–2 kg"), the reader has to ask which value is right and what the range is. It happens in a spec sheet when only one of the two values is edited, when a minus sign is added, or when the two are written the wrong way round. Two quantities in one unit are read as a range when only a range mark (–, —) or "to" stands between them, including a range that writes its unit once ("30–10 cm"). A negative number is read with its sign, so -10 to -40 °C ends below its start and -40 to -10 °C does not. A hyphen right after a number ("5-10 kg") is a range mark, not a minus sign. Two quantities on one line labelled minimum and maximum are compared too.'
+
+message:
+  ja: 量の範囲「{range}」の上限が下限より小さくなっています
+  en: 'The range "{range}" ends below where it starts'
+
+how_to_fix:
+  ja: 範囲の二つの値と符号を確かめて、書き間違えたほうを直すか、小さいほうから書いてください。
+  en: Check both values and their signs, and correct the wrong one or write the smaller one first.
+
+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: 「使用温度範囲：-10〜-40℃」のように、測った量の範囲の終わりが始まりより小さい所
+  en: A measured range that ends lower than it starts, such as "-10 to -40 °C"
+example:
+  ja:
+    before: |
+      使用温度範囲：-10〜-40℃（凍結しないこと）
+    after: |
+      使用温度範囲：-10〜40℃（凍結しないこと）
+  en:
+    before: |
+      Operating temperature: -10 to -40 °C (no freezing)
+    after: |
+      Operating temperature: -10 to 40 °C (no freezing)
+
+not_flagged:
+  ja: 同じ文に値を変える語や下る順を言う語のある二つの量（「40℃から10℃まで冷却」「カウントダウン 10〜0秒」「重い順」）、単位の違う二つの量、間に言葉のある二つの量、計算の式は比べません。百分率や単位の無い数は読みません。
+  en: 'Two quantities in a sentence with a word that changes a value or names a descending order ("cooled from 40 °C to 10 °C", "from 100 m down to 10 m", "countdown"), two quantities in different units, two quantities with words between them, and a sum are not compared. Percentages and numbers without a unit are not read.'
+level_meaning:
+  ja: 測った量の範囲の終わりが始まりより小さいとき指摘
+  en: reported when a measured range ends below where it starts

package/rules/range-band-mismatch.yaml

@@ -0,0 +1,70 @@
+id: range-band-mismatch
+layer: L3
+status: stable
+how_to_find: range-band-mismatch
+# The ends of a band are read with range-band-word, its unit with range-band-unit, and the bare numbers of a column with
+# range-band-heading.
+severity: warning
+
+name:
+  ja: 重なるか、間が空いた区分の幅
+  en: Bands that overlap or leave a gap
+
+why:
+  ja: 「7〜12歳」のあとに「12〜14歳」、「1〜6歳」のあとに「8歳以上」のように、表の列や箇条書きに並べた年齢・体重・金額・点数の区分が重なったり間が空いたりすると、12歳はどちらの量か、7歳はどの区分かを読み手が決められません。用量や料金の表で、一つの区分の端だけを書き換えたときに起きます。以上・以下は端を含み、未満・超は含まないと読みます。年齢・人数・点数のように間に値の無い数は、6〜11歳のあとの12歳〜を続いていると読み、同じ数で接する二つの区分は重なると読みます。重さ・金額・期間のように間に値のある量は、「〜」で同じ数に接する区分（50〜60kg、60〜70kg）と、書いた桁の一つ分だけ離れた区分（59kgまでと60kgから）を続いていると読みます。
+  en: 'When the bands of a table column or a list (ages, weights, amounts, scores) overlap or leave a gap, as "7 to 12" followed by "12 to 14", or "1 to 6 years" followed by "8 years and over", the reader cannot tell which amount a 12-year-old takes or which band a 7-year-old is in. It happens in a dosage or a fee table when only one end of one band is edited. "And over", "or more" and "up to" include their end; "under", "over", "more than" and "less than" do not. Ages, people and points have no value in between, so 6 to 11 then 12 and over is contiguous and two bands that share an end number overlap. Weights, money and durations do, so two bands that meet at one number with a range mark ("50-60 kg", "60-70 kg") are contiguous, and so are two a step of the written digits apart (59 kg then 60 kg).'
+
+message:
+  ja: 区分「{earlier}」と「{later}」の幅が重なっています
+  en: 'The bands "{earlier}" and "{later}" overlap'
+messages:
+  gap:
+    ja: 区分「{earlier}」と「{later}」の間が空いています
+    en: 'The bands "{earlier}" and "{later}" leave a gap between them'
+
+how_to_fix:
+  ja: 区分の端の数を確かめて、書き間違えたほうを直してください。
+  en: Check the end numbers of the two bands, 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: 表の列や箇条書きの「7〜12歳」「12〜14歳」のように、隣り合う区分の幅が重なるか、間が空いた所
+  en: Neighbouring bands that overlap or leave a gap, such as "7 to 12", "12 to 14"
+example:
+  ja:
+    before: |
+      | 年齢 | 1回量 |
+      | --- | --- |
+      | 15歳以上 | 2錠 |
+      | 12〜14歳 | 1錠 |
+      | 7〜12歳 | 半錠 |
+    after: |
+      | 年齢 | 1回量 |
+      | --- | --- |
+      | 15歳以上 | 2錠 |
+      | 12〜14歳 | 1錠 |
+      | 7〜11歳 | 半錠 |
+  en:
+    before: |
+      | Age | Dose |
+      | --- | --- |
+      | 1 to 6 years | 1 chew |
+      | 8 years and over | 2 chews |
+    after: |
+      | Age | Dose |
+      | --- | --- |
+      | 1 to 6 years | 1 chew |
+      | 7 years and over | 2 chews |
+
+not_flagged:
+  ja: 区分は、表の一つの列の続いた行か、一つの箇条書きの続いた項目の頭に、同じ単位で書いたものだけを比べます。単位を書かない数は、列の見出しが何を数えるか言うとき（年齢、体重(kg)）だけ読みます。一方の端だけを書いた区分が重なっていく段階（〜100万円、〜200万円、5人以上、10人以上）は、重なるように書いたものとして読みません。半分を超えて重なる区分（大きさの目安）と、二つだけの区分で、狭いほうの幅より大きく離れたものも言いません。時刻、日付と年（暦の年と分けられない）、負の数、単位の違う区分は読みません。
+  en: 'Only bands in consecutive rows of one table column, or at the head of consecutive items of one list, in one unit, are compared. Bare numbers are read only when the column heading says what they count ("Age", "Weight (kg)"). Tiers bounded at one end that are meant to nest ("up to $100", "up to $200", "5 or more", "10 or more") are not read as overlapping. Bands that overlap by more than half (size guides), and two bands alone that are further apart than the narrower one is wide, are not reported. Times of day, dates, negative numbers and bands in different units are not read.'
+level_meaning:
+  ja: 隣り合う区分の幅が重なるか、間が空いたとき指摘
+  en: reported when neighbouring bands overlap or leave a gap

package/rules/ratio-mismatch.yaml

@@ -0,0 +1,64 @@
+id: ratio-mismatch
+layer: L3
+status: stable
+how_to_find: ratio-mismatch
+requires: [quantities]
+severity: warning
+
+name:
+  ja: 利益率が二つの値の割り算と合わない
+  en: A margin the two values it divides do not give
+
+why:
+  ja: 決算の表の「営業利益率 7.3%」は、同じ列の営業利益を売上高で割った値です。読み手は率を割り算し直さずに信じます。金額だけを直したとき、率を前の期の表から写したときに食い違います。表で、行の見出しが率の名前（営業利益率、経常利益率、売上総利益率）だけの行があり、同じ表にその分子の行（営業利益）と分母の行（売上高）が一つずつあれば、列ごとに分子を分母で割って比べます。一つの文に率の名前と分子・分母の名前が一度ずつあり、それぞれのすぐ後ろに値があるとき（「営業利益は96百万円、売上高は1,320百万円で、営業利益率は7.3%」）も比べます。どの率がどの二つの値の割り算かは、言語パッケージの語彙表 ratio-label と ratio-term にあります。率は書いた桁の半分までの丸めを認めます（7.3% は 7.25% から 7.35% のどれか）。金額は書いた最後の桁の一つ分までのずれを認めます。決算の表は百万円未満を切り捨てることが多く、率は切り捨てる前の金額から計算するので、半分では足りません。
+  en: The "Operating margin 7.5%" of a results table is the operating profit divided by the net sales in the same column. Readers trust it without dividing again. It goes wrong when an amount is corrected and the margin is not, or when the margin is copied from last period's table. In a table, a row labelled with only the name of a ratio (Operating margin, Gross margin, Net margin) is compared, column by column, with its numerator divided by its denominator, when the same table has one row of each (Operating profit, Net sales). One sentence that names the ratio, the numerator and the denominator once each, with a value right after each name ("Operating profit was $198 million on net sales of $2,640 million, an operating margin of 7.5%"), is compared too. Which ratio divides which two values is in the language package's lexicons ratio-label and ratio-term. The ratio may be rounded to half its last digit (7.3% is anything from 7.25% to 7.35%). Each amount may be off by one whole step of its last digit, not half, because results tables often round amounts down and the margin is worked out from the amounts before rounding.
+
+message:
+  ja: 「{ratio}」の「{written}%」は、分子と分母の値からは {computed}% です
+  en: '{ratio} "{written}%" is written, but its two values give {computed}%'
+
+how_to_fix:
+  ja: 率と二つの値のどれが正しいかを確かめて、ほかを直してください。
+  en: Check which of the ratio and the two values is right, and correct the others.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+
+group: facts
+summary:
+  ja: 表や文の「営業利益率」が、営業利益 ÷ 売上高 と合わない所
+  en: A margin in a table or sentence that is not its profit divided by its sales
+example:
+  ja:
+    before: |
+      | 項目 | 前期 | 当期 |
+      | --- | --- | --- |
+      | 売上高 | 1,200 | 1,320 |
+      | 営業利益 | 84 | 96 |
+      | 営業利益率 | 7.0% | 8.0% |
+    after: |
+      | 項目 | 前期 | 当期 |
+      | --- | --- | --- |
+      | 売上高 | 1,200 | 1,320 |
+      | 営業利益 | 84 | 96 |
+      | 営業利益率 | 7.0% | 7.3% |
+  en:
+    before: |
+      | Item | FY2025 | FY2026 |
+      | --- | --- | --- |
+      | Net sales | 1,200 | 1,320 |
+      | Operating profit | 84 | 96 |
+      | Operating margin | 7.0% | 8.0% |
+    after: |
+      | Item | FY2025 | FY2026 |
+      | --- | --- | --- |
+      | Net sales | 1,200 | 1,320 |
+      | Operating profit | 84 | 96 |
+      | Operating margin | 7.0% | 7.3% |
+
+not_flagged:
+  ja: 分子か分母の行が無い表、同じ名前の行が二つある表、三つの行の升の数が違う表（列がそろっているか分からない）、数でない升（—、▲、括弧の付いた値）、二つの値の単位が違う列（百万円と千円）は比べません。文では、率か分子か分母の名前が二度出る文、名前のすぐ後ろに値が無い文は比べません。語彙表に無い率（利用率、自己資本比率）は読みません。丸めで届く範囲の率は言いません。
+  en: "A table without the numerator or the denominator row, with two rows of the same name, or whose three rows have different numbers of cells (its columns may not line up), a cell that is not a plain number (—, a negative or bracketed value), and a column whose two values are in different units ($ million and $ thousand) are not compared. A sentence that names the ratio or a term twice, or has no value right after a name, is not compared. A ratio not in the lexicons (utilisation, equity ratio) is not read. A ratio the rounding of the values can reach is not reported."

package/rules/reference-flag-mismatch.yaml

@@ -0,0 +1,74 @@
+id: reference-flag-mismatch
+layer: L3
+status: stable
+how_to_find: reference-flag-mismatch
+word_list: reference-flag
+extra_word_lists: [lab-result-column, reference-column-heading, reference-bound-mark, range-band-word]
+severity: warning
+
+name:
+  ja: 結果と基準値に合わない判定の印
+  en: A flag that does not match the result and its reference range
+
+why:
+  ja: 検査結果の表で、基準値「30〜149 mg/dL」の中の 88 に「高」、基準値「79 U/L 以下」を超える 88 に「基準内」と付いていると、読み手は印を信じて、見るべき値を見落とすか、問題の無い値を気にします。前の回の表から印を写したまま値だけを書き換えたときや、隣の行の印を貼ったときに起きます。列の見出し（結果、基準値、判定）で結果・基準値・判定の列を見つけ、同じ行の結果を基準値と照らします。「30〜149」のように範囲の印だけで書いた基準値は両端を含むと読みます。基準値は、その値までを基準の範囲として示すものだからです。以上・以下・≦は端を含み、未満・超・<は含みません。
+  en: 'When a results table flags 5.2 "H" against a reference range of 4.0–5.6 %, or 18 "Normal" against 30–100 ng/mL, the reader trusts the flag and either misses the value that needs attention or worries about one that does not. It happens when the flags of last time''s table are kept and only the values are updated, or a row''s flag is pasted from its neighbour. The result, reference range and flag columns are found by their headings, and the result of each row is compared with the range on the same row. A range written with a range mark only ("4.0–5.6") includes both ends, since a reference range names the lowest and the highest value it counts as within it. "Or less", "or more", "≤" and "≥" keep their end; "below", "above", "<" and ">" do not.'
+
+message:
+  ja: 「{item}」の {value} は基準値（{range}）の範囲内なのに、判定が「{flag}」です
+  en: '"{item}" is {value}, within its reference range ({range}), but is flagged "{flag}"'
+messages:
+  outside:
+    ja: 「{item}」の {value} は基準値（{range}）の範囲外なのに、判定が「{flag}」です
+    en: '"{item}" is {value}, outside its reference range ({range}), but is flagged "{flag}"'
+  below:
+    ja: 「{item}」の {value} は基準値（{range}）より低いのに、判定が「{flag}」です
+    en: '"{item}" is {value}, below its reference range ({range}), but is flagged "{flag}"'
+  above:
+    ja: 「{item}」の {value} は基準値（{range}）より高いのに、判定が「{flag}」です
+    en: '"{item}" is {value}, above its reference range ({range}), but is flagged "{flag}"'
+
+how_to_fix:
+  ja: 結果と基準値を確かめて、判定の印か、書き間違えた数を直してください。
+  en: Check the result and the reference range, and correct the flag or the mistyped number.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+
+group: facts
+summary:
+  ja: 検査結果の表で、基準値の範囲内の値に「高」、範囲外の値に「基準内」と付いた行
+  en: A lab result flagged high though within its range, or normal though outside it
+example:
+  ja:
+    before: |
+      | 項目 | 結果 | 基準値 | 判定 |
+      | --- | --- | --- | --- |
+      | 中性脂肪 | 88 mg/dL | 30〜149 mg/dL | 高 |
+      | γ-GTP | 88 U/L | 79 U/L 以下 | 基準内 |
+    after: |
+      | 項目 | 結果 | 基準値 | 判定 |
+      | --- | --- | --- | --- |
+      | 中性脂肪 | 88 mg/dL | 30〜149 mg/dL | 基準内 |
+      | γ-GTP | 88 U/L | 79 U/L 以下 | 高 |
+  en:
+    before: |
+      | Test | Result | Reference range | Flag |
+      | --- | --- | --- | --- |
+      | HbA1c | 5.2 % | 4.0–5.6 % | H |
+      | Vitamin D | 18 ng/mL | 30–100 ng/mL | Normal |
+    after: |
+      | Test | Result | Reference range | Flag |
+      | --- | --- | --- | --- |
+      | HbA1c | 5.2 % | 4.0–5.6 % | Normal |
+      | Vitamin D | 18 ng/mL | 30–100 ng/mL | L |
+
+not_flagged:
+  ja: 結果・基準値・判定の列が見出しでそれぞれ一つに決まる表だけを読みます。結果が一つの数でない行（<0.5、陰性）、基準値の無い行、男女で分けた基準値、結果と基準値の単位が違う行（mmol/L と mg/dL）、端が逆に書かれた基準値、知らない判定の印（A〜E の判定区分、要再検査）の行は言いません。判定区分は健診機関ごとの判定基準で決まり、基準値とは別だからです。
+  en: 'Only tables whose result, reference range and flag columns are each named by exactly one heading are read. A row whose result is not one number ("<0.5", "negative"), a row with no range, a range given separately for men and women, a row whose result and range are in different units (mmol/L against mg/dL), a range written high end first, and a flag chaff does not know (a grade A to E, "repeat test") are not reported: a grade follows the clinic''s own criteria, not the reference range.'
+level_meaning:
+  ja: 判定の印が結果と基準値に合わないとき指摘
+  en: reported when a flag does not match the result and its reference range

package/rules/reference-number-repeated.yaml

@@ -0,0 +1,63 @@
+id: reference-number-repeated
+layer: L3
+status: stable
+how_to_find: reference-number-repeated
+severity: warning
+
+name:
+  ja: 明細の表で、同じ領収書・請求書の番号が二つの行にある
+  en: The same receipt or invoice number on two rows of an itemised table
+
+why:
+  ja: 経費精算書や請求の明細では、一つの行が一枚の領収書や請求書で、その番号は表の中で一度しか出てきません。同じ番号が二つの行にあれば、同じ領収書を二度請求しているか、行を写して番号を直し忘れたかのどちらかです。どちらも、読み手は番号を一つずつ照らし合わせないかぎり気づきません。列は見出しの語（領収書番号、伝票番号、請求書番号、Receipt no.、Invoice no.、Ref.）だけで決めます。番号は数字を一つ以上含む升だけを読み、空の升、「-」、「なし」、「N/A」は番号として数えません。全角と半角、大文字と小文字、空白は同じ番号として比べます。
+  en: In an expense claim or an invoice's line items, each row is one receipt or invoice, and its number appears once in the table. The same number on two rows means either the same receipt is claimed twice or a row was copied and its number not changed. Neither is seen unless the reader checks the numbers one by one. The column is decided by its heading words alone (Receipt no., Invoice no., Voucher no., Ref.). Only cells holding at least one digit are read as numbers; a blank cell, a dash, "none" or "N/A" is not. Case, full-width and half-width forms and spaces are ignored when comparing.
+
+message:
+  ja: 「{heading}」の「{number}」は、{firstLine} 行目の行にもあります
+  en: '"{number}" in the column "{heading}" is already on line {firstLine}'
+
+how_to_fix:
+  ja: 二つの行が別の領収書なら正しい番号に直し、同じ領収書なら一方の行を消してください。
+  en: If the two rows are different receipts, correct the number; if they are the same receipt, remove one of the rows.
+
+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: The same receipt or invoice number written on two rows of one itemised table
+example:
+  ja:
+    before: |
+      | 日付 | 領収書番号 | 内容 | 金額 |
+      | --- | --- | --- | --- |
+      | 2026年4月6日 | K-118 | 電車代 | 480円 |
+      | 2026年4月8日 | K-119 | 文具代 | 1,210円 |
+      | 2026年4月9日 | K-119 | タクシー代 | 2,350円 |
+    after: |
+      | 日付 | 領収書番号 | 内容 | 金額 |
+      | --- | --- | --- | --- |
+      | 2026年4月6日 | K-118 | 電車代 | 480円 |
+      | 2026年4月8日 | K-119 | 文具代 | 1,210円 |
+      | 2026年4月9日 | K-120 | タクシー代 | 2,350円 |
+  en:
+    before: |
+      | Date | Receipt no. | Description | Amount |
+      | --- | --- | --- | --- |
+      | April 6, 2026 | K-118 | Train fare | $12.40 |
+      | April 8, 2026 | K-119 | Stationery | $21.10 |
+      | April 9, 2026 | K-119 | Taxi | $35.50 |
+    after: |
+      | Date | Receipt no. | Description | Amount |
+      | --- | --- | --- | --- |
+      | April 6, 2026 | K-118 | Train fare | $12.40 |
+      | April 8, 2026 | K-119 | Stationery | $21.10 |
+      | April 9, 2026 | K-120 | Taxi | $35.50 |
+
+not_flagged:
+  ja: 見出しが領収書・伝票・請求書の番号の語でない列（科目のコード、口座番号、日付、「番号」だけの列）は読みません。番号の列が二つ以上ある表も読みません。数字を含まない升（空、「-」、「なし」、「N/A」）は比べません。二つ以上の番号が繰り返す表や、一つの番号が三つ以上の行にある表は、一枚の伝票の行をまとめて書いた表（請求書とその入金、一枚の領収書の内訳）なので比べません。表が違えば同じ番号でもかまいません。
+  en: 'A column whose heading is not a receipt, voucher or invoice number word (a category code, an account number, a date, a bare "No.") is not read, nor is a table with two such columns. A cell with no digit (blank, a dash, "none", "N/A") is not compared. A table where two or more numbers repeat, or one number is on three rows or more, groups the rows of one slip (an invoice and its payment, the parts of one receipt) and is not compared. The same number in two different tables is fine.'

package/rules/reference-number-variant.yaml

@@ -0,0 +1,81 @@
+id: reference-number-variant
+layer: L3
+status: stable
+how_to_find: reference-number-variant
+word_list: reference-label
+# The labels (予約番号, Booking number, 発注番号, Student number) and what each labels come from the language's reference-label lexicon; numbers after
+# labels of different kinds (a booking number and a confirmation number) are never compared.
+languages: [ja, en]
+severity: warning
+
+name:
+  ja: 予約番号などの文字の入れ違い
+  en: Booking or reference number with two characters swapped
+
+why:
+  ja: 予約確認書や受付の控えでは、予約番号や受付番号が冒頭と、キャンセルや問合せの案内とに何度も書かれます。一か所だけ「MN-48215」が「MN-48251」になっていると、読み手はどちらを伝えればよいか分からず、違う番号を伝えると予約が見つかりません。隣り合う二つの文字の入れ違いは、打ち間違いで最も多い形です。「予約番号」「受付番号」のような同じ種類の語のすぐ後ろに書いた番号どうしを比べ、隣り合う二つの文字だけが入れ違った番号を指します。
+  en: "A confirmation or a receipt writes its booking number more than once: at the top, and again where it says how to cancel or whom to call. When one place reads MN-48251 for MN-48215, the reader cannot tell which to quote, and the wrong one finds no booking. Two neighbouring characters swapped is the commonest slip in typing a number. chaff compares the numbers written right after labels of the same kind (Booking number, Confirmation number) and reports one that is another with two neighbouring characters swapped."
+
+message:
+  ja: 番号「{written}」は、「{other}」の隣り合う文字が入れ違っています
+  en: "The number {written} is {other} with two neighbouring characters swapped"
+
+messages:
+  substituted:
+    ja: ナンバー「{written}」は、この文書の車のナンバー「{other}」と一連番号の一文字だけが違います
+    en: "The plate {written} differs from this document's plate {other} in one character of its serial"
+
+how_to_fix:
+  ja: 正しい番号を確かめて、もう一方を直してください。
+  en: Check which number is right and correct the other.
+
+levels: { strict: error, normal: warning, relaxed: warning }
+
+options:
+  listed_kinds:
+    kind: words
+    default: [item]
+    about:
+      ja: 文書が多くを並べる番号の種類（reference-label の group）。この種類の、語の後ろや表にある番号どうしは比べず、語の無い番号だけを比べる
+      en: Kinds of number a document lists many of (reference-label groups). Two labelled or tabled numbers of such a kind are never compared; only one with no label is
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: A story's booking numbers are made up and need not agree; one may differ on purpose.
+  speech: A transcript writes what was said, numbers misspoken and corrected included.
+
+group: facts
+summary:
+  ja: 同じ文書で、予約番号などの隣り合う文字が入れ違っている所（MN-48215 と MN-48251）
+  en: A booking number written once with two neighbours swapped (MN-48215, MN-48251)
+example:
+  ja:
+    before: |
+      # ご予約の確認
+
+      予約番号：MN-48215
+
+      ご連絡の際は、予約番号 MN-48251 をお伝えください。
+    after: |
+      # ご予約の確認
+
+      予約番号：MN-48215
+
+      ご連絡の際は、予約番号 MN-48215 をお伝えください。
+  en:
+    before: |
+      # Your booking
+
+      Booking number: MN-48215
+
+      When you call, please give your booking number, MN-48251.
+    after: |
+      # Your booking
+
+      Booking number: MN-48215
+
+      When you call, please give your booking number, MN-48215.
+
+not_flagged:
+  ja: 「予約番号」「受付番号」「予約確認番号」「お問い合わせ番号」「社員番号」「学籍番号」「発注番号」「見積番号」「請求書番号」「患者番号」「契約番号」「登録番号」「口座番号」「証券番号」のような語のすぐ後ろ（間は空白と「：」「、」や開き括弧だけ）にある、数字を4つ以上含む英数字の並びだけを番号と見ます。発注番号は取引先の番号を書き写すこともありますが、同じ種類の語の番号どうしで隣り合う二文字だけが入れ違ったものしか指さないので、別の注文の番号は指しません。「原契約番号」「基本契約番号」「旧契約番号」「変更契約番号」「親契約番号」は別の契約の番号を引く語なので、文書自身の「契約番号」とは比べません。「登録番号」「受講番号」は参加者の登録の番号、「申込番号」は申込みの番号として、互いに比べません。「振込先口座番号」「振込元口座番号」は振込の相手の口座の番号を書く語なので、口座自身の「口座番号」とは比べません。「契約者番号」は契約者その人の番号で、証券番号とは見ません。語の無い番号（下に書く品番の形のものを除く）、種類の違う番号（学籍番号と社員番号、予約番号と受付番号、請求書番号と注文番号、見積番号と注文番号や請求書番号、登録番号と申込番号）、一文字だけ違う番号、離れた文字の入れ違い、二か所以上入れ違った番号は指しません。自動車のナンバー（ひばり野 330 ね 48-15）の形に合う並びは、語が「登録番号」でも自動車のナンバーとして読みます。ナンバーだけは、文書が一台の車のことを書いているとき（その車のナンバーを「登録番号：」のような語と番号だけの行に一つだけ書き、ほかのナンバーは一つだけで、その語が文の初めにあるとき。「代車の登録番号」のように語の前に語があれば別の車と見ます）に限って、地名・分類番号・かなが同じで一連番号が一文字だけ違うものも指します。「ナンバー」だけの語や英語の「Registration」だけの語は、ナンバーの語として読みません。「品番」「商品コード」「品目コード」は商品の番号の語です。表の行や列の見出しにこの語を書いた升の品番も、語の後ろの品番と同じに読みます。語の無い品番（「GP-0521の替芯」）は、英字と「-」と数字4つ以上の形（GP-0521）のときだけ、語の後ろか表にある品番のちょうど一つと隣り合う二文字だけが入れ違っていれば指します。その書き方の品番が文書のどこかで語の後ろか表にあれば、別の商品の品番と見て指しません（カタログの表に並ぶ AB-1234 と AB-1243 は二つの商品です）。語の後ろや表にある品番どうしも、別の商品の品番として比べません（この扱いをする種類は listed_kinds で決めます）。二つ以上の品番のどれとも読めるもの、英字や「-」の無い番号（48251）も指しません。「会員番号」「会員ID」の会員の番号と、「お客様番号」の番号は、別の番号になり得るので比べません。語のすぐ後ろの番号を「HM 5520 8137」のように空白一つずつで区切って書いたときは、続く並びがどれも4文字以上の大文字と数字で数字を含む間を一つの番号と読み、行の終わりや、語（「の方」「2名」）の前で止めます。
+  en: "Only letters and digits right after a label (booking number, reservation number, confirmation number, reference number, employee number, student number, PO number, quote or estimate number, invoice number, patient number, contract or agreement number, registration number, account number, policy number), with nothing but spaces, a colon, a comma or an opening bracket between, are read, and only when they hold four digits or more. A PO number may be the buyer's, copied from another document, but only two numbers of one kind that differ by two neighbours swapped are reported, so a different order's number is not. An original, master, former, amended or parent contract number (and an amendment number) cites another contract, so it is never compared with the document's own contract number. A registration number labels an attendee's registration and an application number an application, so the two are never compared. A payee's, beneficiary's, payer's or sender's account number labels the other side of a transfer, so it is never compared with the account's own account number; a policyholder number is not read as a policy number. Unlabelled codes (but for item codes, below), numbers of different kinds (a student number and an employee number, a booking number and an order number, an invoice number and an order number, a quote number and an order or invoice number, a registration number and an application number), numbers that differ in one character, swaps of characters that are not neighbours and numbers with more than one swap are not reported. A bare quote is not read as a label, since it is also a verb (quote your PO number). A plate number, number plate or licence plate is a vehicle's and is never compared with a registration number; a bare Registration label is not read as a plate, since an attendee's registration is written so too. An item code, item no., SKU or product code labels an item; a code in a table under such a label, in its row or its column, is read as if written after it. A code with no label (Refills for GP-0521) is reported only in the shape letters, a hyphen and four digits or more, and only when it is exactly one labelled or tabled code with two neighbours swapped. When the document labels or tables that writing itself anywhere, it is another item and is not reported (a catalog's AB-1234 and AB-1243 are two items), and two labelled or tabled item codes are never compared with each other (listed_kinds names the kinds read so); nor is a code two labelled codes swap to, or a number with no letters or hyphen (48251). A member number or member ID and a customer number may be different numbers, so they are never compared. A number written in groups one space apart (HM 5520 8137) is read as one while each further group is four or more capitals and digits holding a digit, stopping at the line's end or before a word or a short count (expires, 100 copies)."