Summary: | x11-libs/libXfont-1.2.5 has no way to enable type1 font support | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andreas Arens <ari> |
Component: | [OLD] Library | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | iyosifov |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | modified ebuild for libXfont |
Description
Andreas Arens
2006-12-10 03:34:12 UTC
Created attachment 103735 [details]
modified ebuild for libXfont
The freetype module is supposed to render the Type1 fonts instead of the type1 module. What issues did you have with Type1 fonts after the switch to 1.2.5? (In reply to comment #0) > Of course it's possible to comment out the Load "Type1" from > the xorg.conf, but that's not a real solution. Why isn't it? (In reply to comment #3) > (In reply to comment #0) > > Of course it's possible to comment out the Load "Type1" from > > the xorg.conf, but that's not a real solution. > > Why isn't it? > The problem I had was that we now build (unconditionally) an xserver module which relies on a feature of libXfont for which we no way to enable, resulting in an unresolved symbol for the possible user. Commenting out the "Type1" module load _is_ away to get rid of that, but still leaves the non-working module in the build. As long as I also load "freetype" I indeed have no issue with Type1 font rendering (Joshua comment #2). The whole discussion is mood however, as freedesktop git shows that libXfont 1.2.6 will have Type1 support enable by default and the added useflag therefore is not required any more. So once libXfont 1.2.6 is in portage this can be closed. 1.2.6 has been committed. Thanks for sticking with this! |