264176 - Unicode font substitution for japanese text does not work - regression in 1.7.3

Status: RESOLVED WORKSFORME

(Core :: Layout: Text and Fonts, defect)

Description

[Marc Jackisch]

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

When a stylesheet demands a font, that does not contain certain characters,
substitution with a "better" font does not work anymore. This was well in 1.7b.

Reproducible: Always
Steps to Reproduce:
Call the page shown as example.
Actual Results:  
Line 2 shows squares instead of Japanese characters, because the div has the
(very common) font-family set of "Verdana, Arial, Helvetica, sans-serif". Line 4
does not have such a definition and shows the characters correctly.

Expected Results:  
Both lines (2 and 4) should display the correct characters. (Note once more:
this worked with mozilla 1.7b)

Severity filed as "normal" - who needs mixed pages anyway? Unfortunately, a
blocker for me personally. :(

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Tony Mechelynck [:tonymec]]

www.online-club.de times out (and yet my modem is connected), so I cannot check the testcase. It would be nice if a good (and short) testcase could be added as an attachment to the bug.

IIRC, the GTK2 font interface can choose glyphs from other fonts than those mentioned if none of the fonts mentioned has a glyph for the desired codepoint.

Is anyone seeing this bug which a current build (and which one)? Mine is:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008060101 SeaMonkey/2.0a1pre

Comment 3

[Simon Montagu :smontagu]

Attachment: Possible testcase

This is an attempt to reconstruct a testcase from the description in comment 0. However, I think a Linux font bug reported in 2004 and not confirmed since is very unlikely to have any relevance to the current code base and we should probably just WONTFIX this.

Comment 4

[Tony Mechelynck [:tonymec]]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008060101 SeaMonkey/2.0a1pre

WFM -- I see the Japanese text on both lines of attachment #323341 [details] as identical.

Comment 5

[Matthias Versen [:Matti]]

marking wfm based on the last comment