Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-22 Thread vernon adams
Werner, Not sure i understand 100%, but isn't it significant that the infinality patched freetype only renders ttfautohinted fonts in this way? An infinality patched freetype (bug or not) renders other instructed truetype fonts perfectly normally afaik. -vern On 21/04/12 21:01, Werner

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-22 Thread Werner LEMBERG
Not sure i understand 100%, but isn't it significant that the infinality patched freetype only renders ttfautohinted fonts in this way? An infinality patched freetype (bug or not) renders other instructed truetype fonts perfectly normally afaik. Well, Erik tries to implement Greg's ClearType

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread vern adams
Many thanks for this Erik, You seem to have recreated the glitchy rendering that earlier versions of ttfautohint created on iOS and when adobe apps converted ttfautohinted fonts to outlines. That's very interesting i think, as it probably points to something important still going on. First

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread Werner LEMBERG
Today I tested out the TT-instructed Oxygen font from the KDE repo with my TT subpixel hinting patches. This is the result: http://www.infinality.net/files/oxygen-infinality-problems.png This looks like Oxygen has been hinted with an older version of ttfautohint which was buggy... Current

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread Werner LEMBERG
First though i think we should check that the issue is not with a particular buggy build of Oxygen; FYI: Recent versions of ttfautohint add version information and calling parameters to the `name' table; older ones don't. Werner ___

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread vern adams
I 've sent Erik ttfautohint 0.8 versions of Oxygen to confirm the problem. -v On 21 Apr 2012, at 10:14, Werner LEMBERG wrote: Today I tested out the TT-instructed Oxygen font from the KDE repo with my TT subpixel hinting patches. This is the result:

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread Werner LEMBERG
I 've sent Erik ttfautohint 0.8 versions of Oxygen to confirm the problem. Thanks! Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread Infinality
Hi Vernon / Werner, I tried it out with the version of Oxygen you sent me, with similar results. I was also able to view it in Windows XP, and as I thought it renders fine there (although they filter the hell out of it). 1. This is the image in my original email. The settings I'm using

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread Werner LEMBERG
Erik, thanks for your analysis. (The main difference between #2 and #3 is that #3 snaps horizontal stems to pixel boundaries, which normal Freetype slight hinting does not do. I personally prefer the stems to be snapped to integer pixels like this. It looks less dirty to me, however

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread Infinality
Thanks Werner. I'd definitely be curious to know how the MS rasterizer determines when to/not use backwards compatibility mode. As of right now, my patches have no way of automatically determining this, and I'd like to go from using a hard-coded list of font names to something more dynamic!

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread vern adams
Erik, Are you testing the rendering via web browsers only? Or do you get same results with e.g. ftview? -vern On 21 Apr 2012, at 16:51, Infinality wrote: Hi Vernon / Werner, I tried it out with the version of Oxygen you sent me, with similar results. I was also able to view it in

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread Infinality
I've only been using browsers for these, but AFAIK it *should* be the same. :) On 04/21/2012 12:03 PM, vern adams wrote: Erik, Are you testing the rendering via web browsers only? Or do you get same results with e.g. ftview? -vern On 21 Apr 2012, at 16:51, Infinality wrote: Hi Vernon /

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread vernon adams
Ok, so i've tested this with a infinality patched freetype 2.4.9 w Kubuntu. Using ftview or the system font viewer any truetype font instructed with ttfautohint (i'm using 0.8) renders as Erik has shown. Pretty much the same screwed up rendering that we saw with old versions of ttfautohint w

Re: [ft-devel] ttfautohint / Oxygen / infinality

2012-04-21 Thread Werner LEMBERG
Ok, so i've tested this with a infinality patched freetype 2.4.9 w Kubuntu. [...] Obviously a bug w.r.t. Erik's implementation of ClearType's compatibility mode. I've contacted Greg Hitchcock, asking for clarification. Werner ___

[ft-devel] ttfautohint / Oxygen / infinality

2012-04-20 Thread Infinality
Hi guys, Today I tested out the TT-instructed Oxygen font from the KDE repo with my TT subpixel hinting patches. This is the result: http://www.infinality.net/files/oxygen-infinality-problems.png Yikes!!! After examining the TT instructions in the instructed version of the Oxygen fonts, it