Repository navigation
Dr. Smith née Jones reports no family name — a maiden name suppresses the title-plus-one-word rule #410
Description
Activity
Measured before fixing (1.4.0 and 2.1.0 from PyPI wheels, master at b244c5a): this is not maiden-specific.
othersat_post_rules.py:177tests(SUFFIX, NICKNAME, MAIDEN), and all three suppress H1 identically:input 1.4.0 2.1.0 / master Dr. Smithlast='Smith'family='Smith'Dr. Smith née Jonesfirst='Smith'middle='née'last='Jones'given='Smith'family=''Dr. Smith PhDfirst='Smith'last='PhD'given='Smith'family=''Dr. "Smitty" Smithfirst='Smith'last=''given='Smith'family=''So the answer to "should H1's
otherstest ignoreRole.MAIDEN" is that it should not test roles at all: H1's rationale is that a title addresses by surname, which says nothing about what stands beside the name. The suffix and nickname flavors are fixed with it and need no separate issues.Two things worth recording for whoever reads this later. The v1 suite already carried the nickname reading as a strict xfail (
tests/test_nicknames.py::test_nickname_and_last_name_with_title), so the correct answer was written down and marked unreachable. And N3 moves without changing:'Smitty' Dr. Jonesdeclines N3's one-piece count as it always did, and H1 now names the family behind it —given 'Jones'through 2.1,family 'Jones'now. That interaction was carried by no test and no rule example, so nothing would have caught it; it is now an N3 example line.Fixed in #444.
- added 6 commits that reference this issue
on Aug 29, 2026
Adding a maiden name to a title-plus-surname name moves the surname into
givenand emptiesfamily:Same for the particle spelling, which is how it was found:
The name plainly has a family name in both readings, and the maiden name is reported correctly. Only the family field is lost.
Why
rules.md#H1reads a title followed by exactly one name word and nothing else as title-plus-family. It is gated onnot othersin _post_rules.py, and a token inRole.MAIDENcounts asothers— so the presence of a maiden name makes H1 decline, and the surname falls through to the given slot.The maiden name is not part of the name-proper the way a middle name is; it is a second name announced by a marker. H1's "nothing else" is meant to exclude further name words, and a maiden name arguably is not one.
Scope
Pre-existing, and unchanged by #399 —
Dr. Smith née Jonesbehaves identically at 2.1.0. What #399 changed is reach: stopping the particle chain at the marker routes the canonical title-and-particle shape (Freiherr von Richthofen, named as such in_group.py) into the same gate for the first time. A review sweep put it at roughly 120 of 4800 constructed inputs.Both the delimited and bare marker forms are affected, and all three name orders.
Worth deciding
Whether H1's
otherstest should ignoreRole.MAIDENtokens, or whether a title-plus-one-word name that also carries a maiden name is genuinely outside H1's scope and should be reported some other way.rules.md#M2gainedinteracts: P2, P3, P5, R2, M1in #409 and does not name H1; if the answer is that they interact, that pointer should exist.