You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over at golang#90 some discussion has been happening regarding incorrectly rendered glyphs. It appears (?) that true type fonts should generally set UseNonZeroWindOrder = true on the rasterizer. However, the rasterizer is inaccessible on instances of truetype.Face as well as in freetype.Context. Unless anyone knows more, we should make these accessible, i.e. change r to R in both structs. The value does not control any generated data and can be changed at any time between rasterization of glyphs.
The text was updated successfully, but these errors were encountered:
It was a lot simpler to just set UseNonZeroWindOrder = true on the rasterizer when it is first created. I verified that this fixes the issue -- Apple Chancery euro symbol had it, for example.
Over at golang#90 some discussion has been happening regarding incorrectly rendered glyphs. It appears (?) that true type fonts should generally set
UseNonZeroWindOrder = true
on the rasterizer. However, the rasterizer is inaccessible on instances oftruetype.Face
as well as infreetype.Context
. Unless anyone knows more, we should make these accessible, i.e. changer
toR
in both structs. The value does not control any generated data and can be changed at any time between rasterization of glyphs.The text was updated successfully, but these errors were encountered: