You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Should john smith nee x x read like JOHN SMITH NEE X X? A shape-only numeral in a maiden clause #731
rules/T4 says a name written wholly in one case reads as its capitals, but a maiden clause holding two shape-only numerals doesn't:
>>>parse("john smith nee x x") # suffix 'x', maiden 'x', suffix-or-name>>>parse("JOHN SMITH NEE X X") # maiden 'X X', no report>>>parse("john smith nee v v") # suffix 'v', maiden 'v' -- as JOHN SMITH NEE V V
Both xs carry the initial tag in both spellings, so something in the maiden take reads more than the tag. The likely place is #610's candidate loop for a shape-only numeral (VI to X). This mismatch was already there before PR #729; its code review found it. No _ONE_CASE_SHAPES row puts a numeral after a letter in a clause.
To settle before implementing: which reading is right for the clause? Should the fix be a new grid shape ({a} {b} nee {n} {n}), and should letters x and vi be added?
Activity
Revert #731's maiden-clause numeral fix; accept the shape in T4 (#733)
Scope T4's declined-option claim; fold the tombstone trap into rule 3…
Trim the design docs: archive the differential ledger, tidy mechanism…