New issue
Advanced search Search tips

Issue 787956 link

Starred by 1 user
Status: Duplicate
Merged: issue 245525
Owner: ----
Closed: Nov 2017
Cc:
kojii@chromium.org
e...@chromium.org
drott@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

font fallback: does not try all the fonts on the machine to find a font covering a character

Project Member Reported by js...@chromium.org, Nov 22 2017 
How to reproduce:

1. Go to https://en.wikipedia.org/wiki/Egyptian_Hieroglyphs_(Unicode_block) in Chrome and Safari. 

Actual:

Egyptian Hieroglyphs are shown as Tofus. 

Expected: They're shown as in Safari. 

macOS is bundled with dozens of Noto fonts (see the list included in macOS 10.12 at  https://support.apple.com/en-us/HT206872 ), but Chrome does not use them because its font fallback does NOT scan *all* the fonts installed on the system to look for a font to cover a given character. 

Other platforms (Windows and Linux) have a similar issue. I'll file a separate bug on that (or will use this one if that's better). Linux used to be better in this respect, but recently I've come across tofus more often (even for CJK ideographs or Hangul for which I definitely have more than one fonts in certain hard-to-reduce cases).

Comment 1 by drott@chromium.org, Nov 23 2017 

Yes, you have previously filed issue: 245525. Perhaps it'd help if you'd organize bugs with meta bugs if you plan to file them per platform? 

I am aware that we do not have a full system font scan and indexing. I am thinking about the design for such a thing, but it's a very resource intensive process. 

The solution for this needs to cover issue 591346 (punctuation fallback) as well as correct matching of Postscript names for @font-face{ src:local('PS Name') } and other things. It's a larger effort.

Comment 2 by e...@chromium.org, Nov 30 2017

Mergedinto: 245525
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment