130465 - FreeType rendered fonts are all bold

Status: VERIFIED DUPLICATE of bug 130661

(Core :: Internationalization, defect)

Description

[Olivier Crête]

When I try to render a page that has standard, bold and italic text, the whole
thing is rendered bold. Using the same font with gdkxft and non-aa gives correct
results. The font is Verdana.

I'm attaching a screenshot that contains the following html code:
standard <b>bold</b> <i>italic</i>

Comment 1

[Olivier Crête]

Attachment: Screenshot of the error

Screenshot of the rendering of:
standard <b>bold</b> <i>italic</i>

Comment 2

[Nicolás Lichtmaier]

I see something similar. When turning on FreeType support I see every thing
plain, no-bold, no-italic. I don't think this is a i18n issue, I've tried to
change it to Layout but I haven't go the bugzilla power to do that.. =)

Comment 3

[Iuri Fiedoruk]

I see this too.
Using freetype2, XFree 3.3.6 and build 2002031121 on Redhat 7.1.

Comment 4

[Mihai Bazon]

It happens to me too...  Too bad, because I was looking forward to see
antialiased fonts in Mozilla for a looong time now.

Anyway, just delete the bold fonts and you have regular :)  I still like it... 
But it should be fixed.

Comment 5

[Jens Lautenbacher]

*** This bug has been confirmed by popular vote. ***

Comment 6

[Roy Yokoyama]

-> shanjian, cc'ing bstell

Comment 7

[Shanjian Li]

accept. 

Comment 8

[Mihai Bazon]

Another strange thing -- maybe will help fixing..
If you rename the font files you might get different results.  E.g., I kinda
like the font Verdana.  It has 4 files:
  verdana.ttf (regular)
  verdanab.ttf (bold)
  verdanai.ttf (italic)
  verdanaz.ttf (bold italic, I suppose)
With the default names, Mozilla only shows Bold.

Renaming them like this:
  verdana.ttf (regular)                   --> verdana0.ttf
  verdanab.ttf (bold)                     --> verdana1.ttf
  verdanai.ttf (italic)                   --> verdana2.ttf
  verdanaz.ttf (bold italic, I suppose)   --> verdana3.ttf
Shows only regular font to me... :)  Of course, you must delete ~/.mozilla/fonts
and restart Mozilla to make sure the changes take effect.

Comment 9

[Iuri Fiedoruk]

I think this is a bug too much oustanding and strange to a newbie user to be
marked as 1.1 target. IMHO it should be marked as 1.0 or this feature should be
removed from 1.0, it dosen't even have a configure dialog yet.
My vote: fix, or remove for now.

Comment 10

[mreimer]

You probably have your preferences out-of-sync with the way FreeType was
compiled on your system. Try changing "font.FreeType2.unhinted" from true to
false and see if that helps; it fixes it for me.

Comment 11

[Iuri Fiedoruk]

Yes! This fixes the problem for my.
Now the questions: shouldn't this be false by defalt?
I mean, when you don't put "font.FreeType2.unhinted" on prefs, it should not be
set to false instead of true?
Shouldn't this too be on the directions on mozilla 0.9.9 release notes too?

I hope someone one day writes a doc with all those wonderfull and hidden
preferences of mozilla.

Comment 12

[Nicolás Lichtmaier]

This is important because this is cited as one of the major enhancements in the
new release. Either this should be fixed or the release notes should be
corrected withdrawing the mention of this feature.

Comment 13

[Nicolás Lichtmaier]

It doesn't work for me.

This is now my user.js:
pref("font.FreeType2.unhinted", false);
pref("font.FreeType2.enable", true);
pref("font.directory.truetype.1", "/usr/share/fonts/truetype");

And this is what happens:
http://mazinger.technisys.com.ar/pruebas-nick/font-test.html

Comment 14

[Iuri Fiedoruk]

Attachment: Same url, testing here

user_pref("font.FreeType2.enable", true);
user_pref("font.FreeType2.unhinted", false);
user_pref("font.directory.truetype.1", "/usr/share/fonts/truetype");

Same url, build 2002031121 - maybe this options is post-0.9.9?

Comment 15

[Nicolás Lichtmaier]

It works, but I guess you haven't changed your fonts to the freetype ones. The
characters aren't antialiased, while in my example they are.

Comment 16

[Iuri Fiedoruk]

Yeah, sorry I was in a rush (did I said mysql sucks?).
Anyway, I still get bold fonts, but much better with the
user_pref("font.FreeType2.unhinted", false);
option.

Comment 17

[Vadim Berezniker]

I don't get bold fonts in either case. It remains normal.

putting 
"window, menu, menuitem, toolbarbutton{font-family: sans-serif !important;
font-size: 12pt !important}" in userChrome.css adds anti-aliasing to almost
everything but the problem is that in MailNews you don't see any of the bold
which makes it hard to use.

Comment 18

[Olivier Crête]

From what I can see.. we can get all bold or no bold... Either case, its quite a
big bug... I've abandonned direct freetype use and I switched to blizzard's Xft
patch, it already works much better... 
Shouldn't this be added to the 0.9.9 RelNotes?

Comment 19

[kill this account]

-> bstell

Comment 20

[kill this account]

*** This bug has been marked as a duplicate of 130661 ***

Comment 21

[Yuying Long]

Verified as dup.