Created attachment 362844 [details]
Safari on MacOS (Mojave)
NNBSP is not correctly rendered on MacOSes.
NNBSP (202F) is a very problematic character in Unicode standard and used to connect Mongolian suffixes to stems or to preceding suffix.
If this character handled as white space, then almost all Mongolian suffixes can not be rendered correctly.
However, recently almost all engines and word processors render this character correctly. Even Webkit itself on iOS renders it flawless.
It is just broken on MacOS.
Please correct it.
Created attachment 362857 [details]
On High Sierra
On High Sierra .notdef glyph is shown instead of NNBSP.
The shaping is also failed on High Sierra. The attachment is just to show .notdef glyph.
What is a link where I can view that webpage in the screenshot? I would like to investigate this.
Dear Myles C. Maxfield,
The webpage is reachable under http://test.openmn.org/.
I just opened that webpage on macOS and iOS, and the two sites look identical to me. Can you describe more specifically which part of the rendering is incorrect?
(I can't read Mongolian, so I'd appreciate as much detail as possible.)
Created attachment 363468 [details]
Rendered correct on Chrome, Firefox, IE, Opera etc.
Created attachment 363469 [details]
Rendered incorrect on Safari (probably modern)
NNBSP is also broken on all modern iOS. I just tested on iOS 12.1.1, iOS 12.1.4.
There exist no problems on old iOS devices. For instance: iOS 9.3.5
I just uploaded to images one is incorrect (Safari-Incorrect.png) and one is correct (Chrome-Firefox-IE-correct.png).
(In reply to mail from comment #9)
> Ahh sorry,
> NNBSP is also broken on all modern iOS. I just tested on iOS 12.1.1, iOS
> There exist no problems on old iOS devices. For instance: iOS 9.3.5
> I just uploaded to images one is incorrect (Safari-Incorrect.png) and one is
> correct (Chrome-Firefox-IE-correct.png).
Ah, that makes it much more clear. Thank you so much!
Using raw CoreText draws it correctly. My guess is that the shaping tables in the font specifically involve the NNBSP character, but WebKit treats this character as a space and chops up the text here, and doesn't include the NNBSP in the shaping.
NNBSP is introduced in Unicode to shape Mongolian separated suffixes correctly and to do correct word boundary.
Thus, NNBSP is used in OTF table to shape that suffixes. This character should not be handled as SPACE.
Also want to note, that this problem occurs for all fonts I have tried, including system-ui, serif and sans-serif generic fonts.
And here is another test case reproducing no width for 202F: