>> If you limit hinting-range-max to a value where the blue zones are >> still handled, the generated bytecode uses this hinting set for all >> larger sizes also. Finding a good value for hinting-range-max has >> to be done with trial and error, but a waterfall already indicates >> bad sizes, so hinting-range-max must be less than that). > > hmm i have tested varying min-range & max-range - by shifting ranges > i can get the 'egging issue' to move up/down a ppem size, so the > issue persists but just at different ppem's.
OK. > It seems to me that the egging issue is caused by the top curves of > the 'o' snapping to the top edge of the pixel that corresponds to > that alignment zone, if i force these curves to snap to the bottom > edge of the alignment zone pixel then the egging is fixed! Of > course then i need all pixels in the alignment zone to snap to the > bottom of the pixel to get uniform x-height throughout all glyphs. > > Could there be a way to force pixel snapping to the bottom of pixel > in some alignment zones like this with ttfautohint? While I basically understand what you write, I have some difficulties to imagine it visually. Could you provide FontLab snapshots of an `egged o', together with your proposed fix? Werner _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel