Computing desk
< November 19	<< Oct \| November \| Dec >>	November 21 >

Welcome to the Wikipedia Computing Reference Desk Archives
The page you are currently viewing is an archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages.

November 20

Noto fonts don't work on Chrome browser

Hi all, I'm a linguistics enthusiast and I would like to see my browser showing every possible glyph coded in Unicode. The Noto font family seemed the right answer. Unfortunately, they don't seem to work with Chrome browser (ironically, Google developed both) on Win 7 64 bit. It seems that Chrome prefers a single font which encodes all glyphs (e.g. Code2000), rather than a large font family. Is there a way to force Chrome using Noto font family? I surfed the web finding no clear workaround. Thanks in advance.--Carnby (talk) 17:39, 20 November 2016 (UTC)[reply]

@Carnby:

1) Setup the "Stylish" extension.

2) Create a new style ("Manage installed styles" > "Write new style").

@font-face {
  font-family: Noto;
  src: local("Noto Sans");
}
@font-face {
  font-family: Noto;
  src: local("Noto Naskh Arabic");
}
/* add more fonts */

* { /* asterisk means it will apply to any html tag, that is to the entire web page; you may specify, but it may become buggy */
  font-family: Noto !important;
}

3) You may also use the "Force Custom Fonts" extension (I didn't try).

4) If something's not clear search for "@font-face css".

5) Note this possibly may fail displaying custom fonts with custom icons on some sites (check this). --Lüboslóv Yęzýkin (talk) 20:57, 21 November 2016 (UTC)[reply]

Thanks, it overall works but I still encounter some problems: for example the Stylish extension seems not to support CSS property unicode-range and Chrome simply ignores more recent Unicode additions (7.0, 8.0, 9.0).--Carnby (talk) 19:40, 22 November 2016 (UTC)[reply]

@Carnby: Yes, I'm aware of that, and after doing some research it seems to be the problem of the extension (probably better to write to the author directly and ask to fix it?). I cannot comment on Unicode as I do not use the browser. If it is really thus, then it's another good reason not to use it. In Firefox it's simpler (no need for an extention, just edit userContent.css) and everything works.--Lüboslóv Yęzýkin (talk) 12:48, 23 November 2016 (UTC)[reply]

@Carnby: It seems nothing's wrong with Chrome, but the Noto font family lacks a great deal of Unicode. Try to use other fonts like Unifont. But note when manipulating multiple fonts with Stylish, the font listed below overrides the font listed above. So you need to list Unifont above Noto otherwise everything will be in Unifont. (I don't know why this is so, seems like an idiosyncrasy of Stylish. But you may not need unicode-range, just list fonts in the right order.) Test here. --Lüboslóv Yęzýkin (talk) 14:20, 23 November 2016 (UTC)[reply]