Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Japanese fonts use fake bold font instead of the according real bold fonts



Core Graveyard
GFX: Mac
12 years ago
9 years ago


(Reporter: Kilian Muster, Unassigned)


Mac OS X

Firefox Tracking Flags

(Not tracked)




(1 attachment)



12 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050522 Camino/0.8+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050522 Camino/0.8+

<b> and <strong> tags etc. in Japanese text are rendered using "fake" bold (the
text is copied 4 times in 4 directions) this gives the font a very smudged look,
which makes the Japanese rather unreadable, because of its thin lines. It would
be much more appropriate to have Camino use an according Japanese font to
display the bolded characters..

This has to do with a specific issue with Japanese fonts, since in most cases a
"bold" font is not considered being a bold variation of one "normal" font, but
appears in the font panel as a separate font. Therefore the "bold version" of
e.g. "Hiragino Kaku Gothic Pro W3" would be "Hiragino Kaku Gothic Pro W6", and
accordingly the "bold version" of "Hiragino Mincho Pro W3" is "Hiragino Mincho
Pro W6".

Also Japanese fonts are displayed with Roman Names in OS X, so this has to be
considered when fixing this bug. The Japanese font names are only used when the
OS is switched to Japanese.

Reproducible: Always

Steps to Reproduce:
1. Open Japanese website, with bolded fonts
2. See how ugly it is
3. ?? profit ??

Actual Results:  
The Japanese bolded text was pretty hard to read and ugly.

For whatever reason, no profit.

Expected Results:  
Beatifully rendered fonts using the bolder W6 font instead of applying fake bold.
Does Firefox do the right thing?  I'm not qualified to tell if Firefox gets it
right or not.

I think I've seen a core bug about this subject, but it may well be the "use
ATSUI" bug, too.

Comment 2

12 years ago
(In reply to comment #1)
> Does Firefox do the right thing?  I'm not qualified to tell if Firefox gets it
> right or not.
> I think I've seen a core bug about this subject, but it may well be the "use
> ATSUI" bug, too.

Actually Firefox doesn't render bolded Japanese text properly either.

Comment 3

12 years ago
Created attachment 184320 [details]
blurriness on

This is not just a problem with Japanese fonts.  I've been getting this on too, although I've been told that it looks worse on my powerbook
compared to other screens.
In bug 972(!) Greg K indicates that support for real bold variations needs
ATSUI; leaving this a separate bug but making it depend on ATSUI.  Since this
affects Firefox, too, moving to Core.

I can't reproduce comment 3, but comment 0 seems pretty clear (fuzzy text!) to
me now.

Reporter, a couple of screenshots (Camino/Firefox and a browser that gets it
right (Safari?)) would be helpful, too.
Assignee: pinkerton → nobody
Component: Page Layout → Layout: Fonts and Text
Depends on: 121540
Ever confirmed: true
Product: Camino → Core
QA Contact: layout.fonts-and-text
Version: unspecified → Trunk

Comment 5

12 years ago
Doesn't sound like a layout problem, folks.
Assignee: nobody → joshmoz
Component: Layout: Fonts and Text → GFX: Mac
QA Contact: layout.fonts-and-text → mac

Comment 6

12 years ago
With Japanese fonts the issue is even more complex, because they usually don't have a "bold" font style as part of one font file. The most common way of distinguishing the "boldness" of a Japanese font is the ending of the font name. So e.g. "Hiragino Kaku Gothic W3" would be a regular font and "Hiragino Kaku Gothic W6" would be bold.

I am not a programmer, but I do have the feeling that there must be some Cocoa hooks for doing the bolding just right without really thinking about the font name. Safari e.g. does it properly and all other Cocoa apps I know as well (not only browsers). When you switch your environment to Japanese in OS X some of the Japanese font names do change their name to something in Japanese, so the recognition whether a Japanese font is bold or not is not in the actual name, I guess.
*** Bug 326059 has been marked as a duplicate of this bug. ***
This isn't just an issue with Japanese fonts, but with any font in which the individual styles are installed as separate font files.

I have Bitstream Vera installed as individual TTF files (vera.ttf, verab.ttf, etc.) rather than as a Mac-native suitcase, and the Carbon API sees it as four separate families rather than four styles of the same family (and thus uses artificially generated bold, italic, etc.)  This behavior can also be seen, for instance, in MS Word.


10 years ago
Assignee: joshmoz → nobody
This should be WFM on the trunk now (and if it's not, it needs to be moved to Gfx:Thebes).

Comment 10

10 years ago
Yeah, the Japanese fonts (Hiragino Kaku Gothic and Hiragino Mincho) now use the real bold face (Cairo + atsui). And the code for synthesising bold/italics for those fonts that lack bold/italic faces has been extensively rewritten (in bug 364713).

If there are fonts that still have display issues on Gecko 1.9, new bugs should be filed.

--> WFM
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME


9 years ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.