Comment 36 for bug 1001033

Steve,

disassembling the 20090104 version I see that some glyphs have different widths, for example `.notdef' and `.null'. FontForge is correct to not set the `isFixedPitch' flag. The same is true for the 20100919 version, where the `.null' glyph has a different width.

Regarding FontForge: I've followed the thread, and Khaled is right. I'm sorry that it became personal. Please bear in mind that the `isFixedPitch' flag comes from a very ancient time where non-spacing glyphs (let alone Unicode or OpenType) was something exotic. It's also unfortunate that the OpenType standard doesn't provide a better explanation for the flag which can't be misinterpreted.

Note that I only react to the input. Here on LaunchPad I'm just a guest observer,; I only take care of the FreeType bug report. It's my job to analyze the data and point out the problems. It's *not* my job to search the internet whether a better solution exists. Sometimes I know a better one, but usually I simply don't have enough time for that, sorry. Besides that it's good to know that recent versions of the font have this issue fixed!