ISSUE-502: Unicode equivalent type all not clear

Unicode equivalent type all not clear

Raised by:
Addison Phillips
Opened on:


The specification defines a Unicode equivalence type 'all' whose usage is unclear. Here's the description:

The search MUST use either canonical (NFC/NFD) or compatibility (NFKC/NFKD) Unicode equivalence of characters, whichever produces the more liberal match.

The intention appears to be that all four must be applied to determine which is the "most liberal match". This, combined with other options (case folding, distance) is likely to be extremely slow and possible not useful.

Note that one of the compatibility normalization forms is likely to be the most promiscuous match in all cases.
Related Actions Items:
No related actions
Related emails:
  1. I18N-ISSUE-502: Unicode equivalent type all not clear ⓟ [find-text] (from on 2015-10-16)

Related notes:

Richard Ishida, 17 Mar 2016, 12:26:52

Display change log ATOM feed

Addison Phillips <>, Chair, Richard Ishida <>, Fuqiao Xue <>, Atsushi Shimono <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $