René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Provide constants in non-Latin scripts (Cyrillic, Greek, Arabic, Hebrew)","articleBody":"The parsing machinery is fully Unicode-clean — `\\w`, `.lower()`, and the piece logic all handle non-Latin scripts — but the constant sets (titles, prefixes, conjunctions, suffixes) are almost entirely Latin-script. Verified on v1.3.0 that runtime additions work end-to-end with no code changes, e.g.:\n\n```python\n\u003e\u003e\u003e C = Constants()\n\u003e\u003e\u003e C.titles.add('г-н')\n\u003e\u003e\u003e C.prefixes.add('بن')\n\u003e\u003e\u003e HumanName(\"г-н Иван Петров\", constants=C).title\n'г-н'\n\u003e\u003e\u003e HumanName(\"محمد بن سلمان\", constants=C).last\n'بن سلمان'\n```\n\nUnlike Latin transliterations (which collide across cultures and need opt-in flags), native-script constants cannot collide with Latin-script names, so they are viable as defaults. Only within-script ambiguity needs vetting.\n\n**Candidates:**\n- **Cyrillic titles:** `г-н`, `г-жа`, `д-р`, `проф`, `акад`; Ukrainian `пан`, `пані`. (Abbreviated forms like `проф.` currently work only by accident via the leading-position `period_abbreviation` fallback; hyphenated `г-н` doesn't.)\n- **Cyrillic conjunctions:** `и`; Ukrainian `і`/`та` (interacts with the `initial`-regex question, see #267)\n- **Cyrillic suffixes:** `мл`/`ст` (junior/senior) — needs within-script collision vetting\n- **Greek:** titles `κ`, `κα`, `κος`, `δρ`, `καθ`; conjunction `και`\n- **Arabic script prefixes:** `بن` (bin), `بنت` (bint), `ابن` (ibn), `أبو`/`ابو` (abu), `آل` (Āl); title `الشيخ`. Excluded: standalone `ال` (normally attached, too ambiguous), conjunction `و` (attaches without a space)\n- **Hebrew prefixes:** `בן` (ben), `בת` (bat); title `מר`. Titles containing geresh/gershayim (`ד\"ר`, `גב'`) need testing against the nickname-extraction regexes first.\n\nOut of scope: CJK (family-first order and unspaced segmentation — see #83), Cyrillic patronymic suffixes (already covered by the 1.3.0 regexes).\n\nCoverage should be parsing-behavior tests per script, not assertions on set contents. Related: #265, #266.\n","author":{"url":"https://github.com/derek73","@type":"Person","name":"derek73"},"datePublished":"2026-07-07T21:02:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/269/python-nameparser/issues/269"}