Repository navigation
Support smart quotes (“Jack”), guillemets («Petit»), and CJK brackets as nickname delimiters #273
Description
Activity
- changed the title
[-]Nicknames in smart quotes (“Jack”), guillemets («Petit»), or CJK brackets are not extracted[/-][+]Support smart quotes (“Jack”), guillemets («Petit»), and CJK brackets as nickname delimiters[/+]on Jul 7, 2026 - added a commit that references this issue
on Jul 18, 2026 Implemented on the 2.0 branch (PR #288, commit 7ee6e3a): all eight proposed pairs ship in
DEFAULT_NICKNAME_DELIMITERSand as named sentinels in the v1CONSTANTSAPI (smart_double_quotes,guillemets, ...), with curly single quotes excluded as proposed (U+2019 stays the apostrophe in "O'Connor"). The issue's five repro examples are pinned as test rows,« Petit »inner spacing is tolerated, and a delimiter character consumed by another pair's extraction (the shared-character overlap: German's closing“is English's opening quote) no longer emits a spuriousunbalanced-delimiterambiguity. Closes with the 2.0.0 merge.- added 4 commits that reference this issue
on Jul 18, 2026 - added 7 commits that reference this issue
on Aug 8, 2026 - added a commit that references this issue
on Oct 8, 2026
The three built-in nickname delimiters (
quoted_word,double_quotes,parenthesis) are ASCII-only, so nicknames wrapped in any typographic or non-Latin quote convention leak into the name pieces as garbage middle names (v1.3.0):The smart-quote case is effectively English input:
“…”(U+201C/201D) is what word processors and phone keyboards autocorrect plain quotes to, so real-world copy-paste text hits this constantly — same input-normalization class as #266.Proposed additions to the built-in delimiter inventory, one ordered open/close pair each (the conventions can't be merged into a single character class — German's closing
“is English's opening quote, so each pair needs its own regex, exactly like the three existing ones):“…”«…»« Petit »)„…“»…«”…”「…」,『…』（…）All of these are safe as defaults: unlike the apostrophe, none can legitimately appear inside a name. Explicitly excluded: curly single quotes
‘…’— U+2019 is also the preferred typographic apostrophe (O’Connor), so it would need the same whitespace-border rules as the ASCIIquoted_wordregex and deserves separate, careful treatment if ever.The
nickname_delimitersdict already accepts additional compiled patterns at runtime, so this is purely an expansion of the built-in inventory. Related: #266, #269.