Change the UI font on CrOS to Noto Sans UI from 'Chrome Droid Sans'.

Change the UI font on CrOS to Noto Sans UI from 'Chrome Droid Sans'.

This will go after 'Noto Sans UI' is checked into ChromeOS.

See https://gerrit.chromium.org/gerrit/#/c/29087/1 for the
corresponding CrOS change.

Bug=131515
Test=The UI (both 'native' and web ui) uses Noto Sans UI. For English UI, it's exactly the same as Chrome Droid Sans. If you try Vietnamese UI, there will be no more ransom note effect because Noto Sans UI covers all the Latin letters used in Vietnamese while Chrome Droid Sans does not and leads to a ransom note effect (some characters from Chrome Droid Sans while others coming from other fonts).
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=150605

[Daniel Erat, 2012-08-02 23:22:25]

lgtm

http://codereview.chromium.org/10836082/diff/2001/chrome/app/resources/platfo...
File chrome/app/resources/platform_locale_settings/locale_settings_cros_ar.xtb
(right):

http://codereview.chromium.org/10836082/diff/2001/chrome/app/resources/platfo...
chrome/app/resources/platform_locale_settings/locale_settings_cros_ar.xtb:8:
gtk-font-name="Noto Sans UI,Droid Arabic Naskh,sans-serif, 10"
IDS_LOCALE_GTKRC isn't used anywhere as far as I can tell (which is a relief,
since we don't link against GTK).  Do you mind deleting this?  Putting it in a
separate change is fine if that's easier.

[Evan Stade, 2012-08-02 23:42:53]

http://codereview.chromium.org/10836082/diff/2001/chrome/browser/resources/ch...
File chrome/browser/resources/chromeos/image_burner.html (right):

http://codereview.chromium.org/10836082/diff/2001/chrome/browser/resources/ch...
chrome/browser/resources/chromeos/image_burner.html:89: font-family: 'Noto Sans
UI', 'Droid Sans Fallback', sans-serif;
this should be using the same mechanism as all the other webui pages to load the
system font, i.e. SetFontAndTextDirection

http://codereview.chromium.org/10836082/diff/2001/chrome/browser/resources/fi...
File chrome/browser/resources/file_manager/css/video_player.css (right):

http://codereview.chromium.org/10836082/diff/2001/chrome/browser/resources/fi...
chrome/browser/resources/file_manager/css/video_player.css:8: font-family: Noto
Sans UI,Droid Sans Fallback,sans-serif;
ditto

http://codereview.chromium.org/10836082/diff/2001/chrome/browser/resources/ge...
File chrome/browser/resources/gesture_config.css (right):

http://codereview.chromium.org/10836082/diff/2001/chrome/browser/resources/ge...
chrome/browser/resources/gesture_config.css:6: font-family: 'Noto Sans UI',
'Droid Sans Fallback', sans-serif;
ditto

[jungshik at Google, 2012-08-02 23:51:23]

> this should be using the same mechanism as all the other webui pages 
> to load the system font, i.e. SetFontAndTextDirection

Absolutely ! :-)
I can't agree with you more (having written SetFontAndTextDirection a while
ago), which is why I've already filed http://crbug.com/140307 :-)

I'll work on that bug after this one.

[Evan Stade, 2012-08-03 01:19:36]

ok then lgtm :)

[jungshik at Google, 2012-08-08 17:05:29]

I didn't land it sooner because I was alarmed by a font weight change.  I had to
make sure that it's not this font change but the rendering change that led to a
perceived difference in font weights in the UI (native and web). 

Anyway, I needed an OWNER's approval as well and am asking sky to LGTM.

[sky, 2012-08-08 17:14:16]

LGTM - but you need to address other reviewers comments

[jungshik at Google, 2012-08-08 19:13:43]

On 2012/08/02 23:22:25, Daniel Erat wrote:
> lgtm
> 
>
http://codereview.chromium.org/10836082/diff/2001/chrome/app/resources/platfo...
> File chrome/app/resources/platform_locale_settings/locale_settings_cros_ar.xtb
> (right):
> 
>
http://codereview.chromium.org/10836082/diff/2001/chrome/app/resources/platfo...
> chrome/app/resources/platform_locale_settings/locale_settings_cros_ar.xtb:8:
> gtk-font-name="Noto Sans UI,Droid Arabic Naskh,sans-serif, 10"
> IDS_LOCALE_GTKRC isn't used anywhere as far as I can tell (which is a relief,
> since we don't link against GTK).  Do you mind deleting this?  Putting it in a
> separate change is fine if that's easier.

Yeah, I noticed that, too. I thought we kept them on purpose (for test
builds/comparison with the default non-GTK builds, etc)  even though we don't
rely on GTK any more in ChromeOS.  I'll remove them in a separate CL.