Update Mac fonts

Update fonts on Mac:
- Get rid of Arial as default
- Update non-English font choices (based mostly on Mozilla's choices, <http://mxr.mozilla.org/seamonkey/source/modules/libpref/src/init/all.js>; cross-referenced with what's installed with the OS)

BUG=http://crbug.com/19135; http://crbug.com/20171
TEST=as in bugs

[Avi (use Gerrit), 2009-10-27 19:10:39]

Scope of CL widened. Please review.

[jungshik at Google, 2009-10-27 22:07:33]

For Indic languages and Hebrew, I think just using the common set (Courier,
Times, Helvetica) work well. Because font fallback on Mac OS X works well. 

Our font preference is global (across languages) while Mozilla's are
per-script/per-languageGroup. 


What I'm not sure of is CJK and Arabic. 

I'll be back soon.

http://codereview.chromium.org/335031/diff/3001/4018
File chrome/app/resources/locale_settings_gu.xtb (right):

http://codereview.chromium.org/335031/diff/3001/4018#newcode22
Line 22: <translation id="IDS_FIXED_FONT_FAMILY">Gujarati MT</translation>
This need some checking. (some of Mozilla settings are rather outdated. Also, it
has per-script/per-langGroup font settings while we just have global settings). 

I think we just have to use Courier, Times, Helvetica for all the Indic
languages.

http://codereview.chromium.org/335031/diff/3001/4046
File chrome/app/resources/locale_settings_he.xtb (right):

http://codereview.chromium.org/335031/diff/3001/4046#newcode22
Line 22: <translation id="IDS_FIXED_FONT_FAMILY">Courier New</translation>
Shouldn't this be Courier?

http://codereview.chromium.org/335031/diff/3001/4046#newcode24
Line 24: <translation id="IDS_SANS_SERIF_FONT_FAMILY">Arial Hebrew</translation>
Here again, just using the common set may work as well. (Courier, Times,
Helvetica)

http://codereview.chromium.org/335031/diff/3001/4047
File chrome/app/resources/locale_settings_hi.xtb (right):

http://codereview.chromium.org/335031/diff/3001/4047#newcode24
Line 24: <translation id="IDS_SANS_SERIF_FONT_FAMILY">Devanagari
MT</translation>
same as other Indic languages. common set would be better.

[Avi (use Gerrit), 2009-10-28 15:41:12]

In general, I'm OK with just letting font fallback happen, so for the Indics
I'll change that. Just a little explanation of my thoughts.

http://codereview.chromium.org/335031/diff/3001/4046
File chrome/app/resources/locale_settings_he.xtb (right):

http://codereview.chromium.org/335031/diff/3001/4046#newcode22
Line 22: <translation id="IDS_FIXED_FONT_FAMILY">Courier New</translation>
On 2009/10/27 22:07:33, Jungshik Shin wrote:
> Shouldn't this be Courier?

Turns out that on the Mac, Courier doesn't cover the code points of Hebrew but
Courier New does.

[jungshik at Google, 2009-10-28 17:56:15]

On 2009/10/28 15:41:12, Avi wrote:
> In general, I'm OK with just letting font fallback happen, so for the Indics
> I'll change that. Just a little explanation of my thoughts.
> 
> http://codereview.chromium.org/335031/diff/3001/4046
> File chrome/app/resources/locale_settings_he.xtb (right):
> 
> http://codereview.chromium.org/335031/diff/3001/4046#newcode22
> Line 22: <translation id="IDS_FIXED_FONT_FAMILY">Courier New</translation>
> On 2009/10/27 22:07:33, Jungshik Shin wrote:
> > Shouldn't this be Courier?
> 
> Turns out that on the Mac, Courier doesn't cover the code points of Hebrew but
> Courier New does.

You're right. I forgot about that. I guess the same is true of 'Times vs Times
New Roman' and 'Helvetica vs Arial' not just for Hebrew but also for some other
scripts/languages  ( http://www.microsoft.com/typography/fonts/macosx.htm and 
http://www.alanwood.net/unicode/hebrew.html ). 

Given that Mac OS X has TNR, Arial, Courier New out of the box (which I forgot
yesterday), I wonder which is better, (Times, Helvetica, Courier) or  ( Times
New Roman, Arial, Courier New.). Well, obviously, you think the former is better
Otherwise, you'd not have made a CL :-)

[jungshik at Google, 2009-10-28 17:57:56]

http://codereview.chromium.org/335031/diff/3004/3020
File chrome/app/resources/locale_settings_ru.xtb (right):

http://codereview.chromium.org/335031/diff/3004/3020#newcode22
Line 22: <translation id="IDS_FIXED_FONT_FAMILY">Monaco CY</translation>
Oh no. Please, don't use this and other old fonts (coming from Mac OS 9). Just
use either Times New Roman, Arial, Courier New . I guess Times, Helvetica and
Courier do not cover Cyrillic. 

The same is true of other Slavic languages that use Cyrillic.

[jungshik at Google, 2009-10-28 18:07:55]

On 2009/10/28 17:57:56, Jungshik Shin wrote:
> http://codereview.chromium.org/335031/diff/3004/3020
> File chrome/app/resources/locale_settings_ru.xtb (right):
> 
> http://codereview.chromium.org/335031/diff/3004/3020#newcode22
> Line 22: <translation id="IDS_FIXED_FONT_FAMILY">Monaco CY</translation>
> Oh no. Please, don't use this and other old fonts (coming from Mac OS 9). Just
> use either Times New Roman, Arial, Courier New . I guess Times, Helvetica and
> Courier do not cover Cyrillic. 
> 
> The same is true of other Slavic languages that use Cyrillic.

In addition, languages like Vietnamese and Polish also need TNR/Arial/Courier
New because they have much broader character repertoire than
Times/Helvetica/Courier and cover Latin letters not covered by (traditional)
Times/Helvetica/Courier (unless T/H/C were expanded significantly on OS X). 

Because our font pref (and WebCore's Settings) are 'global/pan-language' (as
opposed to per-script/per-langGroup) and font fallback work rather well on OS X
without UI-language-specific hints, I'm tempted to use TNR/Arial/Courier New for
all UI languages and only change fantasy and cursive to OS X specific fonts
(Papyrus and Apple Ch...).  

What would you say?

[Avi (use Gerrit), 2009-10-28 18:22:48]

On 2009/10/28 18:07:55, Jungshik Shin wrote:
> I'm tempted to use TNR/Arial/Courier New for
> all UI languages and only change fantasy and cursive to OS X specific fonts
> (Papyrus and Apple Ch...).  
> 
> What would you say?

I'd say that I'd highly prefer to use T/H/C rather than TNR/A/CN wherever
possible. The coverage of T/H/C is pretty impressive.

According to Font Book on 10.5 (our base), Times covers:

Afrikaans, Albanian, Azerbaijani, Basque, Belarusian, Bulgarian, Catalan,
Cornish, Croatian, Czech, Danish, Dutch, English, Esperanto, Estonian, Faroese,
Finnish, French, Galician, German, Greek, Hawaiian, Hungarian, Icelandic,
Indonesian, Irish, Italian, Kalaallisut, Kazakh, Latvian, Lithuanian,
Macedonian, Malay, Maltese, Manx, Norwegian Bokmål, Norwegian Nynorsk, Oromo,
Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovenian, Somali,
Spanish, Swahili, Swedish, Turkish, Ukrainian, Uzbek, Vietnamese, Welsh

Helvetica covers:

Afrikaans, Albanian, Azerbaijani, Basque, Belarusian, Bulgarian, Catalan,
Cornish, Croatian, Czech, Danish, Dutch, English, Esperanto, Estonian, Faroese,
Finnish, French, Galician, German, Greek, Hawaiian, Hungarian, Icelandic,
Indonesian, Irish, Italian, Kalaallisut, Kazakh, Latvian, Lithuanian,
Macedonian, Malay, Maltese, Manx, Norwegian Bokmål, Norwegian Nynorsk, Oromo,
Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovenian, Somali,
Spanish, Swahili, Swedish, Turkish, Ukrainian, Uzbek, Vietnamese, Welsh

Courier covers:

Afrikaans, Albanian, Azerbaijani, Basque, Catalan, Cornish, Croatian, Czech,
Danish, Dutch, English, Esperanto, Estonian, Faroese, Finnish, French, Galician,
German, Hawaiian, Hungarian, Icelandic, Indonesian, Irish, Italian, Kalaallisut,
Latvian, Lithuanian, Malay, Maltese, Manx, Norwegian Bokmål, Norwegian Nynorsk,
Oromo, Polish, Portuguese, Romanian, Slovak, Slovenian, Somali, Spanish,
Swahili, Swedish, Turkish, Vietnamese, Welsh

What languages do TNR/A/CN cover that T/H/C don't? On 10.5, none. On 10.6, the
default installs of TNR/A/CN have a few more languages:

Arabic, Hebrew, Pashto, Persian, Urdu

I'm willing to swap in TNR/A/CN for those regions, but for the others T/H/C is
more than capable.

[Avi (use Gerrit), 2009-10-28 18:27:54]

OTOH, for CJK, I think we should use the dedicated fonts there rather than
fallback since AFAIK that's what users expect there.

[jungshik at Google, 2009-10-29 21:15:26]

On 2009/10/28 18:27:54, Avi wrote:
> OTOH, for CJK, I think we should use the dedicated fonts there rather than
> fallback since AFAIK that's what users expect there.

Thanks a lot for the list of languages covered by T/H/C. T/H/C got expanded a
lot ! :-) 

 Then, I agree with you and Mark. 

