- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Sep 2017 11:43:09 +0000
- To: public-i18n-archive@w3.org
r12a has just created a new issue for https://github.com/w3c/i18n-activity: == When should UAOA be used? == http://www.unicode.org/reports/tr53/ It's not clear from the UTR when applications should use UAOA. One implication seems to be that it should be used any time normalisation is applied, however, "5.6 Other uses for UAOA" seems to imply that its use is optional and use just for certain operations. If UAOA should be used any time Arabic text is normalised, it seems problematic to me to package the algorithm as a separate UTR. For example, a large number of W3C specs require normalisation prior to string matching (think, for example, of matching CSS selectors against HTML ids). It is unlikely we can, if we wanted to, go back to all those specifications and require instead that they both normalise AND apply UAOA in order to ensure that strings match correctly. This is particularly complicated because we would need to say that UAOA needs to be applied only if Arabic text is being matched. On the other hand, if this algorithm were simply part of the overall normalization algorithm no change would be needed. If the application of this algorithm is actually optional, or implemented for just certain operations, the situation is much worse, because it would increase the likelihood of mismatched strings in Arabic. --- **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/492 using your GitHub account
Received on Wednesday, 27 September 2017 11:43:03 UTC