polytypo 1.6.1 → 1.6.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0bb01ab8478817898277fc5b6d1f1654cc847a3f82ab1975e043e1a58409d2db
-  data.tar.gz: 559fdc9ca8756129e28d9762f2f3cc5666384f4c470960d84f181448dba56a0b
+  metadata.gz: f6776ba2390f63971edcd4f09cd84dbb3f1fc3e9678feee541a7f1667694fdbf
+  data.tar.gz: 7a6657ca0e43963c3c9f8509a0727a6dc9bbaed2f648b3fd4f295aca1c7bdf03
 SHA512:
-  metadata.gz: 69173cb92815bc03d120ea753d9cf1304c31786bdc576f7ac7f358679cbcac558b789d1d742622728d9cc23486de58b7185832e5e768c939032a24a7b8a94cca
-  data.tar.gz: ed92be4e7fe8d8d026fee4aaff03936553c4d086fe44a1eccf6bd8f890ba17c58710856e0b08a486722022d034ac432c623ccac28610c7c76f2994240e1e83c7
+  metadata.gz: 33d644b27e332aef05d2857a9e95598ab05ef5ff56b29a81ba077b5c1d32f0538a8e0d5718a9e5109710227e3559ad67081d3a418910e8cab9a4bc8c242b14c0
+  data.tar.gz: e8b828b749cfe12d719590ace28fb24a5f296bc52b14c959c74f24176921eca9c4ba583509198f56a4d9e4f684e3878dcb577add5c554a5c8b593a5680530fe9

data/lib/polytypo/data/README.md

@@ -20,12 +20,15 @@ canonical's `spec/` changes, re-copy the affected files here.
 
 CI checks that it was done. `script/check-vendored-spec.sh` compares every file in this
 directory against canonical `polytypo/polytypo` at tag `spec-v` + this directory's own
-`VERSION`, and fails on any difference. Three details: the files this repository authors
-itself are listed in `.not-canonical` and skipped; `locales/*.json` are compared with the
-`sources` array dropped from both sides, which is the one field a vendored copy may
-legitimately differ in; and a file here with no canonical counterpart is a failure, so a
-canonical rename cannot pass unnoticed. Completeness is deliberately not checked — each
-runtime vendors its own subset, and the subsets differ.
+`VERSION`, and fails on any difference. Three details. The files this repository authors
+itself are listed in `.not-canonical` and skipped — and a listed path that canonical *does*
+have is an error, so that list cannot be used to keep a forked copy of a canonical file. A
+`locales/*.json` file is compared in full when it carries its `sources` array, and against
+canonical minus that array when it does not, which is the shipped form three of the five
+runtimes vendor; the script reads which case it is off the file rather than being told. And a
+file here with no canonical counterpart is a failure, so a canonical rename cannot pass
+unnoticed. Completeness is deliberately not checked — each runtime vendors its own subset,
+and the subsets differ.
 
 Before that check existed, this half of the tree went stale unnoticed in four of the five
 ports at once: the data half is proved by the test suite, and nothing at all read the prose.

data/lib/polytypo/data/VERSION

@@ -1 +1 @@
-1.6.1
+1.6.3

data/lib/polytypo/data/fixtures/cs.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "cs",
   "cases": [
     {

data/lib/polytypo/data/fixtures/de-CH.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "de-CH",
   "cases": [
     {

data/lib/polytypo/data/fixtures/de-DE.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "de-DE",
   "cases": [
     {

data/lib/polytypo/data/fixtures/el.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "el",
   "cases": [
     {

data/lib/polytypo/data/fixtures/en-GB.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "en-GB",
   "cases": [
     {

data/lib/polytypo/data/fixtures/en-US.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "en-US",
   "cases": [
     {

data/lib/polytypo/data/fixtures/es.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "es",
   "cases": [
     {

data/lib/polytypo/data/fixtures/fi.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "fi",
   "cases": [
     {

data/lib/polytypo/data/fixtures/fr-CA.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "fr-CA",
   "cases": [
     {

data/lib/polytypo/data/fixtures/fr.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "fr",
   "cases": [
     {

data/lib/polytypo/data/fixtures/it.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "it",
   "cases": [
     {

data/lib/polytypo/data/fixtures/locale-resolution.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "cases": [
     {
       "id": "exact-en-us",

data/lib/polytypo/data/fixtures/nl.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "nl",
   "cases": [
     {

data/lib/polytypo/data/fixtures/pl.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "pl",
   "cases": [
     {

data/lib/polytypo/data/fixtures/pt-BR.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "pt-BR",
   "cases": [
     {

data/lib/polytypo/data/fixtures/pt-PT.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "pt-PT",
   "cases": [
     {

data/lib/polytypo/data/fixtures/ru.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "ru",
   "cases": [
     {

data/lib/polytypo/data/fixtures/sv.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "sv",
   "cases": [
     {

data/lib/polytypo/data/fixtures/tr.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "tr",
   "cases": [
     {

data/lib/polytypo/data/fixtures/uk.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "locale": "uk",
   "cases": [
     {

data/lib/polytypo/data/locales/registry.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "$comment": "Locale resolution input. Algorithm is specified in spec/rules/locale-resolution.md and is identical in every runtime — never delegate it to a platform locale-negotiation library. \"spec\" here must track spec/VERSION exactly — it is not itself the global version source; scripts/validate-spec.mjs enforces the match.",
   "locales": [
     "en-US",

data/lib/polytypo/data/rules/order.json

@@ -1,5 +1,5 @@
 {
-  "spec": "1.6.1",
+  "spec": "1.6.3",
   "$comment": "Single source of truth for pipeline order. Rules run in ascending `order`. Disabling a rule removes it from the sequence and never reorders the rest. Rule ids are public API (see docs/ARCHITECTURE.md section 5). \"spec\" here must track spec/VERSION exactly — it is not itself the global version source; scripts/validate-spec.mjs enforces the match.",
   "rules": [
     {

data/lib/polytypo/data/rules/quotes.md

@@ -605,21 +605,46 @@ spec 1.4.0. Measured on this change, `markdown`/`commonmark`, `en-GB`:
 words early and the author's own closing mark is left to `apostrophe` as a stray U+2019. §1 of
 that issue is closed by the veto above; §3 is not, and is not going to be.
 
-**Why §3 is decided and not merely unfixed.** Two measurements, both on the published 1.6.0
-package. First, **the glyph at the possessive's own position is correct either way** — U+2019,
-whether the mark is taken as a closing quotation mark or left unmatched for `apostrophe`. What
-the defect costs is never the character a reader sees there; it is the *pairing it consumes*,
-which is why the visible symptom always appears somewhere else (a stray U+0027 at the real
-closing mark, or a middle paragraph re-nested from `‘ ’` to `“ ”`). Second, **separating the two
-readings was implemented and measured, and it is worse.** The narrowest local veto that can do
-it — decline a `NARROW` mark whose literal neighbour is `MARKER` and whose attaching `LETTER`
-run is empty — breaks **7 of 2801 conformance cases**, five of them `tr` cases that are correct
-today: `tr-html-span-boundary-suffix-declined`,
+**Why §3 is decided and not merely unfixed.** Two measurements — the first on a published
+package, the second on a build patched with the veto it measures, since no release contains it.
+
+First, **the U+2019 at the possessive's own position is produced by the pairing, and nothing else
+can produce it.** Not because `apostrophe` cannot see past a span boundary — it can, and
+[apostrophe.md](apostrophe.md) §3.3 case 4 says so: the marker is in that rule's `OPENISH`
+(`modes.md` §3.3), which is exactly why `` `x`'s `` reaches case 4 and comes out `` `x`’s ``. It is
+this shape it cannot reach. Case 4 is the only case in the ladder that accepts the marker on the
+left, and it requires `ALNUM` on the **right**; a plural possessive has a space there. Cases 2 and
+2a read `ALNUM` and `CLOSEDELIM` on the left, and cases 3 and 3a read `LETTER`; the marker is in
+none of those three classes (`modes.md` §3.3). So the ladder falls through to case 5 and emits
+nothing. Measured on published 1.6.1,
+`markdown`/`commonmark`, `en-GB`: `` The `xs`' printer works. `` comes back **unchanged** — an
+unmatched span-boundary plural possessive keeps its U+0027. So the cost of this behaviour is a
+consumed *pairing*, and the visible symptom of that appears elsewhere (a stray U+0027 at the real
+closing mark, or a middle paragraph re-nested from `‘ ’` to `“ ”`) — but declining the mark does
+not buy the right glyph in exchange. It moves the straight mark rather than removing it. An
+earlier revision of this paragraph claimed the glyph was "correct either way"; it is not, and the
+measurement above is what replaced the claim.
+
+Second, **separating the two readings was implemented and measured, and it is a trade rather than
+a fix.** The narrowest local veto that can do it — decline a `NARROW` mark whose literal
+neighbour is `MARKER` and whose attaching `LETTER` run is empty — breaks **6 of the 1366 fixture
+cases** (7 tests in polytypo-js's runner, which counts each case's idempotency re-run separately;
+the denominator to reproduce is the suite's case count in [CONFORMANCE.md](../CONFORMANCE.md),
+never a runtime's test total). Five are `tr` cases that are correct today:
+`tr-html-span-boundary-suffix-declined`,
 `tr-markdown-commonmark-span-boundary-suffix-declined`,
 `tr-html-span-boundary-quotation-outside-the-span`,
 `tr-html-span-boundary-non-ascii-initial-fragment` and `tr-html-span-boundary-ordinal-fragment`.
-That is this section's own claim — no test over these neighbours can separate a plural
-possessive from a closing mark after a span — turned from an argument into a number.
+
+The sixth is this section's own fixture, `en-gb-markdown-commonmark-span-boundary-plural-possessive-not-closed`,
+and it is the one worth reading: the veto does exactly what it is aimed at and still comes out
+wrong. `He says 'avoid `` `xs`' `` printer.' Done.` typesets today as
+`He says ‘avoid `` `xs`’ `` printer.' Done.` — pair closed two words early, author's own mark left
+straight. Under the veto it becomes `He says ‘avoid `` `xs`' `` printer.’ Done.` — the pair now
+closes at the author's mark, which is right, and the typewriter apostrophe has moved to the
+possessive, which is not, for the reason the first measurement gives. That is this section's own
+claim — no test over these neighbours can separate a plural possessive from a closing mark after a
+span — turned from an argument into a number, and into a second output nobody would fixture.
 
 **Operator decision (2026-09-24): where no exact answer exists, choose one behaviour and pin it
 rather than leave the rule undefined.** Five runtimes agreeing byte-for-byte is the product; an
@@ -1574,3 +1599,27 @@ released fixture `en-us-markdown-commonmark-boundary-nested-quotes` and the `NAR
 `modes.md` §3.3's normative rows — not their `WIDE` forms, which both vetoes leave alone. §3.2 records that measurement, the accepted false positive (a quotation whose
 whole content is one listed fragment), and the one shape no veto over these neighbours can
 reach — the plural possessive, which is byte-identical to a closing mark after a span.
+
+1.6.2 corrects §3.2's own measurements of the decision above; no behaviour, fixture or locale
+field changes. Two errors, both introduced with the decision record on 2026-09-24 and both
+overstating how cheap the decided behaviour is. The first claimed the glyph at the possessive's
+position was "correct either way" — it is not: `apostrophe` does not reach *this* mark, the plural
+shape, for the reason the 1.6.3 entry below states, so declining the pairing leaves U+0027 there.
+Measured on the published 1.6.1 package. The second counted **7 of 2801 conformance cases** where 2801 is the test
+count of polytypo-js's conformance runner, a figure no other runtime can reproduce; the cost is
+**6 of the 1366 fixture cases**, and the sixth — this section's own `en-GB` fixture — is now described
+rather than left in the count, because the veto moves the pair to the author's mark correctly and
+moves the typewriter apostrophe to the possessive at the same time. A conformance count in this
+document is a count of fixture cases, never of one runner's tests.
+
+1.6.3 corrects §3.2's account of *why* the first of those measurements comes out the way it does;
+again no behaviour, fixture or locale field changes. The 1.6.2 text said `apostrophe` cannot reach
+a mark whose left neighbour is the inline marker and attributed that to the marker's exclusion
+from [apostrophe.md](apostrophe.md) §3.1's `CLOSEDELIM`. Both halves were wrong, and the second
+contradicted `apostrophe.md` §3.3 case 2a's own note in the same vendored tree: the marker is in
+that rule's `OPENISH`, so `` `x`'s `` does reach case 4 and is curled. What the ladder cannot
+reach is the *plural* shape, because case 4 — the only case accepting the marker on the left —
+requires `ALNUM` on the right, and cases 2, 2a, 3 and 3a all read a class the marker is not in.
+`CLOSEDELIM` is irrelevant to it either way, since case 2a reads `ALNUM` on the right as well. The
+same entry also called 2801 a vitest total; it is one runner's conformance test count, and the
+runtime's own total is 4440.

data/lib/polytypo/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Polytypo
-  VERSION = "1.6.1"
+  VERSION = "1.6.3"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: polytypo
 version: !ruby/object:Gem::Version
-  version: 1.6.1
+  version: 1.6.3
 platform: ruby
 authors:
 - Iurii Rogulia