I wrote these for bug 385263, but the FT2 code might as well also use the weight translation. The FT2 code doesn't know the difference between oblique and italic yet so I haven't changed it to use the style calculation. I think the use of ranges rather than a case statement and rough estimate is safer against new fontconfig predefined weights and other possible values from fontconfig settings. FontFamily::FindFontEntry in gfxFT2Fonts.cpp will truncate the 901 to 9 (and doesn't check that the result is within array bounds).
Attachment #338021 - Flags: review?(roc)
Attachment #338021 - Flags: review?(roc) → review?(pavlov)
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.