168940 - font list imcomplete

Status: RESOLVED WORKSFORME

(Core Graveyard :: GFX: Gtk, defect)

Description

[giorgio]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826

hi. problem with mozilla 1.1 on suse linux 8 kde 3.02. the installed true type
fonts are aveilable for every application both in kde and in xwindows but in
mozilla the list of fonts is complete on setup but every time I run mozilla I
find more than half of them missing (while still installed on other applications
as openoffice) . The missing one are the microsoft fonts such as verdana and
unicode forms as arial . the fact is that my fonts all are installed in the same
directory and are fisically present on the directory oitsel but not in the list
of mozilla. The problem is with version 1.1 but not in the previous. Now I try
1.2 alpha

Reproducible: Always

Steps to Reproduce:
1.install mozilla 1.1
2.run mozilla
3.shut computer and try runnin mozilla again


Actual Results:  
4. the list of fonts is incomplete and the missing ones are the most used by me
such as unicode arial

Expected Results:  
5. show the complete list as available at the same moment in other application
as openoffice

Comment 1

[Andrew Schultz]

==> Intl

Comment 2

[Malcolm Scott]

Confirming, Linux 2002091016 (1.2alpha). Also occured in 1.1 .

Comment 3

[Roy Yokoyama]

to shanjian

Comment 4

[giorgio]

Hi. I'm giorgio , the reporter of the bug. I notice that every time I log on as
rott for some reason and then run as users the bug comes back. Hope It's helpful.

Comment 5

[Asa Dotzler [:asa]]

*** Bug 178143 has been marked as a duplicate of this bug. ***

Comment 6

[Asa Dotzler [:asa]]

*** Bug 227281 has been marked as a duplicate of this bug. ***

Comment 7

[Asa Dotzler [:asa]]

*** Bug 185497 has been marked as a duplicate of this bug. ***

Comment 8

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Are the fonts available in other Gtk apps?

Comment 9

[Jungshik Shin]

reporter, where are you looking for fonts? Do they show up in the list of fonts
returned by 'xlsfonts'? You filed this bug against 1.0/1.1 (which is X11core
font builds). In X11core font builds (still the default build available from
ftp.mozilla.org), fonts have to be available via Xserver/X font server.
Otherwise, Mozilla couldn't use them. 

Comment 10

[Tom]

I don't have any problems with the latest Mozilla nightly (2004020308). My
problem is with Firebird and Gnome/GTK font lists coming up short. As I see it,
Mozilla has its own way of picking fonts (which lists the font that I want to
use). Firebird uses the same method of selecting fonts that Gnome/GTK uses
(which for me comes up short). I think for me that the problem is with
Gnome/GTK's font selection process, which appears to create a sublist of the
available fonts based on what it thinks are the best fonts to use. There is
probably a way to change how Gnome/GTK chooses which fonts to display for
selection but I haven't figured it out yet.

Comment 11

[Tom]

(In reply to comment #10)
> I don't have any problems with the latest Mozilla nightly (2004020308). My
> problem is with Firebird and Gnome/GTK font lists coming up short. As I see it,
> Mozilla has its own way of picking fonts (which lists the font that I want to
> use). Firebird uses the same method of selecting fonts that Gnome/GTK uses
> (which for me comes up short). I think for me that the problem is with
> Gnome/GTK's font selection process, which appears to create a sublist of the
> available fonts based on what it thinks are the best fonts to use. There is
> probably a way to change how Gnome/GTK chooses which fonts to display for
> selection but I haven't figured it out yet.

Using the GTK1 builds of the Mozilla suite, a user.js contributed by Roland
Mainz that enabled anti-aliasing and the Microsoft fonts I was able to get fonts
that IMO had *The Right Look*. Until now, I've never been able to get *The Right
Look* in any GTK2 build and the differences between the font selection
mechanisms in the GTK1 and GTK2 builds were a source of unending confusion and
frustration.

As it turns out all along the problem was a misconfigured Fontconfig package.
The configuration script for the Debian Fontconfig package recommends using
"Native" hinting for the Microsoft and Vera fonts, "Auto hinting" for other
truetype fonts and "No Hinting" if you want the fuzzy look. When I initially
upgraded to GTK2 and had to configure Fontconfig for the first time I followed
the suggestion to use "Native" hinting which on my box makes the Microsoft fonts
look downright evil at certain point sizes. Because of the differences in
hinting I could in fact be using the exact same Microsoft font in both the GTK1
and GTK2 builds and never know it because the fonts would be named differently
and look so radically different (no hinting in GTK1 vs. bad hinting in GTK2).

To get (for me) *The Right Look* in GTK2 builds (and in all other GTK2 apps) I
had to do the following:

1. Put the Microsoft fonts in ~/.fonts
2. Run fc-cache

This ensures that when you select "Arial" or "Times New Roman" in the GTK2 font
selection dialog you are selecting the Microsoft version of the font and not
some **** free font of the same name that you might have somewhere else on the
system. Apparently Fontconfig gives priority to whatever you have in the
~/.fonts directory.

3. Run "dpkg-reconfigure fontconfig" as root and select "No Hinting" instead of
"Native Hinting". (Note: Many people may prefer "Auto-Hinting" over "No Hinting"
- this is a matter of personal preference.) I would also highly recommend
disabling bit-mapped fonts.

I'm not sure if this addresses the original reporter's issue but for my problems
with GTK2 builds at least it now works for me.

Comment 12

[Mats Palmgren (inactive)]

Is this bug reproducible in a recent trunk build?
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

Comment 13

[Mats Palmgren (inactive)]

-> WORKSFORME