I see that even though MacType can render glyphs without pixel-grid snapping,
the position of the whole glyphs in a string is however always snapped to the
pixel grid. In other words, all instances of "a" start at the same position
with regard to pixel boundary, instead of some starting 1/3 or 2/3 of pixel
shifted.
The result of missing sub-pixel glyph positioning is uneven, "jumpy" text, bad
kerning.
Anyway, thank you for MacType! It has changed the way I see the world of
computer text!
Original issue reported on code.google.com by pktr5pk...@gmail.com on 6 Dec 2013 at 3:54
Original issue reported on code.google.com by
pktr5pk...@gmail.com
on 6 Dec 2013 at 3:54