On 2016-04-07 21:24, Mingye Wang wrote:
> In addition to the weight matching problem, the screenshot for
> Chromium in #113 gives the JP variant instead of TW.
I didn't even notice "JP" first. This made me fear that
/etc/fonts/conf.avail/64-language-selector-prefer.conf has something to do with it. But the issue with too thin characters in Chrome/Chromium is there also with a TC locale:
On 2016-04-07 21:24, Mingye Wang wrote:
> In addition to the weight matching problem, the screenshot for
> Chromium in #113 gives the JP variant instead of TW.
I didn't even notice "JP" first. This made me fear that conf.avail/ 64-language- selector- prefer. conf has something to do with it. But the issue with too thin characters in Chrome/Chromium is there also with a TC locale:
/etc/fonts/
$ locale | grep LC_CTYPE zh_TW.UTF- 8
LC_CTYPE=
$ fc-match
NotoSansCJK.ttc: "Noto Sans CJK TC" "Regular"
$
So it's probably unrelated to that.
Isn't this issue really weird? Shouldn't Google make sure that their own web browser handles their own fonts properly?