Comment 34 for bug 1001033

Hi Werner,

Now this has gotten really messy.
I don't know what we can do with it.

1) if the flag isFixedPitch is involved, it's going to get crazy.

     - This flag *is* set in the current version of FreeMono.
        (Why don't you download it and try it? -- Please! It has a lot of new stuff!)

    - I agree the flag *should* be set for a monospace font. It wasn't set in the old version
      of FreeMono, as you point out, because FontForge un-sets it.

    - I submitted a patch to FontForge that would cause it to *set* this flag to conform with the
     most obvious reading of the TrueType standards. But somebody has been objecting to it,
     with very dubious arguments and tactics. (This is a very unfortunate slant to the present issue.)

    - But I thought this flag only had an effect in Windows. Now you're telling me recent releases
      of FreeType *use* the flag??? Oh man!

2) Didn't we established that the original complaint, using PyGame, really arose in
    *any* monospace font (depending on the resolution)?

    I just ran a modified version of Sam's script, which looks for characters of varying width,
    in *his* sense. Again, it shows *all* the fonts have this issue.
    (On my Ubuntu 12.04 with stock FreeType)

    See attached, please!

   Was that incorrect?
   Or does it have to do with the FreeType version?

3) Are we 100% sure Sam's complaint is identical with this issue you're reporting,
     having to do with recent changes to FreeType?

4) None of the questions I asked has been answered:
     What units are these PyGame units anyway?
     In what sense is the monospaced property to be preserved in rendering?
     (Your recent results say to me, the FreeType group recently changed their policy regarding this.)

:P !