ISSUE-501: Unicode equivalence type non-specificity

Unicode equivalence type non-specificity

State:

CLOSED

Product:

find-text

Raised by:

Addison Phillips

Opened on:

2015-10-16

Description:

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

--


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

The unicodeEquivalentType parameter provides four possible parameters. Three of these (canonical, compatibility, and all) allow either C or D forms rather than specifying which shall be used. Because of the nature of what FindText is doing (finding matching code point sequences), the results may vary depending on which normalization form is chosen. The FindText API should either (a) be specific about whether the composed or decomposed sequence is used or (b) define separate terms for composed and decomposed.

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-501: Unicode equivalence type non-specificity ⓟ [find-text] (from sysbot+tracker@w3.org on 2015-10-16)

Related notes:

Display change log