Comment 38 for bug 1001033

Werner,

Thanks for your input! I appreciate your position regarding the bug reports.

I disagree with most of what you say about the FontForge issue. I think
I argued my point cogently and completely elsewhere. Since you bring it
up, I will write to you privately on the matter (once I re-read that disturbed wad of material),
as it only obliquely touches on the present bug.

Unfortunately, what was one discussion is now three or four.
I'm running around putting out fires here.

Weeble,

First, it was very important for me to be aware of this change to FreeType.
It changes the way FreeFont is packaged.
I will have to take some actions (not sure what yet).
Thank you!

Although the FreeType issue would likely have an effect on the PyGame values,
it really seems to me that it is something separate.
Tell you what, if you like, open up a support issue, something like
    "change to FreeType handling of 'isFixedPitch'"
on the FreeFont site.
    https://savannah.gnu.org/projects/freefont/
That way you can be apprised of what I do with it.

 As to it being a bug per se, I don't see it that way. It isn't a bug that old versions
of FreeFont conflict with development versions of FreeType.

For the time being, I would like to better understand Sam's original problem.
Thanks for locating the germane code.
I hope I have time to settle the matter soon.