Aric Stewart aric@codeweavers.com wrote:
what Mac does in that case?
The mac handles the fonts without issue
Why do you think that your fix is correct?
..windows tmAveCharWidth should never be negative, and yet this logic causes it to be so for these fonts. If we want to be able to support these fonts, which work in every other regard, we need to have a fix like this.
What did I not answer?
What value does Mac return for these kind of fonts? Does it take an abs() like in your patch? Does it trancate the value? Does it calculate it somehow (like taking an average of glyphs say a+z and A+Z)? Does it do something different?