As for CJK, I'm still not sure, but  let's just do what you suggested.

[jungshik at Google, 2009-10-29 21:57:37]

http://codereview.chromium.org/335031/diff/10001/9011
File chrome/app/resources/locale_settings_ja.xtb (right):

http://codereview.chromium.org/335031/diff/10001/9011#newcode8
Line 8: <translation id="IDS_WEB_FONT_FAMILY">Helvetica</translation>
"Helvetica, Hiragino Kaku Gothic Pro" might work better. An alternative would be
'Helvetica, sans-serif"

http://codereview.chromium.org/335031/diff/10001/9041
File chrome/app/resources/locale_settings_ko.xtb (right):

http://codereview.chromium.org/335031/diff/10001/9041#newcode8
Line 8: <translation id="IDS_WEB_FONT_FAMILY">Helvetica</translation>
"Helvetica, AppleGothic" might work better.

http://codereview.chromium.org/335031/diff/10001/9041#newcode25
Line 25: <translation id="IDS_CURSIVE_FONT_FAMILY">Apple Chancery</translation>
'Gungseo' can be used here, but it does not matter much.

http://codereview.chromium.org/335031/diff/10001/9030
File chrome/app/resources/locale_settings_zh-CN.xtb (right):

http://codereview.chromium.org/335031/diff/10001/9030#newcode8
Line 8: <translation id="IDS_WEB_FONT_FAMILY">Helvetica</translation>
For fonts to use in DOMUI, multiple fonts can be listed. "Helvetica, STHeiti'
might work better(?).

http://codereview.chromium.org/335031/diff/10001/9037
File chrome/app/resources/locale_settings_zh-TW.xtb (right):

http://codereview.chromium.org/335031/diff/10001/9037#newcode8
Line 8: <translation id="IDS_WEB_FONT_FAMILY">Helvetica</translation>
With other CJK, you may want to list CJK-specific sans-serif font after
Helvetica.

