chaffjs 0.30.0 → 0.32.0

package/rules/step-time-sum-mismatch.yaml

@@ -0,0 +1,65 @@
+id: step-time-sum-mismatch
+layer: L3
+status: stable
+how_to_find: step-time-sum-mismatch
+word_list: step-time-total
+extra_word_lists: [step-time-not-own, approximate-marker, unit-time]
+severity: warning
+
+name:
+  ja: 所要時間が、手順に書いた時間の和と合わない
+  en: A total time that is not the sum of the steps' times
+
+why:
+  ja: 「所要時間：60分」と書いたレシピや手順書で、番号を付けた手順の時間（（10分）、40分焼く）を足すと80分になると、読み手は時間の見積もりを誤ります。手順を足したり時間を書き換えたりしたときに、所要時間だけ直し忘れると起きます。手順の外に所要時間の見出し（所要時間、合計時間、合計）のすぐ後ろに書いた時間が一つだけあり、番号付きの手順の並びが一つで、どの手順もその手順にかかる時間をちょうど一つ書いているときに、その和と比べます。所要時間か手順の時間に目安の印（約、程度）があるときは、所要時間の1割（少なくとも5分）までの差を合うとみなします。
+  en: 'When a recipe or a guide says "Total time: 60 minutes" and the times written in its numbered steps ("(10 minutes)", "bake for 40 minutes") add up to 80, the reader plans with the wrong figure. It happens when a step is added or a time is changed and the total is not. The rule runs when the document states one total outside its steps (a length right after Total time, Total, Time required) and it has one numbered list whose every step states exactly one time of its own, and compares the two. When the total or a step time is rough ("about 1 hour", "20 minutes or so"), a difference up to a tenth of the total, and at least 5 minutes, agrees.'
+
+message:
+  ja: 「{written}」が、手順{steps}つに書いた時間の和（{sum}分）と合いません
+  en: '"{written}" is not the sum of the times in the {steps} steps ({sum} minutes)'
+
+how_to_fix:
+  ja: 所要時間と手順の時間のどちらが正しいかを確かめて、片方を直してください。手順を同時に進める（煮ている間にソースを作る）なら、そう書き添えてください。
+  en: Check which is right, the total or the steps' times, and correct the other. If steps run at the same time (the sauce is made while the meat rests), say so.
+
+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 recipe or guide whose total time is not the sum of its steps' times
+example:
+  ja:
+    before: |
+      所要時間：30分
+
+      1. 玉ねぎを薄切りにします（5分）。
+      2. 弱火で炒めます（20分）。
+      3. 水を加えて煮ます（15分）。
+    after: |
+      所要時間：40分
+
+      1. 玉ねぎを薄切りにします（5分）。
+      2. 弱火で炒めます（20分）。
+      3. 水を加えて煮ます（15分）。
+  en:
+    before: |
+      Total time: 30 minutes
+
+      1. Slice the onions (5 minutes).
+      2. Fry them over a low heat (20 minutes).
+      3. Add the water and simmer (15 minutes).
+    after: |
+      Total time: 40 minutes
+
+      1. Slice the onions (5 minutes).
+      2. Fry them over a low heat (20 minutes).
+      3. Add the water and simmer (15 minutes).
+
+not_flagged:
+  ja: 時間を書いていない手順や、時間を二つ以上書いた手順が一つでもあるとき、範囲で書いた時間（10〜15分）、その手順にかかる時間でないもの（10分後、5分ごと、残り5分）、温度（180℃に予熱）は、和を取らず言いません。所要時間が二つの違う値で書いてあるとき、範囲で書いてあるとき、番号付きの手順の並びが二つ以上ある（別の作業の手順かもしれない）ときも言いません。手順を同時に進める作り方は読み分けられないので、そのときは指すことがあります。
+  en: 'A step with no time or with two, a range ("10 to 15 minutes"), a time that is not how long the step takes ("after 10 minutes", "every 5 minutes", "10 minutes later") and a temperature ("preheat to 180°C") make the rule stop rather than add up. Two different totals, a total given as a range, and a document with two or more numbered lists (they may be separate procedures) are not compared either. Steps that run at the same time cannot be told apart, and may be reported.'

package/rules/stock-transition.yaml

@@ -38,7 +38,7 @@ off_for:
 group: ai-tells
 summary:
   ja: 「さらに」「加えて」「このように」で始まる文が多く、何がどう繋がるのかを言わずに並べている所
-  en: Too many sentences opening with "Moreover", "Additionally" or "Furthermore", listing without saying how they connect
+  en: Too many sentences opening with "Moreover" or "Additionally"
 example:
   ja:
     pad: true

package/rules/summary-fact-mismatch.yaml

@@ -31,7 +31,7 @@ off_for:
 group: facts
 summary:
   ja: 冒頭や概要の節に書いた値（締切、料金など）が、本文の同じ項目の値と違う所
-  en: A value in the opening or the summary (a deadline, a fee) that differs from the same item in the body
+  en: A value in the summary (a deadline, a fee) that differs from the body
 example:
   ja:
     before: |

package/rules/table-header-variant.yaml

@@ -29,7 +29,7 @@ use_for: [blog, business, technical, docs, academic, legal, literature, speech]
 group: consistency
 summary:
   ja: 同じ欄の見出しを、表によって「担当者」と「担当」のように書き分けている所
-  en: The same column header written two ways across a document's tables, such as Owner and Owners
+  en: The same column header written two ways across tables (Owner and Owners)
 
 example:
   ja:

package/rules/table-unit-mix.yaml

