The default bug view has changed. See this FAQ.

Fizzilla defaults to old CJK fonts (Osaka instead of Hiragino Pro)

RESOLVED WORKSFORME

Status

Core Graveyard
GFX: Mac
P4
enhancement
RESOLVED WORKSFORME
16 years ago
8 years ago

People

(Reporter: hsivonen, Assigned: Simon Fraser)

Tracking

({intl})

Trunk
Future
PowerPC
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(4 attachments, 1 obsolete attachment)

(Reporter)

Description

16 years ago
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

Actual results:
Fizzilla defaults to Mac OS 8.x/9.x era fonts.

Expected results:
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.

Comment 1

16 years ago
OSX related bug. Reassign to nhotta. 
We need more study about this before do anything. 
Keep this bug as no target for now. 
Assignee: ftang → nhotta
Whiteboard: [OSX]

Updated

16 years ago
QA Contact: andreasb → ylong

Comment 2

16 years ago
mark as moz0.9.3
Target Milestone: --- → mozilla0.9.3

Updated

16 years ago
Status: NEW → ASSIGNED

Updated

16 years ago
Target Milestone: mozilla0.9.3 → ---

Comment 3

16 years ago
move to m94 and ftang
Assignee: nhotta → ftang
Status: ASSIGNED → NEW
Target Milestone: --- → mozilla0.9.4

Comment 4

16 years ago
Is the 0.9.4 milestone realistic?  We are branching on Friday.

Comment 5

16 years ago
no, move to 95
Status: NEW → ASSIGNED
Target Milestone: mozilla0.9.4 → mozilla0.9.5

Comment 6

16 years ago
P4.
Priority: -- → P4

Updated

16 years ago
Blocks: 102998

Comment 7

16 years ago
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. 

cc pierre
Assignee: ftang → nhotta
Status: ASSIGNED → NEW

Updated

16 years ago
Target Milestone: mozilla0.9.5 → mozilla0.9.7

Updated

16 years ago
Blocks: 103669

Comment 8

16 years ago
Multiple default fonts are decribed under bug 71539 which covers the 
implementation on the Mac of bug 61883.
Depends on: 71539

Updated

16 years ago
Status: NEW → ASSIGNED

Comment 9

16 years ago
reassign back to ftang:
got answer from xavier@apple.com

Frank,

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
used.

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.

Comment 10

16 years ago
switch your brwoser to shift jis to see the previous comment
Assignee: nhotta → ftang
Status: ASSIGNED → NEW
Target Milestone: mozilla0.9.7 → mozilla0.9.6

Comment 11

16 years ago
to implement this, we probably need a fallback default font mechanism as what we 
have in window.
Status: NEW → ASSIGNED

Comment 12

16 years ago
There is a dependency on bug 71539 already.

Comment 13

16 years ago
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.

Updated

16 years ago
Target Milestone: mozilla0.9.6 → mozilla0.9.7

Comment 14

16 years ago
move to 0.9.8
Target Milestone: mozilla0.9.7 → mozilla0.9.8

Updated

15 years ago
Whiteboard: [OSX]

Comment 15

15 years ago
mass move unimportant m9.8 bug to m9.9 for now. 
Target Milestone: mozilla0.9.8 → mozilla0.9.9

Comment 16

15 years ago
give this to nhotta and m1.0
Assignee: ftang → nhotta
Status: ASSIGNED → NEW
Keywords: nsbeta1
Target Milestone: mozilla0.9.9 → mozilla1.0

Comment 17

15 years ago
nsbeta1+ per triage meeting 
Keywords: nsbeta1 → nsbeta1+

Comment 18

15 years ago
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.

Status: NEW → ASSIGNED

Updated

15 years ago
No longer depends on: 71539
Blocks: 127253

Comment 19

15 years ago
New Japanese fonts for MacOS X.
Serif:
Hiragino Mincho Pro W3
Hiragino Mincho Pro W6

Sans Serif:
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.

Updated

15 years ago
Keywords: intl

Comment 20

15 years ago
Created attachment 73766 [details]
Screen shot Netscape JA home page with "Osaka" set as Japanese font.

Comment 21

15 years ago
Created attachment 73767 [details]
Screen shot Netscape JA home page with "Hiragino Mincho Pro W3" set as Japanese font.

Comment 22

15 years ago
Created attachment 73769 [details]
Screen shot Netscape JA home page with "Hiragino Kaku Gothic Pro W3" set as Japanese font.

Comment 23

15 years ago
So I think the current font "Osaka" is fine for the MacOS X default.

Comment 24

15 years ago
removing nsbeta+ to triage again
Keywords: nsbeta1+ → nsbeta1

Comment 25

15 years ago
nsbeta1- per i18n triage
Keywords: nsbeta1 → nsbeta1-

Updated

15 years ago
Target Milestone: mozilla1.0 → Future

Comment 26

15 years ago
Considering bug's current status removing as a blocker for 102998 
No longer blocks: 102998

Updated

15 years ago
No longer blocks: 127253
(Reporter)

Comment 27

15 years ago
> 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
families.

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?

Comment 28

14 years ago
also defaults to Osaka in Mach-O 20030227
Severity: minor → enhancement
Summary: FizzillaCFM defaults to old CJK fonts → Fizzilla defaults to old CJK fonts (Osaka instead of Hiragino Pro)
I can take it, if someone will attach the needed changes (what font for what
category for what language...).
Assignee: nhottanscp → bugs.mano
Status: ASSIGNED → NEW
Component: Internationalization → Preferences
Keywords: nsbeta1-
Product: Browser → Seamonkey
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.
Assignee: bugs.mano → sfraser_bugs
Component: Preferences → GFX: Mac
Product: Mozilla Application Suite → Core
QA Contact: amyy → mac
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.
Attachment #168059 - Attachment is obsolete: true
(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
> Traditional).

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).
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.