>> Finally, there is the problem of glyphs which can't be addressed
>> with a cmap directly, like small caps which are activated by an
>> OpenType feature. Similar to FreeType's autohinter, such glyphs
>> don't get any special consideration and are treated by the default
>> hinting module (in FreeType this is the `cjk' module currently, and
>> in ttfautohint it can be either `dummy' or `latin', to be
>> controlled by another yet-to-be-written configuration option :-).
>
> With HarfBuzz it's quite easy to list every glyph that can be
> accessed through, say, the 'latn' GSUB table. I probably can
> provide some API for such introspection. That may solve your
> ttfautohint problem, but not FreeType's.
Yes, this would be very helpful. For FreeType, there could be an
interface to the autorhinter also, extending the table which defines
the latin ranges.
If I understand you correctly, there currently isn't a possibility to
get such info from HarfBuzz easily (if at all)?
Werner
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
