GetGlyphOutline API is a much better renderer than freetype

[GoogleCodeExporter]

I am running gdipp v0.9.1 on windows 7 x64. This isn't really a bug but more of 
an observation/tip for other users.

I used the default freetype renderer when I first installed gdipp but noticed 
that in several places (many already mentioned here) kerning was bad and 
characters wouldn't get rendered in certain programs (l's and -'s in 
particular). I started playing around with the settings and discovered that, at 
least with hinting off, GetGlyphOutline API produces almost identical results 
in smoothness of rendering but does not appear to suffer any of the kerning and 
disappearing issues I had noticed previously.

As a side question: the wiki guide says that each renderer reserves 10 number 
values for 9 variations. I tried values like 15 in the renderer selection and 
that also fixed the kerning/disappearing issues, but appears to be using 
GetGlyphOutline API. How do these "variations" in rendering actually work?

Original issue reported on code.google.com by wu.s...@gmail.com on 8 Apr 2011 at 3:36

[GoogleCodeExporter]

Great tip, it works fine and solves the kerning problem in firefox 5 and other 
programs.

Original comment by albedosh...@gmail.com on 28 Jul 2011 at 1:37