emerging xorg-x11 with +bitmap-fonts makes some fonts look very crappy in Firefox. The fonts on cnn.com for example. emerging with -bitmap-fonts fixes the problem. I do get this seg fault during the xorg emerge no matter which way bitmap-fonts is set: ^[[A^[[73G ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32;01m*^[[0m Creating fonts.scale files... ... /var/tmp/portage-pkg/xorg-x11-6.8.2-r1/inf/xorg-x11-6.8.2-r1.ebuild: line 1815: 3027 Segmentation fault LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:${ROOT}/usr/$(get_libdir)" ${ROOT}/usr/bin/ttmkfdir -x 2 -e ${ROOT}/usr/share/fonts/encodings/encodings.dir -o ${x}/fonts.scale -d ${x} Reproducible: Always Steps to Reproduce: 1.emerge xorg-x11 with +bitmap-fonts 2.startxfce4 3.firefox -> cnn.com Actual Results: crappy fonts Expected Results: smooth fonts [ebuild R ] x11-base/xorg-x11-6.8.2-r1 -3dfx -3dnow -bitmap-fonts +cjk -debug +dlloader -dmx -doc +font-server +hardened -insecure-drivers -ipv6 -minimal +mmx -nls -opengl +pam -sdk +sse -static +truetype-fonts -type1-fonts (-uclibc) +xprint -xv
I just noticed that the fonts _inside_ my yahoo.com mail account look better with my current +bitmap-fonts xorg build. All others that look different between the two USE setting that I have seen in Firefox look drastically better with -bitmap-fonts.
Yep. Thus the description for the flag. /usr/portage/profiles/use.local.desc:x11-base/xorg-x11:bitmap-fonts - Builds the crappy 100 DPI and 75 DPI fonts You might want to set firefox up to always use your fonts, so you can pick your favorites for serif, sans-serif and monospace instead of getting them chosen for you. Unless you'd like to submit changes to the fonts, not much gonna happen on this. If you do decide that's what you'd like to do, bugs.freedesktop.org is the place.
Looks like you are dead on. I needed to tell Firefox to always use my fonts. Thanks!
