- From: Behnam Esfahbod ✅ via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Oct 2017 22:03:59 +0000
- To: public-i18n-archive@w3.org
I submitted a long individual feedback. Here's the part related to this issue: ---- # 2. Scope of the algorithm The scope of the algorithm is not clear, neither in its title nor in the language. The name “Unicode Arabic Mark Ordering Algorithm” is suggesting that this is expected to be the only way Arabic Marks should be ordered in Unicode. That’s clearly not the case. In fact, the document is proposing an algorithm for “reordering” Arabic Marks (not just how they should be ordered) to solve a problem in “rendering” of the script. The title need to be clear about this. Maybe “Unicode Arabic Mark Reordering Algorithm for Rendering” (AMRAR)? Similarly, the Section 2 “Background” doesn’t clarify the scope of the algorithm and only explains how something is not working for some specific application with the existing normalization methods. # 3. Consequences of the Algorithm: Normalization The draft proposal is not clear about the effects of applying the algorithm on text. Specially, for strings X for which this algorithm is useful, we have UAOA(toNFC(X)) ≠ toNFC(UAOA(X)). So, although the behavior of the algorithm can be stabilized over Unicode verions, it’s very important how and when it’s applied to the text, since it changes a text in normalized form to a non-normalized form. Therefore, in terms of normalization, the algorithm cannot be considered stable at all. The document needs to be clear about this, even though it’s obvious from a technical point of view. -- GitHub Notification of comment by behnam Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/496#issuecomment-336578405 using your GitHub account
Received on Friday, 13 October 2017 22:04:19 UTC