@@ -0,0 +1,82 @@
+id: table-unit-mix
+layer: L3
+status: stable
+how_to_find: table-unit-mix
+word_list: table-scale-unit
+extra_word_lists: [table-unit-caption, total-label]
+severity: warning
+
+name:
+  ja: 表の中で金額の桁の単位が混ざっている
+  en: A table that mixes scales of amount
+
+why:
+  ja: 「（単位：百万円）」の表に一行だけ千円で書いた数（52,000）や「110,000千円」があると、読み手はその行を千倍に読み違えます。別の資料から行を写したときや、百万円を千円に直したまま単位を書かなかったときに起きます。表のすぐ上に「単位」と桁の単位（百万円、千円）を書いた短い行があればそれを表の単位と読み、無ければ升の多くに付いた桁の単位を表の単位と読みます。表の単位と違う桁の単位で書いた升（一行に一つ）と、表の単位の下で、一行だけほかの行の千倍に書いた行を指します。
+  en: When a table "(In millions of US dollars)" has one row in thousands (52,000 among 1,200 and 84) or one cell written "$110,000 thousand", the reader takes that row as a thousand times what it is. It happens when a row is copied from another statement, or when millions are turned into thousands and the unit is not changed. A short line right above the table with "in" or "of" and one word of scale (millions, thousands) is read as the table's unit; without one, the word of scale most cells carry is. A cell written in another scale than the table's is pointed out (once per row), and so is a row, under a stated unit, entered a thousand times as large as the others.
+
+message:
+  ja: 「{item}」の「{written}」が、表の単位（{unit}）と違う桁の単位で書かれています
+  en: '"{item}" is written "{written}", in another scale than the table''s ({unit})'
+
+messages:
+  unit:
+    ja: 「{item}」の「{written}」が、表の単位（{unit}）と違う桁の単位で書かれています
+    en: '"{item}" is written "{written}", in another scale than the table''s ({unit})'
+  row:
+    ja: 「{item}」の「{written}」が、ほかの行の千倍ほどあります（{unit}の表なら {reading} ではないか）
+    en: '"{item}" is "{written}", about a thousand times the other rows (in {unit}, {reading}?)'
+
+how_to_fix:
+  ja: その行の数を表の単位に直すか、行の単位が本当に違うなら、行の名前に単位を書いてください（「従業員数（人）」）。
+  en: Write the row in the table's unit, or, if the row really is in another unit, put its unit in the row's label ("Employees (persons)").
+
+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 cell in thousands in a table in millions, or a row a thousand times the others
+example:
+  ja:
+    before: |
+      （単位：百万円）
+
+      | 項目 | 前期 | 当期 |
+      | --- | --- | --- |
+      | 売上高 | 1,200 | 1,320 |
+      | 営業利益 | 84 | 96 |
+      | 経常利益 | 80 | 92 |
+      | 当期純利益 | 52,000 | 60,000 |
+    after: |
+      （単位：百万円）
+
+      | 項目 | 前期 | 当期 |
+      | --- | --- | --- |
+      | 売上高 | 1,200 | 1,320 |
+      | 営業利益 | 84 | 96 |
+      | 経常利益 | 80 | 92 |
+      | 当期純利益 | 52 | 60 |
+  en:
+    before: |
+      | Item | Prior year | Current year |
+      | --- | --- | --- |
+      | Net sales | $2,400 million | $2,640 million |
+      | Operating profit | $168 million | $198 million |
+      | Net profit | $110,000 thousand | $130,000 thousand |
+    after: |
+      | Item | Prior year | Current year |
+      | --- | --- | --- |
+      | Net sales | $2,400 million | $2,640 million |
+      | Operating profit | $168 million | $198 million |
+      | Net profit | $110 million | $130 million |
+
+not_flagged:
+  ja: 単位を言う行の無い表で、大きい金額だけ大きい単位で書いた升（「12億円」と「300百万円」）と、表の単位に満たない小さい金額を小さい単位で書いた升（百万円の表の「500千円」）は言いません。千倍の行は、表のすぐ上に単位を書いた表でだけ探し、行の数がどの列でもちょうど千の倍数で、ほかのどの行よりも十倍以上大きく、千で割るとほかの行の中に収まるときだけ指します。総資産のように本当に大きい行は、どの列でもちょうど千の倍数になることがまずないので言いません。合計の行、名前に括弧で単位を書いた行（従業員数（人））、比べる列が二つ未満か比べる行が二つ未満の表、千倍に見える行が二行以上ある表も言いません。
+  en: In a table with no caption of unit, a large amount written with a larger word ("$2.4 billion" among "$130 million") and a small amount in a smaller word than the table's ("$500 thousand" in a table in millions) are not reported. A row a thousand times the others is looked for only under a caption of unit, and is reported only when its figure in every column is whole thousands, at least ten times every other row, and falls among them once divided by a thousand. A genuinely large row, such as total assets, is almost never whole thousands in every column and is left alone, as are a total row, a row whose label gives its own unit in brackets ("Employees (persons)"), tables with fewer than two columns or two other rows to compare, and tables where more than one row stands out.
+level_meaning:
+  ja: 表の中で桁の単位が混ざっているとき指摘
+  en: reported when a table mixes scales of amount

package/rules/taigen-dome-in-prose.yaml

@@ -34,7 +34,7 @@ off_for:
 group: readability
 summary:
   ja: 名詞で終わる文（体言止め）が本文に続き、言いかけのように読める所
-  en: Many Japanese sentences in the body that stop on a noun, which read as unfinished
+  en: Many Japanese sentences that stop on a noun and read as unfinished
 example:
   ja:
     config: { rules: { taigen-dome-in-prose: strict } }

package/rules/tax-mismatch.yaml

@@ -3,7 +3,8 @@ layer: L3
 status: stable
 how_to_find: tax-amount
 # The words of a tax row and of an included tax come from the language's tax-label and tax-included-word lexicons; the
-# subtotal row is found with total-label, the lexicon total-mismatch reads.
+# subtotal row is found with total-label, the lexicon total-mismatch reads. The price columns of a price list come from
+# tax-price-column.
 requires: [quantities]
 languages: [ja, en]
 severity: error
@@ -13,13 +14,18 @@ name:
   en: A tax that is not its rate of the subtotal
 
 why:
-  ja: 見積書や請求書の「消費税（10%）」の金額が、小計の10%と合わないと、読み手は税の計算を確かめ直し、合計も信じられなくなります。合計の額に税率を掛けてしまったときや、小計を直して税を直し忘れたときに起きます。表か箇条書きで、税の語（消費税・税額）で始まり率を書いた行の金額を、上の小計の行の金額（小計の行が無ければ上の項目の和）に率を掛けた額と比べます。
-  en: When the "Sales tax (10%)" of a quote or an invoice is not 10% of the subtotal, the reader has to work the tax out again and can no longer trust the total. It happens when the rate is applied to the total instead of the subtotal, or when the subtotal is changed and the tax is not. In a list or a table, the amount of a line starting with a tax word (Tax, Sales tax, VAT) and giving a rate is compared with that rate of the subtotal line above it (or, with no subtotal line, of the sum of the items above).
+  ja: 見積書や請求書の「消費税（10%）」の金額が、小計の10%と合わないと、読み手は税の計算を確かめ直し、合計も信じられなくなります。合計の額に税率を掛けてしまったときや、小計を直して税を直し忘れたときに起きます。表か箇条書きで、税の語（消費税・税額）で始まり率を書いた行の金額を、上の小計の行の金額（小計の行が無ければ上の項目の和）に率を掛けた額と比べます。価格表で税抜と税込の価格を並べた表（「1箱の価格（税抜）」と「1箱の価格（税込・10%）」）では、行ごとに、税込の価格を税抜の価格に率を足した額と比べます。率は税込の列の見出しの率、無ければ文書が「消費税10%」のように書いた率です。サービス料（10%）の行も同じように比べ、その下の税は小計にサービス料を足した額に掛けたものとしても読みます。
+  en: When the "Sales tax (10%)" of a quote or an invoice is not 10% of the subtotal, the reader has to work the tax out again and can no longer trust the total. It happens when the rate is applied to the total instead of the subtotal, or when the subtotal is changed and the tax is not. In a list or a table, the amount of a line starting with a tax word (Tax, Sales tax, VAT) and giving a rate is compared with that rate of the subtotal line above it (or, with no subtotal line, of the sum of the items above). In a price list with a price before tax and a price with tax ("Pack price (excl. tax)", "Pack price (incl. 8% tax)"), each row's price with tax is compared with the price before tax plus the rate. The rate is the one in the heading of the price with tax, else the one the document gives ("8% sales tax"). A service charge line giving a rate is compared the same way, and a tax below it may be on the subtotal with the service charge added.
 
 message:
   ja: 税額「{written}」が、上の金額の{rate}（{expected}）と合いません
   en: "The tax {written} is not {rate} of the amount above it ({expected})"
 
+messages:
+  price:
+    ja: 税込の価格「{written}」が、税抜の価格「{base}」に{rate}の税を足した額（{expected}）と合いません
+    en: "The price with tax {written} is not the price before tax {base} plus {rate} tax ({expected})"
+
 how_to_fix:
   ja: 小計と税率を確かめて、税額を計算し直してください。合計も一緒に直します。
   en: Check the subtotal and the rate and work the tax out again. Correct the total with it.
@@ -32,8 +38,8 @@ off_for:
 
 group: facts
 summary:
-  ja: 見積書や請求書で、「消費税（10%）」の金額が小計の10%と合わない所
-  en: A tax line in a quote or an invoice whose amount is not its rate of the subtotal
+  ja: 請求書の消費税や価格表の税込価格が、税率で計算した額と合わない所
+  en: A tax line, or a price list's price with tax, that does not match the tax rate
 example:
   ja:
     before: |
@@ -67,5 +73,5 @@ example:
       | Sales tax (10%) | $800 |
 
 not_flagged:
-  ja: 端数は切り捨て・四捨五入・切り上げのどれでも合っていると読みます。率を書いていない税の行、合計に含まれる税（「うち消費税」「内税」）の行、率の違う税の行が並ぶ表（軽減税率の8%と10%）、小計と税の行の間に金額の行（値引き・送料）がある表は比べません。文の中に書いた税は読みません。
-  en: Rounding down, to the nearest or up are all read as right. A tax line with no rate, a line for tax included in the total ("tax included"), a table with tax lines of different rates, and a table with an amount line (a discount, shipping) between the subtotal and the tax are not compared. A tax written in a sentence is not read.
+  ja: 端数は切り捨て・四捨五入・切り上げのどれでも合っていると読みます。率を書いていない税の行、合計に含まれる税（「うち消費税」「内税」）の行、率の違う税の行が並ぶ表（軽減税率の8%と10%）、小計と税の行の間に金額の行（値引き・送料）がある表は比べません。文の中に書いた税は読みません。価格表では、見出しが税抜・税込の語と率のほかでも違う二つの列（「単価（税抜）」と「1箱の価格（税込）」）、率が見出しにも文書にも無い表、使う率と違う率も書いた文書（軽減税率の8%と10%）は比べません。
+  en: Rounding down, to the nearest or up are all read as right. A tax line with no rate, a line for tax included in the total ("tax included"), a table with tax lines of different rates, and a table with an amount line (a discount, shipping) between the subtotal and the tax are not compared. A tax written in a sentence is not read. In a price list, two columns whose headings differ in more than the before-tax and with-tax words and the rate ("Unit price (excl. tax)" beside "Pack price (incl. tax)"), a table with no rate in its heading or in the document, and a document that also gives another rate (a reduced rate beside the standard one) are not compared.

package/rules/tier-threshold-mismatch.yaml