http://codereview.chromium.org/335031/diff/10001/9037#newcode23
Line 23: <translation id="IDS_SERIF_FONT_FAMILY">Apple LiSung</translation>
I'm not sure "LiHei Pro" and "LiSong Pro" would be better than "Apple LiGothic",
"Apple LiSung". My suspicion is that 'Apple Li*' are fonts coming from Mac OS
Classic (they're 'dfonts') while "Li* Pro" are new in OS X. 

Ok. I found this
(http://mac.hk/appletalk/viewtopic.php?p=22181&sid=52de363b788185e4d2dc9d4ce06...).
"Li* Pro" supports HKSCS-specific additions. So, I think we'd better go with
them rather than 'Apple Li*".  That way, we can minimize the chance of 'ransom
note effect" when a document with HKSCS-specific characters is rendered.

[Avi (use Gerrit), 2009-10-30 15:58:28]

http://codereview.chromium.org/335031/diff/10001/9011
File chrome/app/resources/locale_settings_ja.xtb (right):

http://codereview.chromium.org/335031/diff/10001/9011#newcode8
Line 8: <translation id="IDS_WEB_FONT_FAMILY">Helvetica</translation>
On 2009/10/29 21:57:37, Jungshik Shin wrote:
> "Helvetica, Hiragino Kaku Gothic Pro" might work better. An alternative would
be
> 'Helvetica, sans-serif"

OK. Turns out, BTW, that IDS_WEB_FONT_FAMILY is used in maybe only 1 of the
dozen or so UI webpages.

http://codereview.chromium.org/335031/diff/10001/9041
File chrome/app/resources/locale_settings_ko.xtb (right):

http://codereview.chromium.org/335031/diff/10001/9041#newcode25
Line 25: <translation id="IDS_CURSIVE_FONT_FAMILY">Apple Chancery</translation>
On 2009/10/29 21:57:37, Jungshik Shin wrote:
> 'Gungseo' can be used here, but it does not matter much. 
> 

Oh! Nice font. Seems to be named "#GungSeo" though.

http://codereview.chromium.org/335031/diff/10001/9037
File chrome/app/resources/locale_settings_zh-TW.xtb (right):

http://codereview.chromium.org/335031/diff/10001/9037#newcode23
Line 23: <translation id="IDS_SERIF_FONT_FAMILY">Apple LiSung</translation>
On 2009/10/29 21:57:37, Jungshik Shin wrote:
> I'm not sure "LiHei Pro" and "LiSong Pro" would be better than "Apple
LiGothic",
> "Apple LiSung". My suspicion is that 'Apple Li*' are fonts coming from Mac OS
> Classic (they're 'dfonts') while "Li* Pro" are new in OS X. 
> 
> Ok. I found this
>
(http://mac.hk/appletalk/viewtopic.php?p=22181&sid=52de363b788185e4d2dc9d4ce06...).
> "Li* Pro" supports HKSCS-specific additions. So, I think we'd better go with
> them rather than 'Apple Li*".  That way, we can minimize the chance of 'ransom
> note effect" when a document with HKSCS-specific characters is rendered.
> 

Done.

[Mark Mentovai, 2009-10-30 16:04:31]

jshin@chromium.org wrote:
> http://codereview.chromium.org/335031/diff/10001/9011#newcode8
> Line 8: <translation id="IDS_WEB_FONT_FAMILY">Helvetica</translation>
> "Helvetica, Hiragino Kaku Gothic Pro" might work better. An alternative
> would be 'Helvetica, sans-serif"

What's the point?  A Mac's never going to not have Helvetica available.

Mark

[jungshik at Google, 2009-10-30 16:33:09]

On 2009/10/30 16:04:31, Mark Mentovai wrote:
> mailto:jshin@chromium.org wrote:
> > http://codereview.chromium.org/335031/diff/10001/9011#newcode8
> > Line 8: <translation id="IDS_WEB_FONT_FAMILY">Helvetica</translation>
> > "Helvetica, Hiragino Kaku Gothic Pro" might work better. An alternative
> > would be 'Helvetica, sans-serif"
> 
> What's the point?  A Mac's never going to not have Helvetica available.

Sure,  it does.  I'm not worried about Helvetica at all. The point is to make
Japanese domUI (e.g. New Tab, History) reliably use a Japanese font when
Helvetica does not cover characters (e.g. Kanji and Katakana) instead of a
Chinese or Korean font. 

Perhaps, I'm worried too much. Because on Mac, Japanese Chrome implies Japanese
at the top of the language list in the system preference (on Windows, Chrome's
UI language can be independent of the OS UI language), Mac OS X is likely to
take care of that, automatically.


> 
> Mark

[Avi (use Gerrit), 2009-10-30 16:35:30]

On 2009/10/30 16:33:09, Jungshik Shin wrote:
> The point is to make
> Japanese domUI (e.g. New Tab, History) reliably use a Japanese font when
> Helvetica does not cover characters (e.g. Kanji and Katakana) instead of a
> Chinese or Korean font. 

Does listing a font in the list control the glyph fallback order?

[jungshik at Google, 2009-10-30 16:54:24]

On 2009/10/30 16:35:30, Avi wrote:
> On 2009/10/30 16:33:09, Jungshik Shin wrote:
> > The point is to make
> > Japanese domUI (e.g. New Tab, History) reliably use a Japanese font when
> > Helvetica does not cover characters (e.g. Kanji and Katakana) instead of a
> > Chinese or Korean font. 
> 
> Does listing a font in the list control the glyph fallback order?

Only for domUI fonts. Other preferences can take only a single value. 
IDS*WebFont is injected into our domUI's CSS. It can take a list (comma
separated). 

I wish we could take a list for other font prefs, too.  Then, the font selection
UI would be very tough to design (or too difficult for average users) if we did
that. Also, Webkit has to be changed to take lists because our preferences are
mapped to Settings via WebPreferences). Mozilla has two preferences for each CSS
family + langGroup/script pair, one taking a single value and the other taking a
fallback list, but it just offers the UI for the former (the latter can be
changed with its 'about:config' interface by advanced users). 

Not being able to do so puts us in kinda quandary with CJK monospace fonts.
Unlike on Windows (e.g. "MS Mincho" is bi-width while "MS PMincho" is
proportional), Mac OS X does not come with 'monospace' (actually "bi-width" in
that CJK characters have twice the width of the glyphs for the ASCII portion +
alpha) fonts. What we can do is 

1) Ignore that CJK fonts we specify are not "monospace" (not bi-width) and
specify sans-serif CJK fonts like STHei or AppleGothic for 'monospace'
(sans-serif goes better with monospace for CJK). That's what the current CL does

2) Put 'Courier New' for monospace font pref for CJK and hope the font fallback
will do the right thing. 

