Summary: | freetype 2.1.9[-r1] breaks usability of certain bitmap fonts (profont-x11, maybe others) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrew D. Keyser (aka Legoguy) <legoguy> |
Component: | Current packages | Assignee: | Gentoo Fonts Team <fonts> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | troworld |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrew D. Keyser (aka Legoguy)
2004-12-24 16:53:03 UTC
This problem was fixed by re-encoding the font, but you still have to wonder, what changed? Everyday users won't know how to re-encode a font just to make it work again, so I myself still consider this a bug. what do you mean by re-encoding ? remerging & going trough the font creation steps ? I also have sets of bitmap fonts, but no problems here with them. If it crashes we need a backtrace. By re-encoding I mean actually decoding the font to BDF with FontForge and then re-encoding it to PCF with bdftopcf. this seems to be an ABI issue with freetype 2.1.9, not sure what we to do about it. Apparently it doesn't hit all fonts bdf to pcf fonts, x11 has quite a few of them. I tested profont and it works fine here, firefox displays it correctly and doesn't crash (same for other apps). I think this can be closed with NEEDINFO, unless someone's still using a 2 year old fontconfig :) The reason why it works is because I actually modified ProFont and sent the author the changes and it is now the "official" Linux profont version that you have ;) Bug can be closed at least in the case of ProFont, however I'm not sure how many older fonts are still broken. Closing then, noone else reported this w/ any other font. |