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
#544 gave two rules the same question to answer, can this suffix word stand in a credential run?, and they answer it differently for the two words that are both particles and unambiguous suffix vocabulary, vd and mc.
C1's run test (after a comma, _segment.py) counts them as suffix words.
The anchor (_pieces._anchors) excludes them, because a particle chains onto the name after it (rules.md#P2). The anchor exclusion was added on PR fix(#544): a credential run keeps its ambiguous members #552 after Smith vd Ma, John lost the contiguity of its family name.
So the same words read differently depending on the path:
With a comma, vd Ma is a credential run; without one, the same two words are a family name. The last row shows why the comma reading isn't simply wrong: vd alone after a comma has always read as a suffix.
The question: after a comma, should a particle that is also a suffix word (a) count in the run, as today, so John Smith, vd Ma is a credential; or (b) end the run as it ends the anchor, so the part reads as the listing form?
(b) makes one predicate answer both questions: whether a word "has a live name reading" would decide both C1's run membership and the anchor. The cost is that John Smith, vd Ma returns to master's family John Smith vd Ma, a one-word listing-form part with no given name.
Aside: Doe, Jane PhD vd Ma puts vd Ma in middle without any report, on both master and #552. Whichever way this is decided, that silence deserves a look.
#544 gave two rules the same question to answer, can this suffix word stand in a credential run?, and they answer it differently for the two words that are both particles and unambiguous suffix vocabulary,
vdandmc._segment.py) counts them as suffix words._pieces._anchors) excludes them, because a particle chains onto the name after it (rules.md#P2). The anchor exclusion was added on PR fix(#544): a credential run keeps its ambiguous members #552 afterSmith vd Ma, Johnlost the contiguity of its family name.So the same words read differently depending on the path:
John Smith, vd MaJohn Smith vd MaJohn Smith vd Mavd Ma, reportedJohn Smith, PhD vd MaPhD, middleMa, suffixvdPhD, middlevd MaPhD vd Ma, reportedJan Smith PhD vd MaPhD vd Mavd Mavd MaDoe, Jane PhD vd MaMa, suffixPhD vdvd Ma, silentvd Ma, silentJohn Smith, vdvdvdvd(
Mcreads the same way asvd.)With a comma,
vd Mais a credential run; without one, the same two words are a family name. The last row shows why the comma reading isn't simply wrong:vdalone after a comma has always read as a suffix.The question: after a comma, should a particle that is also a suffix word (a) count in the run, as today, so
John Smith, vd Mais a credential; or (b) end the run as it ends the anchor, so the part reads as the listing form?(b) makes one predicate answer both questions: whether a word "has a live name reading" would decide both C1's run membership and the anchor. The cost is that
John Smith, vd Mareturns to master's familyJohn Smith vd Ma, a one-word listing-form part with no given name.Aside:
Doe, Jane PhD vd Maputsvd Mainmiddlewithout any report, on both master and #552. Whichever way this is decided, that silence deserves a look.