- From: siqin <siqin@almas.co.jp>
- Date: Wed, 29 Jul 2015 20:50:10 +0900
- To: Andrew West <andrewcwest@gmail.com>, "Badral S." <badral@bolorsoft.com>
- Cc: public-i18n-mongolian@w3.org
- Message-ID: <55B8BDF2.6030902@almas.co.jp>
Hi All, I create a sample page about NNBSP on our mongolianfont site. http://www.mongolfont.com/test/sample_nnbsp.html I also tested this text on some app and the result like below. No nnbsp_win7_firefox_39.0.png No nnbsp_win7_chrome_44.0.png No nnbsp_win7_ie_11.0.21.png No nnbsp_win7_opera_31.0.png Ok nnbsp_win7_safari_5.1.7.png Ok nnbsp_win7_notepad.png Ok nnbsp_win7_word_2010.png Ok nnbsp_win7_excel_2010.png Ok nnbsp_win7_word_2010.pdf No nnbsp_copy_from_pdf_paste_to_notepad.png No nnbsp_mac_chrome_44.png No nnbsp_mac_firefox_39.0.png No nnbsp_mac_opera_27.0.png Ok nnbsp_mac_safari_8.0.7.png And I also send the sample text throw skype. The result is that The starting of NNBSP was losted. I do not know france. When france word and mongolian word connected with NNBSP, the NNBSP belong to which one ? This case exists in Mongolian document like mongolian people studing france language. (asume the france languauge need NNBSP) SiqinBilige. On 2015/07/29 20:13, Andrew West wrote: > Hi Badral, > >> Any incorrect classified breaker characters (for us NNBSP, MVS- between >> unicode 5.0 and 6.3) corrupt GSUB rules of OTF for Mongolian. > I'm afraid that I don't see how the classification of NNBSP or MVS can > break the GSUB rules. Maybe it has an effect on whether the rendering > system (e.g. Uniscribe) applies the GSUB rules around the character, > but should not affect the GSUB rules themselves. And if the rendering > system is not applying OpenType shaping rules for Mongolian around > NNBSP or MVS then that is a bug in the implementation. > >> The suffixes >> have to be started by "medial" variant after NNBSP. This rule is already >> implemented in every Mongolian Fonts. But every suffix starts with "initial" >> variant, if NNBSP belongs to spaces or word boundary class ... The problem exists on >> Openoffice, Libreoffice, Google Chrome, Safari and Opera as my test. > That would be a bug in the implementation of these products. Of the > above software I only have Google Chrome installed, and that renders > NNBSP + suffix correctly, e.g. on this page > <http://en.wikipedia.org/wiki/Subei_Mongol_Autonomous_County> > NNBSP+yin is rendered with the medial form as expected. > > Andrew > > >
Attachments
- application/x-zip-compressed attachment: nnbsp_test.zip
Received on Wednesday, 29 July 2015 11:50:33 UTC