Fontconfig fallbacks ignored for missing glyphs
Reported by
ter...@gmail.com,
May 9 2016
|
||||||||
Issue descriptionChrome Version : 50.0.2661.94 URLs (if applicable) : http://jsbin.com/towazexetu/edit?html,output Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: Firefox: OK IE: What steps will reproduce the problem? (1) Configure your fontconfig with a set of fallbacks, e.g.: <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> <alias> <family>serif</family> <prefer> <family>Merriweather</family> <family>cwTeXMing</family> <family>Symbola</family> </prefer> </alias> <alias> <family>sans-serif</family> <prefer> <family>Merriweather Sans</family> <family>Source Han Sans CN</family> <family>Symbola</family> </prefer> </alias> </fontconfig> (2) Visit the URL: http://jsbin.com/towazexetu/edit?html,output What is the expected result? The glyphs not found for the serif font Merriweather should fallback to cwTeXMing and eventually Symbola. What happens instead? If a glyph is not found in Merriweather it takes another route and ends up fallbacking to Source Han Sans CN. So basically it assumes the font cannot be used an continues in the list of font-families as soon as a glyph is not found, instead of going through all the fonts according to the fontconfig. I have tried putting a font after serif that has the glyph and then it will use that one. I assumes that the browser fall backs to sans-serif if no font-family matches and that is how it ends up matching the Source Han Sans CN.
,
May 14 2016
I have upgraded to the latest version and the problem still persists. I am running Archlinux. In your screenshot you managed to reproduce the issue , as you can see in the window in the behind, the chinese font is different and correct. While in the front window it is using the Han Sans.
,
May 14 2016
Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 17 2016
,
May 17 2016
,
May 19 2016
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
,
Apr 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 18 2018
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by kavvaru@chromium.org
, May 13 2016Labels: Needs-Feedback
239 KB
239 KB View Download