@@ -0,0 +1,73 @@
+id: tier-threshold-mismatch
+layer: L3
+status: stable
+how_to_find: tier-threshold
+# The keys that state a member's tier come from tier-label, the units a threshold is counted in from tier-unit, and the words
+# that bound a band from range-band-word (range-band-mismatch's reading).
+extra_word_lists: [tier-label, tier-unit, range-band-word]
+severity: warning
+
+name:
+  ja: 会員の値が、書いたランクの基準に当たらない
+  en: A member's tier that their own points or nights do not reach
+
+why:
+  ja: ポイントや宿泊の明細で、ランクの表が「ゴールド：50,000ポイント以上」なのに、「会員ランク：ゴールド」の会員の「年間獲得ポイント：42,400ポイント」では、ランクと値のどちらが正しいか読み手は決められません。値を書き換えてランクを直し忘れたとき、別の会員の値を写したときに起きます。文書のランクの表（一つ目の列がランクの名前、別の列が基準）か箇条書き（「ゴールド：前年度のご宿泊数が20泊以上」）の基準と、同じ節に書いた会員のランクと値を比べます。下の端だけを書いたランク（20泊以上）は、一つ上のランクが始まる手前までと読みます。
+  en: 'On a points or hotel statement, when the tier table says "Gold: 50,000 points or more" and a member stated as "Tier: Gold" has "Points earned last year: 42,400 points", the reader cannot tell whether the tier or the points are right. It happens when the value is updated and the tier is not, or when another member''s value is copied. The bands of the document''s tier table (the tier''s name in the first column, its threshold in another) or tier list ("Gold: 20 nights or more stayed last year") are compared with the tier and the value stated in one section. A tier written with its lower end only (20 nights or more) is read as running up to where the next tier starts.'
+
+message:
+  ja: ランク「{tier}」の基準は「{band}」ですが、「{value}」は「{actual}」の基準に当たります
+  en: 'The tier "{tier}" needs "{band}", but "{value}" falls in "{actual}"'
+
+how_to_fix:
+  ja: 会員の値とランクの基準を確かめて、ランクか値の書き間違えたほうを直してください。
+  en: Check the member's value against the tier thresholds, and correct the tier or the value, whichever is wrong.
+
+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 stated tier whose member's points or nights fall outside that tier's band
+example:
+  ja:
+    before: |
+      - 会員ランク：ゴールド
+      - 年間獲得ポイント：42,400ポイント
+
+      | ランク | 年間獲得ポイント |
+      | --- | --- |
+      | シルバー | 10,000ポイント以上50,000ポイント未満 |
+      | ゴールド | 50,000ポイント以上 |
+    after: |
+      - 会員ランク：シルバー
+      - 年間獲得ポイント：42,400ポイント
+
+      | ランク | 年間獲得ポイント |
+      | --- | --- |
+      | シルバー | 10,000ポイント以上50,000ポイント未満 |
+      | ゴールド | 50,000ポイント以上 |
+  en:
+    before: |
+      - Status: Platinum
+      - Nights stayed last year: 24 nights
+
+      - Gold: 20 nights or more stayed last year
+      - Platinum: 30 nights or more stayed last year
+    after: |
+      - Status: Gold
+      - Nights stayed last year: 24 nights
+
+      - Gold: 20 nights or more stayed last year
+      - Platinum: 30 nights or more stayed last year
+
+not_flagged:
+  ja: ランクの名前が表や箇条書きの名前と同じ字で、基準と会員の値が同じ単位（ポイント、泊、回、円）のときだけ比べます。残高や次のランクまでに要る数の行は会員の値に数えません。同じ節に、その単位の会員の値が二つ以上あるもの、基準の幅が重なるもの、基準が二つの単位にまたがるものは比べません。値が下の端だけを書いた基準を上に超えたもの（20泊以上のランクで35泊）と、値がどのランクの基準にも当たらないものは言いません。文の中に書いたランクや値は読みません。
+  en: "Only a tier named exactly as in the table or list, with the thresholds and the member's value in one unit (points, nights, $), is compared. A balance, or what the next tier needs, is not counted as the member's value. Nothing is compared when the section states two or more member values in that unit, when two bands overlap, or when the thresholds are in different units. A value above a tier written with its lower end only (35 nights for a tier of 20 nights or more), and a value that falls in no tier, are not reported. A tier or a value written in a sentence is not read."
+level_meaning:
+  ja: 会員の値が、書いたランクの基準に当たらないとき指摘
+  en: reported when a member's value falls outside the stated tier's band

package/rules/time-order.yaml

@@ -10,8 +10,8 @@ name:
   en: A time out of order in a day's schedule
 
 why:
-  ja: 旅程や式次第のように、頭に時刻を書いた項目を並べた箇条書きや表で、ひとつだけ前の項目より早い時刻があると、書き間違いか順番の入れ替わりかを読み手が確かめることになり、集まる時刻を間違える人も出ます。一日の予定は早い順に並ぶので、その順に逆らう時刻を指します。日付の見出しが変わるところ、行の頭の日付が変わるところで一日を区切ります。23:30 の次の 0:15 のように夜をまたぐ時刻は、翌日の印（翌、+1）があれば翌日の時刻として読みます。
-  en: In a list or a table whose items start with a time, such as an itinerary or a programme, one time earlier than the item before it makes the reader check whether it is a typo or a swapped row, and someone turns up at the wrong time. A day's schedule runs from the earliest time, so a time against that order is pointed out. A day ends where a date heading or the date at the start of a row changes. A time past midnight, such as 0:15 after 23:30, is read as the next day's when it is marked so (+1, "next day").
+  ja: 旅程や式次第のように、頭に時刻を書いた項目を並べた箇条書きや表で、ひとつだけ前の項目より早い時刻があると、書き間違いか順番の入れ替わりかを読み手が確かめることになり、集まる時刻を間違える人も出ます。一日の予定は早い順に並ぶので、その順に逆らう時刻を指します。日付の見出しが変わるところ、行の頭の日付が変わるところで一日を区切ります。23:30 の次の 0:15 のように夜をまたぐ時刻は、翌日の印（翌、+1）があれば翌日の時刻として読みます。開場と開演、受付開始と開始、集合と出発のように、語で前後の決まった二つの時刻も比べます。開場が開演より遅いと、入れない時間に公演が始まってしまいます。
+  en: In a list or a table whose items start with a time, such as an itinerary or a programme, one time earlier than the item before it makes the reader check whether it is a typo or a swapped row, and someone turns up at the wrong time. A day's schedule runs from the earliest time, so a time against that order is pointed out. A day ends where a date heading or the date at the start of a row changes. A time past midnight, such as 0:15 after 23:30, is read as the next day's when it is marked so (+1, "next day"). Two times whose labels fix their order, such as doors open and the show's start, or meeting time and departure, are compared too, since doors that open after the start leave the audience outside when the show begins.
 
 message:
   ja: 「{time}」が、前後の時刻の並びから外れています（前は「{previous}」）
@@ -21,6 +21,9 @@ messages:
   first:
     ja: 「{time}」が、後の時刻の並びから外れています（次は「{next}」）
     en: "{time} breaks the order of the times after it (before {next})"
+  pair:
+    ja: 「{earlier_label}」の「{time}」が、後に来るはずの「{later_label}」の「{later}」より遅くなっています
+    en: "{earlier_label} at {time} is later than {later_label} at {later}, which should come after it"
 
 how_to_fix:
   ja: 時刻を確かめて、書き間違いなら直し、順番が違うなら並べ替えてください。
@@ -61,5 +64,5 @@ example:
       - 6:30 PM Dinner
 
 not_flagged:
-  ja: 時刻が二つしかない並び、早い順に並ぶ時刻が半分以下の並び（時刻で並べた一覧ではない）、項目の頭でなく文の中に書いた時刻は比べません。夜をまたいで半日より大きく戻る時刻（23:30 の次の 0:15）は、翌日の印が無くても翌日の時刻と読みます。「現地時間」の付いた時刻や時間帯の印が変わる所では一日を区切ります。
-  en: 'A run of only two times, a list where no more than half of the times are in order (not a schedule), and times written inside a sentence rather than at the start of an item are not compared. A time more than half a day earlier than the one before it (0:15 after 23:30) is read as past midnight even without a mark. A "local time" mark, or a change of time zone, starts a new day.'
+  ja: 時刻が二つしかない並び、早い順に並ぶ時刻が半分以下の並び（時刻で並べた一覧ではない）、項目の頭でなく文の中に書いた時刻は比べません。夜をまたいで半日より大きく戻る時刻（23:30 の次の 0:15）は、翌日の印が無くても翌日の時刻と読みます。「現地時間」の付いた時刻や時間帯の印が変わる所では一日を区切ります。語の決まった二つの時刻は、日付が違うもの（間に別の日付の見出しがある）、時間帯の印が違うもの、半日より大きく戻るもの（夜をまたいだ時刻）、一行に時刻が二つあるもの（範囲）は比べません。開場と開演が二組あれば、それぞれ近いほうと比べます。
+  en: 'A run of only two times, a list where no more than half of the times are in order (not a schedule), and times written inside a sentence rather than at the start of an item are not compared. A time more than half a day earlier than the one before it (0:15 after 23:30) is read as past midnight even without a mark. A "local time" mark, or a change of time zone, starts a new day. Two labelled times are not compared when they fall on different dates (a date heading between them), when their time-zone marks differ, when the later one is more than half a day back (past midnight), or when a line holds two times (a range). With two shows, each start is compared with the doors written nearest to it.'

