- From: Behnam Esfahbod ✅ via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Oct 2017 18:51:14 +0000
- To: public-i18n-archive@w3.org
behnam has just created a new issue for https://github.com/w3c/i18n-activity: == Check compatibility of UAOA with NFC == 1. Overview http://www.unicode.org/reports/tr53/ > This algorithm is the simplest algorithm that matches user expectations, stays within the stability requirements of Unicode, correctly renders data in normalized forms, and renders all canonically equivalent sequences the same way. ## "stays within the stability requirements of Unicode" This needs to be checked. Since the algorithm uses NFD and then reorders marks and brings any MCM mark to the front of the list, this can break actually break stability by resulting in the following: ``` UAOA(NFC(x)) ≠ NFC(UAOA(y)) when NFC(x) = NFC(y) ``` If there are `x` and `y` that this can happen, then this claim would be invalid and misleading. --- **WHEN CREATING A NEW ISSUE DO SO ABOVE THIS PARAGRAPH, REPLACING THE PROMPTS, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** When this issue is raised in the github/bugzilla/mail of the WG that owns the spec, use the text above this para as the basis for that comment. Then edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue, but leave the remaining text below this para unaltered. **This is a tracker issue.** Only discuss things here if they are i18n WG internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:** link_to_issue_raised Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/495 using your GitHub account
Received on Tuesday, 3 October 2017 18:51:04 UTC