---------- Original Message ----------------------------------
From: "Paul W. Abrahams"
On my (KDE) desktop, the Firefox browser shows up with a tiny font for the top-line menu (File, Edit, View, etc.) The control for that font appears to be neither in Firefox itself nor in the KDE control center. I'm guessing that it's somewhere in the X configuration. Can anyone tell me how to make that font bigger (or to change it to a different font)?
Paul
Paul, I am also new to Suse 10 and had a similar problem, only with page content. In my situation the font size in INPUT boxes were too large and the font size in TEXTAREA boxes were too small. I fixed this by creating a userContent.css file as intructed here... http://www.mozilla.org/unix/customizing.html The above page also talks about using userChrome.css to modify the user interface fonts, etc. It also discusses display problems in Linux. Hope this helps. Matt
On Saturday 12 November 2005 6:40 am, Matt Stamm wrote:
I am also new to Suse 10 and had a similar problem, only with page content.
In my situation the font size in INPUT boxes were too large and the font size in TEXTAREA boxes were too small. I fixed this by creating a userContent.css file as intructed here...
http://www.mozilla.org/unix/customizing.html
The above page also talks about using userChrome.css to modify the user
interface fonts, etc. It also discusses display problems in Linux. Oddly, that page says nothing about the gnome-control-center method of controlling fonts in Mozilla, nor does it even say that Mozilla relies on Gnome for font control (and other stuff too, I presume). Yet I found that if you have gnome-control-center available, it provides by far the simplest and most straightforward way of controlling the Mozilla/Firefox menu fonts and provides a way of choosing the face as well as the size (playing with DPI doesn't do that). I had a little difficulty in locating gnome-control-center on the distribution CD, because its package name doesn't contain the word "gnome". You need to search on " control center". Paul
Paul W. Abrahams wrote:
Oddly, that page says nothing about the gnome-control-center method of controlling fonts in Mozilla, nor does it even say that Mozilla relies on Gnome for font control (and other stuff too, I presume). Yet I found that if you have gnome-control-center available, it provides by far the simplest and most straightforward way of controlling the Mozilla/Firefox menu fonts and provides a way of choosing the face as well as the size (playing with DPI doesn't do that).
It says nothing about using gcc to control fonts in Mozilla because Mozilla depends on the GTKx desktop environment font settings (even when using KDE or other environments), which are not specific to Mozilla, but rather affect all GTKx apps. If you want to change the fonts only for Mozilla, you can't use gcc, unless Mozilla is the only GTKx app you have installed. Mozilla queries the environment for the CSS System Font "Menu", which is what it uses (both size and family for the main menu items) unless you override it with userChrome.css. -- "I can do all things through Him who gives me strength." Philippians 4:13 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/auth/
On Saturday 12 November 2005 01:51 pm, Felix Miata wrote:
Paul W. Abrahams wrote:
It says nothing about using gcc to control fonts in Mozilla because Mozilla depends on the GTKx desktop environment font settings (even when using KDE or other environments), which are not specific to Mozilla, but rather affect all GTKx apps. If you want to change the fonts only for Mozilla, you can't use gcc, unless Mozilla is the only GTKx app you have installed. Mozilla queries the environment for the CSS System Font "Menu", which is what it uses (both size and family for the main menu items) unless you override it with userChrome.css.
Is that true of the Mozilla distributed on mozilla.org? I know that to build Mozilla, I need some parts of the Gtk development environment. Quite honestly, I don't like the builds with Gtk2 nearly as much as the traditional builds. The file widget lacks functionality which I expect from a GUI. Fonts in Mozilla have always been a bit weird. The latest combination of SuSE 10 and Mozilla produced some, shall we say, unusual results. Here's the photographic evidence: https://bugzilla.novell.com/attachment.cgi?id=56426&action=view Here's the story: https://bugzilla.novell.com/show_bug.cgi?id=132047 Steven
Steven T. Hatton wrote:
On Saturday 12 November 2005 01:51 pm, Felix Miata wrote:
It says nothing about using gcc to control fonts in Mozilla because Mozilla depends on the GTKx desktop environment font settings (even when using KDE or other environments), which are not specific to Mozilla, but rather affect all GTKx apps. If you want to change the fonts only for Mozilla, you can't use gcc, unless Mozilla is the only GTKx app you have installed. Mozilla queries the environment for the CSS System Font "Menu", which is what it uses (both size and family for the main menu items) unless you override it with userChrome.css.
Note that above I was writing about UI fonts. AFAICT, the UI toolkit selected to build Moz does not affect web page font rendering, but there are other available build options that can, such as MathML.
Is that true of the Mozilla distributed on mozilla.org?
That's where it comes from. All the various distros are free to diddle as they see fit, but I'm not aware that SuSE makes any attempt to deviate from the official build configuration as to UI font handling. about:buildconfig in the address window will tell you the build options for whatever you are running that was built within the past 3 or so years.
I know that to build Mozilla, I need some parts of the Gtk development environment. Quite honestly, I don't like the builds with Gtk2 nearly as much as the traditional builds. The file widget lacks functionality which I expect from a GUI.
Official builds of Mozilla and SeaMonkey come in two flavors, GTK1 & GTK2. Firefox and TB only come in GTK2. Up through the 1.7 line (Mozilla), the primary configuration was GTK1. Beginning with 1.8 (SeaMonkey 1.0), the primary is GTK2. IIRC, SuSE switched to using the GTK2 toolkit for its RPMs back around v8.2, as did RedHat and Mandrake about the same time. Mozilla has a relatively new QT build configuration, but I have no knowledge that any publicly available builds using it have ever happened. -- "I can do all things through Him who gives me strength." Philippians 4:13 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
In an earlier post in this thread I noted that I've used gnome-control-center to change the font size for the Firefox menu bar to a larger value. I much prefer this method over fiddling with the DPI for two reasons: it's more flexible (allows changing the font face also) and simpler. It's also simpler than learning about Chrome.css, which I wouldn't need for any other purpose. The only problem is that the change doesn't stick, I've discovered. Once I log out, the effect is lost, and I have to repeat the operation on each login. (My previous choice is remembered by gnome-control-center, however.) So is there a way to either make the choice stick or to recreate it automatically as part of ~/.xinitrc? Someone mentioned gnome-settings-daemon, but I can't locate it in the 10.0 distribution. Maybe it's there, but in what package? And by the way, the KDE control center does not affect the Firefox menu font at all. Paul
On Sunday 13 November 2005 10:51 pm, Paul W. Abrahams wrote:
In an earlier post in this thread I noted that I've used gnome-control-center to change the font size for the Firefox menu bar to a larger value. I much prefer this method over fiddling with the DPI for two reasons: it's more flexible (allows changing the font face also) and simpler. It's also simpler than learning about Chrome.css, which I wouldn't need for any other purpose.
The only problem is that the change doesn't stick, I've discovered. Once I log out, the effect is lost, and I have to repeat the operation on each login. (My previous choice is remembered by gnome-control-center, however.) So is there a way to either make the choice stick or to recreate it automatically as part of ~/.xinitrc? Someone mentioned gnome-settings-daemon, but I can't locate it in the 10.0 distribution. Maybe it's there, but in what package?
And by the way, the KDE control center does not affect the Firefox menu font at all.
Paul
There is a save settings on exit "feature" of the GNOME, reminiscent of the bad old days of the CDE. If you are not setting this up while running a GNOME session, that may be the problem. Steven
On Sunday 13 November 2005 11:05 pm, Steven T. Hatton wrote:
There is a save settings on exit "feature" of the GNOME, reminiscent of the bad old days of the CDE. If you are not setting this up while running a GNOME session, that may be the problem.
I expect that it is. But since I'm running KDE, not Gnome, how can I get those settings to be preserved? Paul
On Monday 14 November 2005 00:10, Paul W. Abrahams wrote:
On Sunday 13 November 2005 11:05 pm, Steven T. Hatton wrote:
There is a save settings on exit "feature" of the GNOME, reminiscent of the bad old days of the CDE. If you are not setting this up while running a GNOME session, that may be the problem.
I expect that it is. But since I'm running KDE, not Gnome, how can I get those settings to be preserved?
I've been going through the same issues - I was led to the suggestion that the gnome-settings-daemon needed to be running, and suggestions to put that in autostart. That definitely worked, but caused endless other headaches due to some gnome settings stomping over my KDE settings(running a screensaver, affecting key-repeats). I'm convinced this is *not* the best way to deal with it. I'm still waiting for someone to suggest the "proper" way, if it exists...:P Cheers, J.C. -- John Coldrick www.axyzfx.com Axyz Animation 416-504-0425 425 Adelaide St W Toronto, ON Canada jc@axyzfx.com M5V 1S4 ----------------------------------------------------------------------- The earth is like a tiny grain of sand, only much, much heavier.
On Monday 14 November 2005 09:39 am, John Coldrick wrote:
I've been going through the same issues - I was led to the suggestion that the gnome-settings-daemon needed to be running, and suggestions to put that in autostart. That definitely worked, but caused endless other headaches due to some gnome settings stomping over my KDE settings(running a screensaver, affecting key-repeats). I'm convinced this is *not* the best way to deal with it. I'm still waiting for someone to suggest the "proper" way, if it exists...:P
Once upon a time there was an effort to create a common desktop configuration framework. I don't know if that is a healthy idea for either the GNOME or the KDE. Having independence to experiment without having to take compatability into account is a valuable freedom. OTOH, it would be nice if there were hooks in the KDE for GNOME settings, or in YaST? To be quite honest, I was looking at GNOME yesterday, and realized one of the things I don't like about it is that settings are applied immediately, and there is no "commit" mechanism. The current problem is an example of how the lack of such a commit mechanism causes problems. Steven
On Monday 14 November 2005 09:39 am, John Coldrick wrote:
I've been going through the same issues - I was led to the suggestion
the gnome-settings-daemon needed to be running, and suggestions to put
On Monday 14 November 2005 10:00 am, Steven T. Hatton wrote: that that
in autostart. That definitely worked, but caused endless other headaches due to some gnome settings stomping over my KDE settings(running a screensaver, affecting key-repeats). I'm convinced this is *not* the best way to deal with it. I'm still waiting for someone to suggest the "proper" way, if it exists...:P
Once upon a time there was an effort to create a common desktop configuration framework. I don't know if that is a healthy idea for either the GNOME or the KDE. Having independence to experiment without having to take compatability into account is a valuable freedom. OTOH, it would be nice if there were hooks in the KDE for GNOME settings, or in YaST? To be quite honest, I was looking at GNOME yesterday, and realized one of the things I don't like about it is that settings are applied immediately, and there is no "commit" mechanism. The current problem is an example of how the lack of such a commit mechanism causes problems.
An astute analysis -- but what can we peons do until the Messiah arrives? Does anyone have a suggestion as to how to apply the Gnome settings in a KDE environment without, as John notes, stomping all over the KDE settings? All I (and many others) want is to have the Gnome settings apply to Gnome-sensitive applications. And by the way, which package contains gnome-settings-daemon? Is it possible, perhaps, to run that daemon in a session before running the KDE controls so that the KDE controls will rule? Paul
On Monday 14 November 2005 11:07, Paul W. Abrahams wrote:
An astute analysis -- but what can we peons do until the Messiah arrives? Does anyone have a suggestion as to how to apply the Gnome settings in a KDE environment without, as John notes, stomping all over the KDE settings? All I (and many others) want is to have the Gnome settings apply to Gnome-sensitive applications.
I think the messiah is *supposed* to be gtk-qt-engines - it's just that it's busted and doesn't always work as advertised. It's supposed to run under KDE and handle GTK requests. That's my understanding, anyway, but I'm never able to get a clear answer on this, though. Their website is up and running, everyone acts like it works. Btw, do you have Gnome installed at all? I'm wondering if that's why it's causing problems? I realize there's a basic install that happens with SUSE regardless, but I chose to not install the full-up Gnome package. Perhaps there's a little thing in there that we're missing? Cheers, J.C. -- John Coldrick www.axyzfx.com Axyz Animation 416-504-0425 425 Adelaide St W Toronto, ON Canada jc@axyzfx.com M5V 1S4 ----------------------------------------------------------------------- The earth is like a tiny grain of sand, only much, much heavier.
On Monday 14 November 2005 11:17 am, John Coldrick wrote:
On Monday 14 November 2005 11:07, Paul W. Abrahams wrote:
An astute analysis -- but what can we peons do until the Messiah arrives? Does anyone have a suggestion as to how to apply the Gnome settings in a KDE environment without, as John notes, stomping all over the KDE settings? All I (and many others) want is to have the Gnome settings apply to Gnome-sensitive applications.
I think the messiah is *supposed* to be gtk-qt-engines - it's just that it's busted and doesn't always work as advertised. It's supposed to run under KDE and handle GTK requests. That's my understanding, anyway, but I'm never able to get a clear answer on this, though. Their website is up and running, everyone acts like it works. Btw, do you have Gnome installed at all? I'm wondering if that's why it's causing problems? I realize there's a basic install that happens with SUSE regardless, but I chose to not install the full-up Gnome package. Perhaps there's a little thing in there that we're missing?
Truth is, I'm not sure whether I have any Gnome components installed that aren't required by gcc (Gnome control center). [Too bad that gcc is an ambiguous abbreviation.] I didn't know which package had gcc and so I installed a bunch of Gnome packages in the hope of getting gcc. Perversely, gcc is in a package named control-center, and a Yast search on gnome doesn't turn it up. I have gtk-qt-engines installed, I just discovered, but how do I tell it to get to work? Paul
On Monday 14 November 2005 11:27, Paul W. Abrahams wrote:
Truth is, I'm not sure whether I have any Gnome components installed that aren't required by gcc (Gnome control center). [Too bad that gcc is an ambiguous abbreviation.] I didn't know which package had gcc and so I installed a bunch of Gnome packages in the hope of getting gcc. Perversely, gcc is in a package named control-center, and a Yast search on gnome doesn't turn it up. I have gtk-qt-engines installed, I just discovered, but how do I tell it to get to work?
It's with KDE, if it's installed, it's working. You apparently have to go out of your way to turn it off. The fact this thread even exists goes a long way towards showing something's obviously off with it. :) Cheers, J.C. -- John Coldrick www.axyzfx.com Axyz Animation 416-504-0425 425 Adelaide St W Toronto, ON Canada jc@axyzfx.com M5V 1S4 ----------------------------------------------------------------------- The earth is like a tiny grain of sand, only much, much heavier.
Steven T. Hatton wrote:
On Monday 14 November 2005 09:39 am, John Coldrick wrote:
I've been going through the same issues - I was led to the suggestion that the gnome-settings-daemon needed to be running, and suggestions to put that in autostart. That definitely worked, but caused endless other headaches due to some gnome settings stomping over my KDE settings(running a screensaver, affecting key-repeats). I'm convinced this is *not* the best way to deal with it. I'm still waiting for someone to suggest the "proper" way, if it exists...:P
Once upon a time there was an effort to create a common desktop configuration framework. I don't know if that is a healthy idea for either the GNOME or the KDE. Having independence to experiment without having to take compatability into account is a valuable freedom. OTOH, it would be nice if there were hooks in the KDE for GNOME settings, or in YaST? To be quite honest, I was looking at GNOME yesterday, and realized one of the things I don't like about it is that settings are applied immediately, and there is no "commit" mechanism. The current problem is an example of how the lack of such a commit mechanism causes problems.
Steven
Why should any desktop be allowed to walk over another desktop? If we allow users to pick which desktop they want, then more of this stuff should bee left for YAST. That means that maybe the desktop people have to keep their fingers out of it, or at least structure their desktop usage of things. We use fvwm for dual screen CAD workstation. This is not a workstation "appliance", it is an independent consulting engineering office-in-a-box. Accounting, correspondence, engineering calcs, online literature searches, photography stuff, time records, and production of CAD drawings for building construction. It just works out to have one 21" screen mostly running 1024x and the CAD screen on high resolution. Galeon displays on the CAD monitor. Firefox tends to be used on the 1024x monitor. Mostly anything set up with YAST just works under fvwm or Gnome or KDE. Gnome tends to walk on the others, as does KDE.
participants (6)
-
Felix Miata -
John Coldrick -
Matt Stamm -
Paul W. Abrahams -
Stanley Long -
Steven T. Hatton