package/rules/time-range-reversed.yaml

@@ -0,0 +1,53 @@
+id: time-range-reversed
+layer: L3
+status: stable
+how_to_find: time-range-reversed
+requires: [dates]
+severity: warning
+
+name:
+  ja: 時刻の範囲の終わりが始まりより前
+  en: A time range that ends before it starts
+
+why:
+  ja: 「15:15〜14:15」のように、時刻の範囲の終わりが始まりより前だと、読み手はいつ終わるのかを問い合わせることになり、次の予定の時刻も信じられなくなります。時刻を一つだけ直したときや、前の行から書き写したときに起きます。二つの時刻の間が範囲の記号（〜、–）だけのとき、「から」でつなぎ「まで」で閉じるとき、「from … to」のときを範囲として比べます。片方にだけ午前・午後を書いた範囲は、もう片方も同じと読みます。勤務表のように始まりと終わりを別の列（始業と終業、出勤と退勤、開始と終了）に書いた表も、行ごとに比べます。
+  en: 'When a time range such as "15:15–14:15" ends before it starts, the reader has to ask when it really ends, and the times after it are in doubt too. It happens when only one of the two times is changed, or when a line is copied from the one before. Two times are read as a range when only a range mark (–, —) or a word such as "until" stands between them, or when they are written "from … to …". When only one side carries a.m. or p.m., the other is read the same way ("2:00–1:30 pm" is 2 pm to 1:30 pm). A table with the start and the end in separate columns, such as a timesheet (Time in and Time out, Start and End), is compared row by row.'
+
+message:
+  ja: 時刻の範囲「{range}」の終わりが始まりより前です
+  en: 'The time range "{range}" ends before it starts'
+
+messages:
+  columns:
+    ja: 「{end_label}」の「{end}」が「{start_label}」の「{start}」より前です
+    en: '{end_label} "{end}" is before {start_label} "{start}"'
+
+how_to_fix:
+  ja: 始まりと終わりの時刻を確かめて、書き間違えたほうを直してください。夜をまたぐ範囲なら、終わりに「翌」を付けてください。
+  en: Check both times and correct the wrong one. If the range runs past midnight, mark the end as the next day.
+
+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: 「15:15〜14:15」のように、時刻の範囲の終わりが始まりより前の所
+  en: A time range whose end comes before its start
+example:
+  ja:
+    before: |
+      | 15:15〜14:15 | 事例紹介 |
+    after: |
+      | 15:15〜16:15 | 事例紹介 |
+  en:
+    before: |
+      The workshop runs from 2:00 to 1:30 pm.
+    after: |
+      The workshop runs from 2:00 to 3:30 pm.
+
+not_flagged:
+  ja: 終わりに翌日の印のある範囲（22:00〜翌6:00）、三時間以上戻る範囲（夜をまたぐ 22:00〜6:00、十二時間制の 9:00〜5:00）、「から」だけで「まで」の無いもの（14時から13時に変更）、時刻の印の無い数（2〜1、1時間〜30分）は比べません。片方だけに午前・午後を書いた範囲は、正午をまたぐ書き方（8:00〜午後6:00）があるので、一時間未満の戻りだけを言います。両方に同じ午前・午後を書いた範囲（午前9時〜午前5時）は、戻りの幅を問わず言います。勤務表の行は、文書に夜勤の印（夜勤、深夜、翌6:00、25:00）があれば比べず、実働の列が夜をまたいだ長さと合う行（22:00、6:00、休憩1:00、実働7.0時間）も言いません。
+  en: 'A range whose end is marked as the next day ("22:00–6:00 +1"), a range that goes back three hours or more (overnight, as 22:00–6:00, or a 12-hour clock, as 9:00–5:00), "from … to …" in a sentence that changes a time ("moved from 3:00 to 2:00"), and numbers without a time mark are not compared. Where only one side carries a.m. or p.m., a range may cross noon ("8:00–6:00 pm"), so only a step back of less than an hour is reported. A range with the same a.m. or p.m. on both sides (9:00 AM – 5:30 AM) is reported however far it goes back. A timesheet row is not compared when the document shows night work (night shift, overnight, 6:00 +1, 25:00), nor when its hours fit a shift past midnight (22:00, 6:00, a 0:30 break, 7.50 hours).'

package/rules/title-case-consistency.yaml

@@ -10,8 +10,8 @@ name:
   en: Heading capitalisation is inconsistent
 
 why:
-  ja: Title Case と sentence case のどちらが正しいかは決めません。1 つの文書で混ざっていると、見出しの階層が変わったように見えます。文書の題名（先頭にある深さ 1 の見出しが 1 つだけのとき）は名前なので比べません。節の見出しが同数に割れたときだけ、題名の流儀に合わせます。
-  en: Neither Title Case nor sentence case is wrong. Mixed within one document, the headings look like they change level. The document's title (a single top-level heading that opens it) is a name and is not compared; when the section headings split evenly, the title's style decides.
+  ja: Title Case と sentence case のどちらが正しいかは決めません。1 つの文書で混ざっていると、見出しの階層が変わったように見えます。文書の題名（先頭にある深さ 1 の見出しが 1 つだけのとき）は名前なので比べません。節の見出しが同数に割れたときだけ、題名の流儀に合わせます。頭の番号の札（Section 3. / Day 1:）と、曜日・月の名（どちらの流儀でも大文字）は、どちらの流儀の証拠にも数えません。
+  en: Neither Title Case nor sentence case is wrong. Mixed within one document, the headings look like they change level. The document's title (a single top-level heading that opens it) is a name and is not compared; when the section headings split evenly, the title's style decides. A leading label (Section 3., Day 1:) and the names of weekdays and months, capitalised in either style, count as evidence for neither.
 
 message:
   ja: この見出しだけ他と大文字化の流儀が違います（文書の中で {count} 個）

