258750 - Poor rendering of japanese text with utf-8 encoding when no font-family is specified

Status: RESOLVED DUPLICATE of bug 175651

(Camino Graveyard :: Preferences, defect)

Description

[philippe (part-time)]

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

see : http://dev.l-c-n.com/Gecko/Camino_japanese_utf-8.php
When an (xhtml) page is served as utf-8, Camino cannot render the Japanese text
correctly, unless a (Japanese) font-family is specified in the stylesheet. 

The test page shows 3 blocks of text; the first one renders incorrectly (no
font-family specified, except 'sans-serif'), the second and third one have a
font-family specified and render correctly.
OS X 10.3.5, but happened on previous Panter releases

This happens even if I set all font-preferences (unicode) to Hiragino.

Reproducible: Always
Steps to Reproduce:
1.see description
2.
3.

Actual Results:  
Incorrect rendering of Japanese text; the kanjis are decent, the kanas... pooh.

Expected Results:  
Render Japanese text decently, even if no font-family is specified.

Comment 1

[Mike Pinkerton (not reading bugmail)]

looks exactly the same to me in firefox. dont' think it's camino specific. that
said, the no-font-family looks the same, just a bit lighter.

am i missing something?

Comment 2

[philippe (part-time)]

Attachment: screenshot from the test page

Top part shos the poor rendering, bottom part show rendering with Osaka font
specified.

Comment 3

[philippe (part-time)]

(In reply to comment #1)
> looks exactly the same to me in firefox. dont' think it's camino specific. that
> said, the no-font-family looks the same, just a bit lighter.

Firefox, and Mozilla render everything correctly, but Camino does not.

Comment 4

[Mike Pinkerton (not reading bugmail)]

i see what you mean now (in the screenshot), but i don't see that kind of
discrepancy on a stock us system. looks fine to me, only lighter.

Comment 5

[philippe (part-time)]

Oops, wait a minute. I logged as another user (which never used Camino),
creating a new profile for Camino... Then the japanese text renders correctly
indeed. It never occured to me that something might be corrupted in my Camino
profile, although there is nothing fancy or special in there. I only use Camino
for testing pages under development. Sorry for the spam.

Comment 6

[Mike Pinkerton (not reading bugmail)]

would be helpful to know what pref in your profile caused this difference.

Comment 7

[philippe (part-time)]

(In reply to comment #6)
> would be helpful to know what pref in your profile caused this difference.

I don't think it's the profile. When I first tested the file under a different
user (see #5), I hadn't set any preferences for Camino. I now just tested :
1/ test-user one is running OS X in English - setting the preferences for fonts
in Camino, for Japanese, it reports missing fonts (Hiragino... ?, they all there
and work fine in other browsers or apps.). I select the font to Hiragino
font-family, Kaku Gothic W3 (not yet going into the advanced tab). As soon as I
close the pref's window, my test-file displays incorrectly.
2/ test user two is running OS X in Japanese. Exactly the same problem; trying
with Osaka font gives same result. Clicking the advance button: the pull down
menu reports missing fonts, although I just set them (I think there are few bugs
noted about this).

(under both users, I compared the test file in Firefox (stock 0.9.3) and Safari,
both always render it correctly).

Hope this narrow down a bit the problem.

Comment 8

[Boris Zbarsky [:bzbarsky]]

Sounds like a Mac fonts bug, not a layout one....

Comment 9

[philippe (part-time)]

The problem is specific to Camino. As said before: no problems whith other
browsers (Gecko or others), and no problems with any other application my system
when using Japanese fonts (daily working with Japanese texts).
The various Hiragino fonts appears particularly sensitive to this. Other Gecko
browsers have some problems with these fonts as well (bug 240841 and many
others), but Camino appears more sensitive - it doesn't even recognize those
fonts as preferences (I'll attach a screeenshot).

Note - as a developper I can easily solve that main problem by specifying a
font-family in the stylesheet.

Comment 10

[philippe (part-time)]

Attachment: Camino font-preferences

Preferences > Appearance > Fonts > Japanese
With a brand new profile.

Comment 11

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

The behavior in comment 7 is definitely bug 175651 (see bug 175651 comment 17;
when Camino's font prefs show "missing" for Asian fonts, the correct font is
used.  When the user corrects the "missing" fonts, Gecko/Gfx:Mac doesn't know
which font to use.)

As far as I can tell, comment 7 sums up this bug, so it's a dupe.  There are
other serious i18n bugs/holes in Gfx:Mac, but this doesn't look like one of them.

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

Comment 12

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

philippe, do you happen to still have that testcase sitting around?  If so, could you attach it here?

Comment 13

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Oops, moving this back to Camino since it was a Camino bug; sorry for the extra bugspam.