- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Jul 2018 16:41:17 +0000
- To: public-i18n-archive@w3.org
@EricSharkey/@Richard57 I'm aware that case fold doesn't preserve normalization. However, I had overlooked D145. I suspect we need to rework the algorithm in light of this. Providing canonical (or compatibility) equivalence should at least be an option for users of the spec. That suggests four versions of the "algorithm": 1. "Lightweight equivalence". The current "algorithm" with no normalization or casefolding. 2. "ASCII equivalence". The current "algorithm" with no normalization and ASCII case fold (for vocabularies that need this). 3. Canonical equivalence. NFD -> casefold -> NFD 4. Compatibility equivalence. NFD -> casefold -> NFKD -> casefold -> NFKD Thoughts? -- GitHub Notification of comment by aphillips Please view or discuss this issue at https://github.com/w3c/charmod-norm/issues/172#issuecomment-405309578 using your GitHub account
Received on Monday, 16 July 2018 16:41:20 UTC