package/rules/toc-heading-mismatch.yaml

@@ -28,7 +28,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: structure
 summary:
   ja: 目次（「目次」「Contents」の見出しの下の箇条書き）の項目のうち、文書のどの見出しとも合わないもの
-  en: An entry of the table of contents (the list under a "Contents" heading) that matches no heading of the document
+  en: A table of contents entry that matches no heading of the document
 example:
   ja:
     before: |

package/rules/topic-predicate-distance.yaml

@@ -33,7 +33,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: readability
 summary:
   ja: 「会議は」のように主題を出してから、文の終わりの述語まで長く待たせる文
-  en: A Japanese sentence that names its topic (〜は) early and makes the reader wait long for its predicate
+  en: A Japanese sentence that makes the reader wait long for its verb
 example:
   ja:
     before: |

package/rules/total-mismatch.yaml

@@ -10,8 +10,8 @@ name:
   en: A total that is not the sum of its items
 
 why:
-  ja: 見積や請求の「合計」が、上に並べた金額の和と合わないと、読み手はどちらが正しいのかを計算し直すことになります。行を足したり消したりしたあとに、合計だけ直し忘れると起きます。箇条書きか表で、合計の語（合計・小計）で始まる行を、同じ単位で同じ列の金額の和と比べます。契約書のように一つの文に書いた合計（「保守費60,000円、運用費30,000円とし、合計100,000円とする」「月額150,000円（内訳：…）」）も、その文に並べた同じ単位の金額の和と比べます。小計のあとの総計のように、足し方が何通りかあるときは、どの足し方でも合わないときだけ指します。
-  en: When the total of a quote or an invoice is not the sum of the amounts listed above it, the reader has to add them up again to find out which is right. It happens when a line is added or removed and the total is not updated. In a list or a table, a line starting with a total word (Total, Subtotal) is compared with the sum of the amounts in the same unit and column above it. A total written in a sentence, as contracts do ("$6,000 for hosting and $3,000 for support, for a total of $9,000", "$8 per month, made up of …"), is compared with the amounts in the same unit listed in that sentence. When there is more than one way to add them up, such as a grand total after a subtotal and tax, it is pointed out only when none of them matches.
+  ja: 見積や請求の「合計」が、上に並べた金額の和と合わないと、読み手はどちらが正しいのかを計算し直すことになります。行を足したり消したりしたあとに、合計だけ直し忘れると起きます。箇条書きか表で、合計の語（合計・小計）で始まる行を、同じ単位で同じ列の金額の和と比べます。表の最初の列の見出しか、合計の行が数を書いた列の見出しが名指す語を付けた合計（見出しが「控除項目」の表の「控除合計」、「単位数」の列の「修得単位合計」）も合計の行と読みます。合計が足す期間を頭に付けた合計（年間合計、年計、通年合計）も合計の行と読みます。見出しが「項目」の表でも、最後の行の差引合計・控除合計は、上に合計のような行が無く金額の列が一つなら合計の行と読みます。契約書のように一つの文に書いた合計（「保守費60,000円、運用費30,000円とし、合計100,000円とする」「月額150,000円（内訳：…）」）も、その文に並べた同じ単位の金額の和と比べます。小計のあとの総計のように、足し方が何通りかあるときは、どの足し方でも合わないときだけ指します。
+  en: When the total of a quote or an invoice is not the sum of the amounts listed above it, the reader has to add them up again to find out which is right. It happens when a line is added or removed and the total is not updated. In a list or a table, a line starting with a total word (Total, Subtotal) is compared with the sum of the amounts in the same unit and column above it. A total with a word that the header of the table's first column, or of the column the total holds its number in, names ("Total deductions" under "Deduction", "Total credits earned" in the "Credits" column) is read as a total line too, and so is a total naming the span it covers ("Total for the year", "Year total", "Annual total"). Under a header that names nothing ("Item"), a "Total deductions" on the table's last row is read too, when no row above it is a total or a gross or net amount and the table has one column of amounts. A total written in a sentence, as contracts do ("$6,000 for hosting and $3,000 for support, for a total of $9,000", "$8 per month, made up of …"), is compared with the amounts in the same unit listed in that sentence. When there is more than one way to add them up, such as a grand total after a subtotal and tax, it is pointed out only when none of them matches.
 
 message:
   ja: 合計「{written}」が、内訳の金額の和（{sum}）と合いません
@@ -31,7 +31,7 @@ sources: [de-marneffe-2008]
 group: facts
 summary:
   ja: 見積もりや請求書、契約書で、合計が内訳に並べた金額の和と合わない所
-  en: A total in a quote, an invoice or a contract that is not the sum of the amounts it is made up of
+  en: A total in a quote, invoice or contract that is not the sum of its items
 example:
   ja:
     before: |
@@ -61,5 +61,5 @@ example:
       | Total | $8,000 |
 
 not_flagged:
-  ja: 単位や列の違う金額は足しません。足し方が何通りもあるとき（小計と税のあとの総計など）は、どれとも合わないときだけ指します。文の中では、合計の語（合計・総額）のすぐ後ろの金額か内訳の語（内訳は）のすぐ前の金額だけを合計と読み、内訳の金額が二つ以上あるときだけ比べます。並びの一部（単価や上限など、合計の語から離れた金額を除いた並び）の和か、一つを引いた額（値引き）と合えば指しません。
-  en: Amounts in another unit or column are not added. Where there is more than one way to add them up, it is reported only when none matches. In a sentence, only the amount right after a total phrase (a total of) or right before a breakdown phrase (made up of) is read as a total, and only when two or more items in its unit are listed. It is not reported when the items nearest the phrase add up to it, or when it matches with one item taken away (a discount).
+  ja: 単位や列の違う金額は足しません。合計の語に表の見出しが名指さない語を付けた行（見出しが「項目」の表の「消費税合計」）は、別の種類の合計かもしれないので比べません。差引合計・控除合計も、表の最後の行でないとき、上に合計の行や総支給額・支給合計の行があるとき、金額の列が二つ以上あるときは比べず、下から続けた行の和か、その上の行の和からそれを引いた額と合えば指しません。面積のように、上の行の和とは限らない量の合計（面積合計）も比べません。前の期間の合計（前年合計）は読まず、期間を付けた合計が内訳の和を一年に直した額（ちょうど4倍・12倍・52倍。月額の内訳に年間合計）なら比べません。重さ・容量・長さ（mg、g、mL、L、cm、km）は、列のどの行も同じ種類の量なら換算して足します（500mg と 0.5g は 1g）。何あたりかを書いた量（300mg/錠）、目安の量（約300mg）、範囲（300〜400mg）がある列は足しません。足し方が何通りもあるとき（小計と税のあとの総計など）は、どれとも合わないときだけ指します。文の中では、合計の語（合計・総額）のすぐ後ろの金額か内訳の語（内訳は）のすぐ前の金額だけを合計と読み、内訳の金額が二つ以上あるときだけ比べます。並びの一部（単価や上限など、合計の語から離れた金額を除いた並び）の和か、一つを引いた額（値引き）と合えば指しません。
+  en: Amounts in another unit or column are not added. A total with a word the table's header does not name ("Total tax" under "Item") is not compared, as it may be a total of another kind, nor is a total of a quantity that need not be the sum of the rows (Total area). Under such a header, "Total deductions" is not compared when it is not the last row, when a total or a gross or net amount (Gross pay) is above it, or when the table has two columns of amounts; it is not reported when it matches the last few rows, or the rows above those less them. A total for another span ("Prior-year total") is not read, and a total naming its span that is the items scaled to a year (exactly 4, 12 or 52 times their sum, as monthly items under an annual total) is not compared. Mass, volume and length (mg, g, mL, L, cm, km) are converted and added when every row of the column is the same kind of measure (500 mg and 0.5 g make 1 g); a column with an amount per something (300 mg/tablet), a rough amount (about 300 mg) or a range (300-400 mg) is not added. Where there is more than one way to add them up, it is reported only when none matches. In a sentence, only the amount right after a total phrase (a total of) or right before a breakdown phrase (made up of) is read as a total, and only when two or more items in its unit are listed. It is not reported when the items nearest the phrase add up to it, or when it matches with one item taken away (a discount).

package/rules/ui-label-variant.yaml

@@ -34,7 +34,7 @@ off_for:
 group: consistency
 summary:
   ja: 太字や［］の画面の札で、大文字・小文字や空白、「を」「の」だけが違う二通りの書き方
-  en: A bold or bracketed screen label written two ways that differ only in case, spaces or a particle
+  en: A screen label written two ways that differ only in case, spacing or a particle
 example:
   ja:
     config: { genre: docs/manual }

package/rules/unclosed-code-fence.yaml

@@ -33,7 +33,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: structure
 summary:
   ja: 「```」で始めたまま閉じていないコードブロック（後ろがすべてコードになる）
-  en: A code block opened with "```" and never closed (everything after it shows as code)
+  en: A code block opened with "```" and never closed
 example:
   ja:
     before: |

package/rules/uncomparable-graded.yaml

@@ -31,8 +31,8 @@ off_for:
 
 group: wording
 summary:
-  ja: 「より最適な」「とても完璧」（very unique、more unanimous）のように、程度の無い語に付けた程度
-  en: A degree given to an adjective that has none, such as "very unique" or "more unanimous" (より最適な, とても完璧)
+  ja: 「より最適な」「とても完璧」のように、程度の無い語に付けた程度
+  en: A degree given to a word that has none, such as "very unique"
 example:
   ja:
     before: |

package/rules/undefined-term.yaml

@@ -36,8 +36,8 @@ off_for:
 
 group: consistency
 summary:
-  ja: 「本業務」のように定義した語と同じ形の「本成果物」や、英語の契約で大文字で始めた語（its Affiliates）を、定義しないまま使っている所
-  en: A term in the defined form (本成果物, its Affiliates) that the document never defines
+  ja: 「本業務」のように定義した語と同じ形なのに、定義しないまま使っている語（本成果物）
+  en: A term written like a defined one (its Affiliates) that is never defined
 example:
   ja:
     config: { genre: legal/contract }

package/rules/unfilled-placeholder.yaml

@@ -28,8 +28,8 @@ use_for: [blog, business, technical, legal, docs, academic, literature, speech]
 
 group: slips
 summary:
-  ja: "「【会社名】」「[Your Name]」「TODO: …」のように、雛形の空欄や後で埋めるつもりの値が埋まらないまま残っている所"
-  en: 'A template blank or a to-do value left unfilled, such as "[Your Name]", "[Insert Date]" or "TODO: …"'
+  ja: 「【会社名】」「TODO」のように、雛形の空欄が埋まらないまま残っている所
+  en: 'A template blank left unfilled, such as "[Your Name]" or "TODO: …"'
 example:
   ja:
     before: |

package/rules/unit-mismatch.yaml

@@ -11,13 +11,21 @@ name:
   en: One item given in two units that do not convert
 
 why:
