I don’t remember the list off-hand, but a lot is related to language specific features. There’s also 3 or 4 levels of ligatures. There were some features I wished it supported (maybe it was contextual alternates?), but the OpenType support in general is not bad. There’s definitely missing pieces in Japanese composition, but there’s also a lot of support.
I think native browser support is pretty good, and for basic text rendering you can probably fall back to default browser support and for text in FlexJS components that’s the way to go, but for pixel-perfect composition, browser rendering of text is not going to cut it. There’s been some efforts to do some OpenType rendering using Javascript, most notably Bram Stein's work[1] There’s also opentype.js[2]. But, everything that I’ve found which was done to date is really basic. Any of the more advanced OpenType features are not supported at all. Some GSUB support, but not even basic GPOS support, etc. It’s kind of scary how hard it’s going to be to really do text right in the browser. Getting even close to FTE is really hard. And I haven’t a clue what performance is going to be like in JS. I would have to guess that it’s going to be a sore point… [1]https://github.com/bramstein/opentype [2]https://github.com/nodebox/opentype.js On Nov 2, 2015, at 3:07 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 11/1/15, 10:26 AM, "Harbs" <harbs.li...@gmail.com> wrote: > >> Not just RTL. There’s an awful lot of OpenType features that it supports. >> (Of course It would be great to support even more…) ;-) > > I wasn’t aware of that. What kinds of things and how do the browsers do > it? > > -Alex >
