Created attachment 8675991 [details] firefox_android_vertical_lr_mongolian_incorrect.png User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0 Build ID: 20151014143721 Steps to reproduce: access : http://www.mongolfont.com/ Actual results: firefox_android_vertical_lr_mongolian_incorrect.png Expected results: firefox_android_vertical_lr_mongolian_correct.png
The glyphs need to rotate 90deg clockwise.
Strange. I can reproduce this with current Nightly on an Android tablet ... but on a FirefoxOS device, it renders fine.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Because of technical reason, the glyphs not upright in mongolian(1800..18AF) and Phags-Pa(A840..A87F) fonts. It is counterclockwise 90deg. So, according to http://unicode.org/reports/tr50/ mongolian(1800..18AF) and Phags-Pa(A840..A87F) need to rotate 90deg clockwise.
in vertical_lr writing mode.
in both vertical_rl and vertical_lr writing mode.
jdaggett: offhand, I'm mystified why this would fail on Android only, when it appears to work OK everywhere else. Maybe something about how we're using Freetype (though I would have expected that to be the same on b2g)? If you have time to investigate a bit, that'd be really helpful.
siqinbilige: I notice the http://www.mongolfont.com/ site is serving different versions of the font: Firefox on OS X gets mnglwhiteaat.ttf, while on Windows it gets mnglwhiteotf.ttf. (Is this a recent change? I don't remember noticing it before.) Unfortunately, the use of AAT-based webfonts for scripts that require complex shaping -- such as Mongolian -- is not supported by Firefox (or in Chrome, I believe), because the AAT tables are discarded by the OTS sanitizer. (It's too easy for a badly constructed -- or malicious -- AAT font to cause crashes deep within Core Text code...) Therefore, it would be preferable to serve the OpenType version mnglwhiteotf.ttf to Mac clients, except for Safari. This will give you better results in both Firefox and Chrome.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
Aha, that explains things! Thanks for following up here.
You need to log in before you can comment on or make changes to this bug.