- From: Internationalization Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Fri, 16 Oct 2015 21:43:24 +0000
- To: public-i18n-core@w3.org
I18N-ISSUE-501: Unicode equivalence type non-specificity ⓟ [find-text] http://www.w3.org/International/track/issues/501 Raised by: Addison Phillips On product: find-text 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.
Received on Friday, 16 October 2015 21:43:28 UTC