I'm sorry I meant to mention this when starting a review, but forgot it while
going through the files.  What do you think of this? 

If you think #1 is ok, you can just go ahead and land. 

BTW, '#Gungseo' is probably for a vertical layout. I don't know why 'Gungseo'
does not show up. Anyway, cursive does not matter much and we can just go with
'Apple Chan*' for Korean.

[jungshik at Google, 2009-10-30 16:55:52]

I meant 'Courier' (not 'Courier New').

[Avi (use Gerrit), 2009-10-30 17:21:57]

Does monospace mean much for CJK (re columns lining up)? Let's do Courier and
let the fallback do its thing.

[Avi (use Gerrit), 2009-10-30 17:25:01]

Changes from last time:

- Korean has no cursive (uses Apple Chancery)
- Korean and Chinese use Courier (there is a fixed-width Japanese font)

Good to land?

[jungshik at Google, 2009-10-30 21:58:53]

LGTM !

On 2009/10/30 17:25:01, Avi wrote:
> Changes from last time:
> 
> - Korean has no cursive (uses Apple Chancery)
> - Korean and Chinese use Courier (there is a fixed-width Japanese font)

Yes, I saw that (Osaka Mono). 

> 
> Good to land?

[jungshik at Google, 2009-10-30 22:01:59]

On 2009/10/30 17:21:57, Avi wrote:
> Does monospace mean much for CJK (re columns lining up)? Let's do Courier and
> let the fallback do its thing.

Yes, that's better although the width ratio between the "ASCII portion" and the
CJK is not 1:2 (as expected by East Asian users).

[Avi (use Gerrit), 2009-11-02 15:48:41]

On 2009/10/30 22:01:59, Jungshik Shin wrote:
> Yes, that's better although the width ratio between the "ASCII portion" and
the
> CJK is not 1:2 (as expected by East Asian users).

:( This'll have to do for now; if they need that they can tweak the font.