ISSUE-502: Unicode equivalent type all not clear

Unicode equivalent type all not clear

State:

CLOSED

Product:

find-text

Raised by:

Addison Phillips

Opened on:

2015-10-16

Description:

https://github.com/w3c/findtext/issues/11

--

http://www.w3.org/TR/2015/WD-findtext-20151015/#idl-def-UnicodeEquivalenceType.canonical

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. Weekly github digest (Tracker items) (from sysbot+gh@w3.org on 2021-03-03)
2. Daily github digest (WG INTERNAL review issues) (from sysbot+gh@w3.org on 2021-02-26)
3. Weekly github digest (Tracker items) (from sysbot+gh@w3.org on 2020-03-25)
4. Daily github digest (WG INTERNAL review issues) (from sysbot+gh@w3.org on 2020-03-20)
5. Weekly github digest (Tracker items) (from sysbot+gh@w3.org on 2020-03-11)
6. Daily github digest (WG INTERNAL review issues) (from sysbot+gh@w3.org on 2020-03-10)
7. I18N-ISSUE-502: Unicode equivalent type all not clear ⓟ [find-text] (from sysbot+tracker@w3.org on 2015-10-16)

Related notes:

Display change log