- From: Behnam Esfahbod ✅ via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Oct 2017 20:38:52 +0000
- To: public-i18n-archive@w3.org
@khaledhosny, I case it's not clear from my comments, I'm not against the algorithm in general. In fact, I believe it has potential, but needs to be documented better and put in the right place. >From all the discussions, it sounds like it's only supposed to be used for text rendering (fonts), but not text processing, transforming, or transferring. If so, maybe it belongs to OpenType or other standards, as a normative step. The fact that it's being proposed as a generic algorithm for processing and editing Arabic text (that's how it looks like at the moment, at least) is not a good thing for the users of the script and applications trying to understand and support the script. More importantly, the examples provided to justify the need of the algorithm are based on corner cases of a single use-case: Quranic text. The document completely lacks any analysis on how the algorithm impacts average users of all the variety of use cases of the script. In fact, by claiming to be "within the stability requirements of Unicode", it's claiming to have no affect on average use cases. (More in <https://github.com/w3c/i18n-activity/issues/495>) The selection rational for MCM list sounds arbitrary and needs data for the claims of differences between "small seen" and "small meem" marks and such. The same is true for other similar claims in the document, which -- GitHub Notification of comment by behnam Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/493#issuecomment-333971032 using your GitHub account
Received on Tuesday, 3 October 2017 20:38:42 UTC