Closed Bug 233782 Opened 21 years ago Closed 19 years ago

Wrong font substituted for Japanese text

Categories

(Core :: Internationalization, defect)

Product:
Core
Component:
Internationalization
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED EXPIRED

People

(Reporter: needle, Assigned: smontagu)

Details

(Keywords: intl) 

User-Agent:       
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

Usually, Mac OS X running in Japanese works in the following way: When the font is set to 
Lucida Grande and the system encounters Japanese text, it automatically substitues the missing 
characters from those taken from the Japanese font "Hiragino Kaku Gothic Pro W3". For this reason, the 
default browser display font in Safari is set to Lucida Grande even when the OS primary language is set 
to Japanese, and it works fine. All other Mac OS X apps running in Japanese substitute fonts in the same 
way.

This is not the case with Firefox, however; When the browser display font is set to Lucida Grande and 
Japanese text is encountered, the Japanese text is substituted in a different, strange-looking font. I 
could not figure out which font it was, but I'm guessing it's some kind of Chinese or Korean font. This 
font looks VERY low-quality, with unbalanced characters and the Japanese equivalents of commas and 
periods in wrong places. It looks as if the designer of the font did not have a command of Japanese 
him/herself - practically unusable.

Reproducible: Always
Steps to Reproduce:
1. Open System Preferences.
2. Open "International" Preferences pane.
3. In the "Language" tab, add the Japanese language to the language list and drag it to the top of the 
list.
4. Log out and log in.
5. Start Firefox.
6. Open Firefox Preferences.
7. In the "General" section, push the "Fonts & Colors" section.
8. Set the fonts for Japanese to Lucida Grande.
9. Hit OK, leave the prefs and open a Japanese page.
Actual Results:  
The English text was displayed in Lucida Grande.
The Japanese text was displayed in a strange, low-quality font.

Expected Results:  
The English text should be displayed in Lucida Grande (As it was).
The Japanese text should be displayed in Hiragino Kaku Gothic Pro W3.
This is not only Firefox.
If this is not invalid, this depends on Bug 120913 and probably Bug 61883.
-> browser, intl
Assignee: firefox → smontagu
Component: General → Internationalization
Keywords: intl
Product: Firefox → Browser
QA Contact: amyy
Version: unspecified → Trunk
(In reply to comment #0)

> default browser display font in Safari is set to Lucida Grande even when the
OS primary language is set 
> to Japanese, and it works fine. All other Mac OS X apps running in Japanese
substitute fonts in the same 
> way.

Mozilla doesn't seem to take advantage of the system-provided font-substitution.
As other ports of Gfx, Gfx:Mac seems to use its own font substitution mechanism
which may not be as mature as found on other ports of Gfx.
 
> This is not the case with Firefox, however; When the browser display font is
set to Lucida Grande and 
> Japanese text is encountered, the Japanese text is substituted in a different,
strange-looking font. I 

As you guessed, that may be either a Korean or TC or SC font. What happens if
you explicitly specify 'lang'? The easiest way to do that is to begin your html
file with 

<html lang="ja"> 
instead of 

<html>   

I'll test it myself later today on Mac. 

Anyway, why would you want to set the default font for Japanse to 'Lucida
Grande' in the first place? 
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/

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.