You are not logged in.
Hi, PDFs in Firefox look really bad, I mean the fonts. How can I fix this?
http://i.imgur.com/dPRluBC.png
I have infinality bundle installed and I'm really happy with it.
I also have export MOZ_DISABLE_PANGO=1 in .bash_profile.
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr]
Offline
I forgot to mention, KDE.
And another thing, if I'm here, can Firefox have the normal file dialog that most of the app have? (dolphin-like)? Chromium has it, virtualbox, most of them ![]()
Offline
hi, about the kde-like menu in firefox you can use kgtk package in AUR repository, I use it and i'm happy to have "almost" the same feel in GTK apps, and you can find anothers tips in Uniform Look for Qt and GTK Applications
KF5 & Plasma5 (git versions) - Awesome WM
ASUS Sabertooth 990FX - AMD FX8350 - ATI Radeon HD 7970
[testing] repo
Offline
How do PDFs look in other applications? I use infinality-bundle as well and I've noticed that PDFs look bad in both Evince and mupdf but I'm still trying to make sure that I'm not crazy or I don't have something configured wrong, so I haven't said anything here.
Offline
In Evince it looks great.
Only in Firefox it's the problem...
Offline
Without infinality, just a plain vanilla freetype, I get reasonable font rendering in Firefox and very good rendering with mupdf. Rendering might be different if the Firefox generic serif font isn't Times New Roman. Inspecting one source for the page MilenKid offered, Firefox is calling for 16 pixel serif for the text.
Firefox pdf: http://imgur.com/wc6GGJ6.png
Firefox font settings:http://i.imgur.com/PDk60sT.png
Offline
Offline
infinality-bundle + FF (stock, no tweaks) = click The quality of the pdf document is pretty mediocre, though.
@hadrons123, this is only relevant for freetype2 2.4.12. I don't know about thisoldman, but infinality-bundle uses freetype2 2.4.11 which works perfectly well.
Edit:
KDE
Assuming that the infinality-bundle was installed and is working correctly, what are your current font settings in KDE (the ones you set in its control panel)? What fonts did you install? What is the output of
fc-match serifand
xrdb -q | grep Xft?
Last edited by bohoomil (2013-05-17 03:31:42)
:: Registered Linux User No. 223384
:: github
:: infinality-bundle+fonts: good looking fonts made easy
Offline
Without infinality, just a plain vanilla freetype, I get reasonable font rendering in Firefox and very good rendering with mupdf. Rendering might be different if the Firefox generic serif font isn't Times New Roman. Inspecting one source for the page MilenKid offered, Firefox is calling for 16 pixel serif for the text.
Firefox pdf: http://imgur.com/wc6GGJ6.png
Firefox font settings:http://i.imgur.com/PDk60sT.png
It looks great. Strange, I don't find Times New Roman. I will find how to install it, I remember something in aur about windows fonts.
infinality-bundle + FF (stock, no tweaks) = click The quality of the pdf document is pretty mediocre, though.
@hadrons123, this is only relevant for freetype2 2.4.12. I don't know about thisoldman, but infinality-bundle uses freetype2 2.4.11 which works perfectly well.
Edit:
MilenKid wrote:KDE
Assuming that the infinality-bundle was installed and is working correctly, what are your current font settings in KDE (the ones you set in its control panel)? What fonts did you install? What is the output of
fc-match serifand
xrdb -q | grep Xft?
Thank you, output is:
wbu@Leny ~ $ fc-match serif
LiberationSerif-Regular.ttf: "Liberation Serif" "Regular"wbu@Leny ~ $ xrdb -q | grep Xft
Xft.antialias: 1
Xft.hinting: 1
Xft.hintstyle: hintmedium
Xft.rgba: rgb
wbu@Leny ~ $ L.E. I have installed Times New Roman, still bad.
Last edited by MilenKid (2013-05-17 10:23:38)
Offline
Run firefox from the commandline, and see if it complains about libs or fonts.
I don't know these days whether it's still an advantage to compile firefox with --enable-system-cairo (but it's what I do).
Offline
Chrome's built-in pdf reader is far better than firefox's. It' s quite normal for me to encounter some poor rendered pdf with firefox built-in pdf reader.
Offline
@MilenKid: if you are using infinality-bundle, the settings in Xresources should look as follows:
Xft.dpi: 96
Xft.antialias: 1
Xft.rgba: rgb
Xft.autohint: 0
Xft.lcdfilter: lcddefault
Xft.hinting: 1
Xft.hintstyle: hintfullThis is not going to solve the problem, but should be tweaked anyway. Make sure Xresources is properly loaded when KDE starts up. Check also if /etc/profile/infinality-settings.sh is present in your system in its most recent version: it should provide necessary Xft settings even if you don't have a local copy of Xresources.
You haven't provided your font settings found in KDE control panel, but I guess they may differ from the bundle's defaults. You should set the following (I can't remember which exactly are available in KDE -- use those that apply):
rgba => rgb
hinting => slight
antialias => true
lcdfilter => lcddefaultFrom what I can tell, you must have somewhere antialiasing disabled (are there any fontconfig files in your ~/.config/fontconfig or ~/.fonts.conf?) or a bitmap serif font is used despite the fc-match output. Check your fontconfig configuration, both global and local, for files that may contain instructions causing such behaviour.
Chrome's built-in pdf reader is far better than firefox's. It' s quite normal for me to encounter some poor rendered pdf with firefox built-in pdf reader.
Well, this is not true, not to the extent of the OP's problem at least. What's happening in his case has nothing to do with FF's pdf solution, which generally works very well and doesn't produce that sort of output by default…
Last edited by bohoomil (2013-05-17 18:51:10)
:: Registered Linux User No. 223384
:: github
:: infinality-bundle+fonts: good looking fonts made easy
Offline