- From: Badral S. <mail@badral.net>
- Date: Sun, 05 Jul 2015 08:43:51 +0200
- To: public-i18n-mongolian@w3.org
- CC: Greg Eck <greck@postone.net>
- Message-ID: <5598D227.1080101@badral.net>
Hi Greg, NNBSP is real problem. Please see the highlighted (bold) text. If this is not changed anymore then this symbol is not useful for mongolian, although it introduced by Report 170. In this case we have following two options. 1. We should handle suffix bindings also by MVS in fonts. (Quick and dirty way) 2. We need to introduce new control glyph like NNBSP, which should not be handled as whitespace but as joiner. It should not be named like NNBSP but Suffix Joiner or something to avoid mishandling. (Slow and cleaner way) The best way in my opinion is NNBSP must be handled as joiner/formatter in all rendering engines like ICU, Harfbuzz, MS-Uniscribe etc. PS: My reply to "RE: NNBSP-MVS Impact" thread not delivered. Probably, my emails cannot be delivered to public-i18n-mongolian list. Regards, Badral -------- Forwarded Message -------- Subject: Mongolian feedback on Unicode 6.3 Date: Tue, 13 Aug 2013 14:21:45 -0700 From: Rick McGowan <rick@unicode.org> To: Andy Heninger <andy.heninger@gmail.com> CC: mail@badral.net Hello Andy, and Badral -- Regarding the feedback below... The Mongolian Vowel Separator is not whitespace any more as of Unicode 6.3. *The NNSP is and will remain a whitespace; it can't be changed at this stage because of stability policies.* But the issues around Mongolian are being investigated, and further work will be done. There was an extensive discussion of Mongolian during the meeting, and people will be discussing various issues ad hoc. Regards, Rcik Original bug report: http://bugs.icu-project.org/trac/ticket/10212
Received on Tuesday, 7 July 2015 10:42:25 UTC