Build ID: 2001-06-05 FizzillaCFM
Steps to reproduce:
1) Create a new profile if necessary
2) Take a look at the East Asian font prefs
Fizzilla defaults to Mac OS 8.x/9.x era fonts.
Expected Fizzilla to default to the new fonts that Apple is shipping with Mac OS
X when it makes sense to use the new fonts.
For example, in the Japanese prefs Osaka is the default for serif, sans-serif
and cursive. It might be better to use Hiragino Mincho Pro W3 for serif &
cursive and to use Hiragino Kaku Gothic Pro W3 for sans-serif.
Disclaimer: I can't actually read these languages, so there is a chance I am
missing the point.
OSX related bug. Reassign to nhotta.
We need more study about this before do anything.
Keep this bug as no target for now.
mark as moz0.9.3
move to m94 and ftang
Is the 0.9.4 milestone realistic? We are branching on Friday.
no, move to 95
dear nhotta- can you do some research on this ?
I know pierre once try to put the multiple default font name fallback ont omac
from our window code which shanjian wrote, I am not sure it's done or not. maybe
we can use that facility for this.
Multiple default fonts are decribed under bug 71539 which covers the
implementation on the Mac of bug 61883.
reassign back to ftang:
got answer from firstname.lastname@example.org
Here are the answers to the font questions you asked me:
For Japanese it would be: "ƒqƒ‰ƒMƒm–¾’© Pro W3", "ƒqƒ‰ƒMƒmŠpƒS Pro W3",
"Osaka-“™•�", "ƒqƒ‰ƒMƒmŠÛƒS Pro W4", "ƒqƒ‰ƒMƒmŠÛƒS Pro W4". Note, it is much
better if they can use font fallback like the system does, e.g. use Western
set of fonts for Latin characters.
Cyrillic fonts have been renamed to: "Times CY" "Helvetica CY" "Monaco CY"
Turkish is a Roman variant covered by our Western script fonts.
i.e. Western "Times" "Helvetica" "Courier" "Apple Chancery" "Gadget"
Apple Chancery and Gadget are not shipped on OSX.
For OSX the same fonts are available on the menu or an updated set could be
Don't have info on Baltic but assume same as Turkish if it is latin script.
Which languages does baltic cover?
Your Thai is OK, though we may add/change the fonts for Thai in OSX.
Arabic would be "AB Geeza" "AB AlBayan" "AB Baghdad" "AB Kufi" "AB Nadeem"
Though I'm not certain of the style matches.
switch your brwoser to shift jis to see the previous comment
to implement this, we probably need a fallback default font mechanism as what we
have in window.
There is a dependency on bug 71539 already.
bug 71539 is MORE than what we really need to depend on. We really need A
fallback default font solution, but 71539 include other platform and pref UI. We
need to break down dependency , instead of build UP dependency.
move to 0.9.8
mass move unimportant m9.8 bug to m9.9 for now.
give this to nhotta and m1.0
nsbeta1+ per triage meeting
Remove depends for bug 71539.
My current plan for nsbeta1 is to change the names to "Hiragano" for Japaense.
For OS9, the default "Osaka" is used. I can also change Chinese and Korean fonts
if we know the font names.
New Japanese fonts for MacOS X.
Hiragino Mincho Pro W3
Hiragino Mincho Pro W6
Hiragino Kaku Gothic Pro W3
Hiragino Kaku Gothic Pro W6
Hiragino Kaku Gothic Std W8
The current default for MacOS X is Osaka (for both serif and sans serif), this
is because we set defaults for MacOS 9 fonts which are not included in MacOS X.
I tried the new fonts and I actually prefer Osaka. It is more legible than
Mincho and Gothic.
Cc to momoi, I think he did a research about the default font before.
Created attachment 73766 [details]
Screen shot Netscape JA home page with "Osaka" set as Japanese font.
Created attachment 73767 [details]
Screen shot Netscape JA home page with "Hiragino Mincho Pro W3" set as Japanese font.
Created attachment 73769 [details]
Screen shot Netscape JA home page with "Hiragino Kaku Gothic Pro W3" set as Japanese font.
So I think the current font "Osaka" is fine for the MacOS X default.
removing nsbeta+ to triage again
nsbeta1- per i18n triage
Considering bug's current status removing as a blocker for 102998
> So I think the current font "Osaka" is fine for the MacOS X default.
I'm not qualified to comment on the readablility of Japanese fonts since I can't
read Japanese. However, shouldn't Mozilla have a serif font set as the Japanese
serif font and a sans-serif font as the Japanese sans-serif font? If all the
generic families map to Osaka, it defeats the purpose of having generic font
This issue is probably worth revisiting when Mozilla gets Quartz font
rasterization support, since that will have an impact on the exact look of fonts.
How about the Chinese and Korean defaults?
also defaults to Osaka in Mach-O 20030227
I can take it, if someone will attach the needed changes (what font for what
category for what language...).
Jshin, any word here (comment 29)?
Created attachment 168059 [details]
Gecko charsets/locales styled with CSS fonts
The Japanese changes (comment 9) seem to have been made some time ago.
However, I'm not sure they (nor any of the Chinese or Korean fonts) are working
properly (bug 246527)?
The "copy-paste from the attached webpage into TextEdit" test reveals different
fonts being used in reality in certain cases (JP.mono, Ko.serif, Simplified and
Traditional). "Fallback" to the OS default seems to be working in this test
(everything appears to be displayed), so it may not be anything to worry about
until bug 246527 gets fixed.
Created attachment 177346 [details]
Gecko charsets/locales styled with CSS fonts (revised/corrected by jshin)
jshin fixed some errors in my test page over in bug 159809.
I *think* this bug should be resolved by the patch under review in bug 159809.
(In reply to comment #31)
> The "copy-paste from the attached webpage into TextEdit" test reveals different
> fonts being used in reality in certain cases (JP.mono, Ko.serif, Simplified and
That is because we can't copy styled text out of Gecko. So, as far as I can
tell, this bug is fixed (and has been for some time, pre-bug 159809).