Hi Nikolaus, I suppose this reduced form of hinting may be better than completely unhinted rendering. You'd be giving up hinting stems that are not in alignment zones, like the middle stem of 'E'. Also, you'd need some way to identify and locate the stems in an outline. In FreeType, there is a run-time auto-hinter that could do this. In normal CFF fonts, there is an auto-hinter that runs at font production time and records its output as a series of hstem and vstem declarations in the charstring. The production auto-hinter also recognizes and handles conflicting hints by partitioning complex glyphs into multiple hint zones, using the hintmask operator.
-Dave On 6/2/2017 3:14 PM, Nikolaus Waxweiler wrote:
Hey list, hey Dave Arnold, I noticed that the CFF fonts served on e.g. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmedium.com%2F%40raphlinus%2Finside-the-fastest-font-renderer-in-the-world-75ae5270c445&data=02%7C01%7C%7Cab8ed3ced4934945cd9808d4aa04b4ac%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636320384572695460&sdata=%2BuYQz2yMS4imZ%2BA42HrJ7YSnZEErHr%2Bw47xT3fppBeo%3D&reserved=0 aren't snapped to the grid. Turns out they don't contain any vertical or horizontal hints, just the blue zones. I don't remember if I asked this before, but what keeps the CFF engine from simply snapping everything inside a blue zone to the same pixel height? _______________________________________________ Freetype-devel mailing list [email protected] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.nongnu.org%2Fmailman%2Flistinfo%2Ffreetype-devel&data=02%7C01%7C%7Cab8ed3ced4934945cd9808d4aa04b4ac%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636320384572695460&sdata=4i5Z4YKEc1Fw1xMbOc1986sLpWyQa8KmGnedyAm%2Bsf0%3D&reserved=0 .
_______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
