Chad Brokaw
Chad Brokaw
The [Ahem font](https://web-platform-tests.org/writing-tests/ahem.html) is used in web platform tests and its well-defined glyphs make great test cases for autohinting. See also: https://issues.skia.org/issues/344529168
1 GB of text per layout is more than generous. We're likely to see severe performance degradation long before reaching this limit anyway suggesting that applications wanting to support excessively...
Testing with fauntlet revealed that applying autohinting to the [Handjet](https://fonts.google.com/specimen/Handjet) font takes considerable time to the point where we should likely avoid doing it at all. Let's get some metrics...
Initial implementation was focused on matching FreeType both for expediency and to ensure correctness. There is a lot of room for improvement in code quality by making use of more...
Support for this exists in FT (and thus our current code) but it has been disabled for years and only seems to apply to CJK with an emphasis on vertical...
Initial autohinting implementation will not include the bits that require shaping. Let's do that next. This has two components: 1. Examine layout tables to assign styles for glyphs that are...
Some confusing bits in the FreeType CJK autohinter. 1. Scaled/fitted values are never generated for stem widths so they're always 0. https://gitlab.freedesktop.org/freetype/freetype/-/blob/57617782464411201ce7bbc93b086c1b4d7d84a5/src/autofit/afcjk.c#L661 2. There's an extra loop to detect round...
Some recent restructuring (ref #1079) to support autohinting leaves us in an unfortunate state with a new "common" object for glyf and cff. After autohinting is done and all requirements...
Large checkpoint of Latin autohinting plumbed through to the public API. Primarily for @drott to experiment with Skia integration. Don't merge me.