The parser's Western-order assumption is confined to the positional assignment loops in parse_full_name — the vocabulary layer (titles, prefixes, suffixes, conjunctions, nicknames, capitalization) is entirely order-agnostic, and the lastname-comma path already parses family-first when a comma provides the signal. That makes name order configurable without restructuring the parser.
Proposal: an opt-in Constants attribute specifying the positional order of name parts, e.g.:
C.name_order = ('last', 'first', 'middle') # Chinese, Hungarian, Japanese rōmaji (#83)
C.name_order = ('last', 'middle', 'first') # Vietnamese (#146)A boolean family_name_first flag was considered and rejected: Vietnamese order is [family][middle][given] — the given name is the last token — so these issues need at least two non-Western orders. An order spec covers both and subsumes the Western default as ('first', 'middle', 'last').
Notes for design:
Would resolve the spaced-input cases of #83 and #146.
The parser's Western-order assumption is confined to the positional assignment loops in
parse_full_name— the vocabulary layer (titles, prefixes, suffixes, conjunctions, nicknames, capitalization) is entirely order-agnostic, and the lastname-comma path already parses family-first when a comma provides the signal. That makes name order configurable without restructuring the parser.Proposal: an opt-in
Constantsattribute specifying the positional order of name parts, e.g.:A boolean
family_name_firstflag was considered and rejected: Vietnamese order is [family][middle][given] — the given name is the last token — so these issues need at least two non-Western orders. An order spec covers both and subsumes the Western default as('first', 'middle', 'last').Notes for design:
patronymic_name_order(v1.3.0, last name + first name + optional patronymic, Russian name order #85) is the architectural precedent for an opt-in flag reassigning first/middle/last.Would resolve the spaced-input cases of #83 and #146.