Hi Steve, Am 09.06.2012 09:21, schrieb Steve White:
The argument against this I cannot understand. First that the spec was unclear (in what respect, I could not understand. Maybe because it didn't say what they wanted it to say.) and then that such a setting would break some Windows apps (but no examples were provided -- just a referece to a mailing list...I followed this lead, found a long conversation, but... none of what I found there indicated a failure caused by setting this flag. Confusion.)
I am not sure if I got this right. There'll be a change in the way FreeType interprets metrics of monospaced fonts based on a flag being either set or not and a change you proposed for FontForge to set this flag automatically has been rejected, right?
Depending on how plausible and convincing this change is (at the moment, to be honest it is not, could you please provide some more background, e.g. some links to the patch and the discussion following it?), maybe we could add it as a distro patch in Debian.
So... I'm considering other options, such as setting the flag *outside* of FontForge in the build process. It's a cludge but it would work. Just, it'll take a day or two to write it.
You mean, as in patching the binary font files? That sounds fragile... - Fabian