On 15-03-17 06:33 PM, Adam Twardoch (List) wrote: > So actually, if I use the "coretext" shaper, then it doesn't really matter > whether the font has GSUB/GPOS or morx/kerx, because HB takes OT-lingo > feature spec, translates it to the AAT feature spec, and just calls CoreText, > and CoreText itself decides "what to do" with the AAT feature spec, i.e. > whether to use these features directly with morx/kerx or internally translate > it back to OT tags and use GSUB/GPOS. > > Right?
Correct. > A. > >> On 18 Mar 2015, at 01:36, Behdad Esfahbod <[email protected]> wrote: >> >> On 15-03-17 05:27 PM, Adam Twardoch (List) wrote: >>> Behdad, >>> >>> What functionality does the coretext_aat shaper currently support? >> >> What the coretext_aat does is: if the font has 'mort' or 'morx' table, then >> call the coretext shaper, otherwise fail (and let ot shaper handle). It's >> just a mechanism to choose which shaper to use. >> >> >>> I can see that it does something with "mort" and "morx", but possibly not >>> "kerx" or the extended "kern" table? Or does it? With something like >>> hb-view, which options (if any) are passed on? Direction, script, language, >>> features? >> >> Everything is supported. >> >> >>> Thanks, >>> A. >>> _______________________________________________ >>> HarfBuzz mailing list >>> [email protected] >>> http://lists.freedesktop.org/mailman/listinfo/harfbuzz >>> > > _______________________________________________ HarfBuzz mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/harfbuzz
