Selecting Noto Sans CJK KR as Standard/Sans-Serif Font Does Not Take Effect

[oliviazhu]

What steps will reproduce the problem?

1. In Chrome, 'Settings', Show Advance Settings
2. Customize Fonts
3. Set Noto Sans CJK kr as Standard Font & Sans-serif Font

What is the expected output? What do you see instead?
Since Noto Sans can show all Chinese/Japanese/Korean characters, no umbrella
font (e.g., 'Gulim') should be used when viewing typical web pages containing
CJK letters.
But when I choose Noto as default (and Sans-serif) font in Chrome, every Korean
letter is in Gulim, which is ugly since it does not support ClearType.

What version of the product are you using? On what operating system?

Please provide any additional information below.

I guess .OTF files are filtered by some applications. When using font dialog in
several applications, the enumeration skips Noto Sans in some apps and not in
others. For example in MS Word Noto works perfectly, in IE11 not even on the
list, in Chrome on the list but not working.

Here is the screenshot of IE11 font enumeration not showing Noto Sans.

https://storage.googleapis.com/google-code-attachments/noto/issue-192/comment-1/nonoto.PNG

Turning off DirectWrite makes me see Google Noto Sans CJK fonts in browser, but
they are way more ugly than them in Firefox...I cannot describe it but native
CJK users will definitely see it at a glance
...
Adobe's testing suggests that there is an issue with Chrome about selecting
non-default fonts. About IE, it seems that only TrueType fonts can be
specified, which probably makes sense to Microsoft given that they bundle only
TrueType fonts with their OS. In other words, the issue is not with the fonts,
but with browsers' inability to use or select them.

Moved from notofonts/noto-fonts#192

[jungshik]

I confirmed that Chrome allows us to select Noto Sans CJK, but 'font-family: sans-serif' does not pick the font.

<span style="font-family: Noto Sans CJK KR;">한글</span> does work, though.

Firefox does not have this issue. This is a chrome bug and I'll report it at http://crbug.com.

I'll look into IE11 issue.

[davelab6]

@oliviazhu thanks for reporting this one too, and thanks to @jungshik for assessing it. Closing as stale from 2015 and an upstream rendering issue :)