merge 352097 352045 352194 thanks Hi everyone.
Basically, all your problems are related to font sizes since the switch to the pango backend. There are actually 2 different issues, one related to the pango support, and the other one related to the non-pango support. Before 1.5.dfsg+1.5.0.1-1, our firefox was built with pango support, but it was disabled at runtime, so that the xft/fontconfig backend was used. In this configuration, it seems the screen resolution parameter in the font preferences has no effect whatsoever. With the pango backend, on the other hand, changing the screen resolution changes both the resolution for the interface and for the rendered html page. Now this is the real problem, since a lot of web designers are assuming a screen resolution of either 72 or 96dpi, depending on the OS type. I'm not saying this is not stupid, it's just the way it is. That can make a change of the screen resolution setting painful for some websites. Anyways, to get things right, here is my workaround: set the screen resolution to "system settings" (or set browser.display.screen_resolution to 0 with about:config), and if you feel the web pages to be displayed with too small or too big fonts, change the font sizes, that setting doesn't have an influence on the interface. I haven't made my decision whether or not we should change this parameter by default yet, but I think I'll file a bug upstream about the "dpi setting should leave the interface alone" issue. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