-  ja: 「距離：5 km」と「距離：3000 m」のように、同じ項目の量を違う単位で書くと、読み手は換算してどちらが正しいかを確かめることになります。片方の単位を書き換えたときに、数を直し忘れると起きます。「項目：量」「項目は量です」と書いた所と表の升を読み、同じ節の同じ項目で単位の違う量（長さ、重さ、時間、体積、データの量）を換算して比べます。丸めた書き方（1 mile と 1.6 km）は、2% までの差なら合っているとみなします。
-  en: 'When one item is given as "Distance: 5 km" and later "Distance: 3000 m", the reader has to convert to find out which is right. It happens when the unit of one is rewritten and its number is not. Values written as "Item: value" or "The item is value", and table cells, are read; within one section, the same item in two different units (of length, mass, time, volume or data) is converted and compared. A rounded figure (1 mile and 1.6 km) agrees when the difference is within 2%.'
+  ja: 「距離：5 km」と「距離：3000 m」のように、同じ項目の量を違う単位で書くと、読み手は換算してどちらが正しいかを確かめることになります。片方の単位を書き換えたときに、数を直し忘れると起きます。三つの所を読みます。①「項目：量」「項目は量です」と書いた所と表の升で、同じ節の同じ項目の量。②一つの量を括弧で二つの単位に並べた所（180℃（350°F）、300kPa（約44psi））。③材料の表に書いた品物を、手順で違う単位で書いた所（表の「しょうゆ｜大さじ1」と手順の「しょうゆ30ml」）。表の量は行の最初の量（人数ごとの列があれば最初の列）で、節が違っても比べます。手順の量が表の量より多いときだけ言います（少ない量は、その一部を使う所かもしれません）。量の種類は長さ、重さ、時間、体積（大さじ 15 mL、小さじ 5 mL、カップ 200 mL）、データの量、温度、圧力、面積です。面積の坪は 400/121 ㎡（約 3.306 ㎡）で数えます。畳（帖）は、大きさが地方や建物で違い、広告の決まりも 1.62 ㎡ 以上という下限しか決めていないので、面積の単位として読みません。丸めた書き方（1 mile と 1.6 km）は、2% までの差なら合っているとみなします。小数で書いた量は書いた最後の桁で丸めたものとみなし、その桁の半分までの差も合うとみなします（1.2 kg は 1.15〜1.25 kg なので、1,250 g と合います）。整数は末尾の 0 が丸めかどうか分からないので、2% だけで比べます。括弧で並べた二つの量は、どちらもそれぞれの桁で同じ値を丸めたものでありうるなら合うとみなします（44 psi は 1 の位、100 miles は 10 の位）。温度は割合では比べられないので、オーブンの目盛り（25 °F 刻み）より小さい 15 °F（約 8 ℃）までの差を合うとみなします（換算表は 170 ℃ を 325 °F と書きます）。32 °F より小さい °F の量は温度の差（0.5 ℃ の上昇は 0.9 °F）としても比べます。「度」は、同じ行に「オーブン」「温度」のような語があるときだけ温度として読みます。
+  en: 'When one item is given as "Distance: 5 km" and later "Distance: 3000 m", the reader has to convert to find out which is right. It happens when the unit of one is rewritten and its number is not. Three places are read: values written as "Item: value" or "The item is value", and table cells, for the same item within one section; one value given in two units with the second in brackets ("180°C (350°F)", "300 kPa (about 44 psi)"); and an item of an ingredients table given in another unit in a step ("Soy sauce | 1 tablespoon" in the table, "30 ml of soy sauce" in a step), wherever in the document, against the first amount in the row (the first column when there is one per number of servings); only an amount larger than the one in the table is reported, since a smaller one may be a part of it. The kinds of quantity are length, mass, time, volume, data, temperature, pressure and area. A tsubo is 400/121 m² (about 3.306 m²). A tatami mat (畳) is not read as a unit of area: its size differs by region and building, and the advertising rules only set a minimum of 1.62 m². A tablespoon is 14.8 mL (US) or 15 mL (metric), a teaspoon 4.9 or 5 mL, a cup 240 mL (the US legal cup) or 250 mL, and either agrees. A rounded figure (1 mile and 1.6 km) agrees when the difference is within 2%, and a decimal also agrees within half of its last written digit (1.2 kg is 1.15 to 1.25 kg, so it agrees with 1,250 g; a whole number keeps the 2%, since its trailing zeros may or may not be rounding); two values side by side also agree when both could be roundings of one value at their last digits (44 psi to the unit, 100 miles to the ten). A temperature cannot be compared by a share, so it agrees within 15 °F (about 8 °C), less than one 25 °F step of an oven dial (conversion tables give 170 °C as 325 °F). A Fahrenheit figure below 32 °F is also compared as a difference (a rise of 0.5 °C is 0.9 °F). "degrees" alone is read as a temperature only when a word such as "oven" or "temperature" is on the same line.'
 
 message:
   ja: "「{label}」が {value} と書かれていますが、同じ節の前の所では {other} で、換算すると合いません"
   en: '"{label}" is {value} here, but {other} earlier in the same section, and they do not convert'
 
+messages:
+  bracket:
+    ja: "{value} を {other} と並べていますが、換算すると合いません"
+    en: "{value} is given next to {other}, and they do not convert"
+  item:
+    ja: "「{label}」が {value} と書かれていますが、表では {other} で、換算すると合いません"
+    en: '"{label}" is {value} here, but {other} in the table, and they do not convert'
+
 how_to_fix:
   ja: どちらの量が正しいかを確かめて、もう一方を換算して直してください。一つの文書では、同じ項目の単位を揃えると読み手が比べやすくなります。
   en: Check which value is right and convert the other to match. Using one unit for an item throughout a document makes it easier to compare.
@@ -29,7 +37,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: facts
 summary:
   ja: 同じ項目の量を、違う単位で書いて換算すると合わない所（距離：5 km と 3000 m）
-  en: 'The same item given in two units that do not convert ("Distance: 5 km" and "3000 m")'
+  en: The same item in two units that do not convert ("5 km" and "3000 m")
 example:
   ja:
     before: |
@@ -55,8 +63,8 @@ example:
       - Distance: 5000 m
 
 not_flagged:
-  ja: 単位が同じ量（食い違いは fact-conflict が見ます）、種類の違う量（長さと重さ）、違う見出しや違う親の項目の下の量、2% までの差は見ません。GB や MB は 1000 倍でも 1024 倍でも合えば合うとみなします。
-  en: Values in the same unit (fact-conflict looks at those), of different kinds (a length and a mass), under different headings or parent items, and differences within 2% are left alone. GB and MB agree when they match at either 1000 or 1024.
+  ja: 単位が同じ量（食い違いは fact-conflict が見ます）、種類の違う量（長さと重さ）、違う見出しや違う親の項目の下の量、2% までの差は見ません。GB や MB は 1000 倍でも 1024 倍でも合えば合うとみなします。単位が一つだけの温度（180℃に予熱）、表に無い名前の品物、量の前に分数が続く量（大さじ1と1/2）、表より少ない手順の量、表の中の量どうしは、括弧や品物の比べ方では見ません。スラッシュで並べた量（1 GB / 500 MB）は、別の選択肢のことがあるので比べません。
+  en: Values in the same unit (fact-conflict looks at those), of different kinds (a length and a mass), under different headings or parent items, and differences within 2% are left alone. GB and MB agree when they match at either 1000 or 1024. A temperature given in one unit only, an ingredient under another name, an amount with a fraction (1 1/2 cups), a step amount smaller than the table's, and amounts inside the table itself are left out of the bracket and ingredient comparisons. Values separated by a slash (1 GB / 500 MB) are not compared, since they may be alternatives.
 rewrite:
   depth: light
   ja:

package/rules/unit-spacing-consistency.yaml

@@ -28,7 +28,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: consistency
 summary:
   ja: 「5 GB」と「5GB」のように、一つの文書で数と単位記号の間を空けたり詰めたりしている所
-  en: A number and a unit symbol spaced in some places and not in others, such as "5 GB" and "5GB"
+  en: A number and its unit spaced in some places and not others (5 GB, 5GB)
 example:
   ja:
     before: |