Issue metadata
Sign in to add a comment
|
Blink 537.36 Cannot rendering text with Adobe Type1 font in Linux
Reported by
icc.pot....@gmail.com,
Jul 22 2016
|
||||||||||||||||||||||||
Issue descriptionChrome Version : Google Chrome 52.0.2743.82 (Official Build) URL : all pages Behavior in Safari 4.x/5.x: page is rendered in normally Behavior in Firefox 3.x/4.x: page is rendered in normally Linux distro: ArchLinux (packages is updated at Jul 22th, 2016, about 3:00 UTC) What steps will reproduce the problem? (1) setting sans-serif and seirf fontfamily to using type1 font with fontconfig (2) All pages is rendered with nothing text (But, if web page suggest opentype/truetype font family in CSS,I can get correct rendering result.) (3) I tested Vivaldi snapshot is also (Vivaldi snapshot also uses blink 537.36)
,
Jul 22 2016
,
Jul 22 2016
I suspect this is intentional.
,
Jul 22 2016
Sorry, I don't remember the details here.
,
Jul 22 2016
Humm. I had totally forgotten that such things still exist... Dominik: do you think we should detect non-OpenType fonts and fallback to Skia-based font funts instead of hb-ot-font?
,
Jul 22 2016
My personal preference is to say we don't support non-OpenType fonts, and filter those out.
,
Jul 26 2016
,
Jul 26 2016
See report in the above issue for bisect. While it appears CG and DirectWrite do not support Type1, Ubuntu is still shipping Type1 fonts in standard packages (http://packages.ubuntu.com/yakkety/all/gsfonts/filelist for an example).
,
Jul 29 2016
Sure, but I still suggest not-support. This is not different from not supporting bitmap fonts.
,
Aug 1 2016
This is different from not supporting bitmap fonts. Skia didn't handle drawing of bitmap fonts well at all in the past, so they were filtered out. Skia does support bitmap fonts fairly well now, and there's no great reason to exclude them anymore (other than looking kinda ugly and the present bug, of course). I see no good reason to limit Blink to sfnt fonts only. Ubuntu generally supports non-sfnt fonts; Type1 fonts (from the gsfonts package) are part of the default install of Ubuntu.
,
Aug 1 2016
Web doesn't support non-sfnt... And gsfonts are generally there for ghostscript to work. It's a packaging bug to expose them to fontconfig. Sure, Blink supported them in the past. But does that mean we support them forever? Anyway, I leave it to drott@ to decide.
,
Aug 2 2016
,
Aug 5 2016
FWIW, here is a snippet that claims to remove them from fontconfig: https://gist.github.com/gdamjan/8672432
,
Aug 26 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e70ca0a2e161e47a7f36f94c19e5a9c6448a15b9 commit e70ca0a2e161e47a7f36f94c19e5a9c6448a15b9 Author: drott <drott@chromium.org> Date: Fri Aug 26 09:24:36 2016 Filter font list, use Fontconfig and build on Ozone Since we dropped support for rendering Type 1 fonts in Chrome, we should filter the list of fonts that can be configured as defaults to only display fonts that have the right font format, i.e. TrueType or CFF. A a side effect, this allows us to build the font list enumeration for ozone as well, as it is only dependent on Fontconfig after this CL, not dependent on Pango anymore. For backwards compability with the old implementation, we're adding three Fontconfig alias families Sans, Serif and Monospace to the list, since our default settings on Linux included the "Monospace" family for the fixed width font. BUG= 630508 , 457307 Review-Url: https://codereview.chromium.org/2278143002 Cr-Commit-Position: refs/heads/master@{#414677} [modify] https://crrev.com/e70ca0a2e161e47a7f36f94c19e5a9c6448a15b9/content/common/BUILD.gn [add] https://crrev.com/e70ca0a2e161e47a7f36f94c19e5a9c6448a15b9/content/common/font_list_fontconfig.cc [delete] https://crrev.com/bce76d1034fd1ea3c97abf58aaa33b146fd20d69/content/common/font_list_ozone.cc [delete] https://crrev.com/bce76d1034fd1ea3c97abf58aaa33b146fd20d69/content/common/font_list_pango.cc [modify] https://crrev.com/e70ca0a2e161e47a7f36f94c19e5a9c6448a15b9/content/content_common.gypi
,
Sep 8 2016
Merging, Type 1 fonts are no longer supported. If sans-serif or serif are configured to be Type 1 fonts in Fontconfig this will not use and trigger font fallback.
,
Oct 10 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b9d9cb9d8693d5fc3b4bc9e4067b3020f3a90b1c commit b9d9cb9d8693d5fc3b4bc9e4067b3020f3a90b1c Author: hshi <hshi@chromium.org> Date: Mon Oct 10 19:44:25 2016 Filter font list, use Fontconfig and build on Ozone Since we dropped support for rendering Type 1 fonts in Chrome, we should filter the list of fonts that can be configured as defaults to only display fonts that have the right font format, i.e. TrueType or CFF. A a side effect, this allows us to build the font list enumeration for ozone as well, as it is only dependent on Fontconfig after this CL, not dependent on Pango anymore. For backwards compability with the old implementation, we're adding three Fontconfig alias families Sans, Serif and Monospace to the list, since our default settings on Linux included the "Monospace" family for the fixed width font. BUG= 630508 , 457307 TBR=avi@chromium.org TBR=derat@chromium.org TBR=spang@chromium.org NOTRY=true NOPRESUBMIT=true Review-Url: https://codereview.chromium.org/2278143002 Cr-Commit-Position: refs/heads/master@{#414677} (cherry picked from commit e70ca0a2e161e47a7f36f94c19e5a9c6448a15b9) Review-Url: https://codereview.chromium.org/2406983002 Cr-Commit-Position: refs/branch-heads/2840@{#705} Cr-Branched-From: 1ae106dbab4bddd85132d5b75c670794311f4c57-refs/heads/master@{#414607} [modify] https://crrev.com/b9d9cb9d8693d5fc3b4bc9e4067b3020f3a90b1c/content/common/BUILD.gn [add] https://crrev.com/b9d9cb9d8693d5fc3b4bc9e4067b3020f3a90b1c/content/common/font_list_fontconfig.cc [delete] https://crrev.com/55a0dba38e5df7bea291c3aa0ce96b01892d74ec/content/common/font_list_ozone.cc [delete] https://crrev.com/55a0dba38e5df7bea291c3aa0ce96b01892d74ec/content/common/font_list_pango.cc [modify] https://crrev.com/b9d9cb9d8693d5fc3b4bc9e4067b3020f3a90b1c/content/content_common.gypi
,
Oct 27 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b9d9cb9d8693d5fc3b4bc9e4067b3020f3a90b1c commit b9d9cb9d8693d5fc3b4bc9e4067b3020f3a90b1c Author: hshi <hshi@chromium.org> Date: Mon Oct 10 19:44:25 2016 Filter font list, use Fontconfig and build on Ozone Since we dropped support for rendering Type 1 fonts in Chrome, we should filter the list of fonts that can be configured as defaults to only display fonts that have the right font format, i.e. TrueType or CFF. A a side effect, this allows us to build the font list enumeration for ozone as well, as it is only dependent on Fontconfig after this CL, not dependent on Pango anymore. For backwards compability with the old implementation, we're adding three Fontconfig alias families Sans, Serif and Monospace to the list, since our default settings on Linux included the "Monospace" family for the fixed width font. BUG= 630508 , 457307 TBR=avi@chromium.org TBR=derat@chromium.org TBR=spang@chromium.org NOTRY=true NOPRESUBMIT=true Review-Url: https://codereview.chromium.org/2278143002 Cr-Commit-Position: refs/heads/master@{#414677} (cherry picked from commit e70ca0a2e161e47a7f36f94c19e5a9c6448a15b9) Review-Url: https://codereview.chromium.org/2406983002 Cr-Commit-Position: refs/branch-heads/2840@{#705} Cr-Branched-From: 1ae106dbab4bddd85132d5b75c670794311f4c57-refs/heads/master@{#414607} [modify] https://crrev.com/b9d9cb9d8693d5fc3b4bc9e4067b3020f3a90b1c/content/common/BUILD.gn [add] https://crrev.com/b9d9cb9d8693d5fc3b4bc9e4067b3020f3a90b1c/content/common/font_list_fontconfig.cc [delete] https://crrev.com/55a0dba38e5df7bea291c3aa0ce96b01892d74ec/content/common/font_list_ozone.cc [delete] https://crrev.com/55a0dba38e5df7bea291c3aa0ce96b01892d74ec/content/common/font_list_pango.cc [modify] https://crrev.com/b9d9cb9d8693d5fc3b4bc9e4067b3020f3a90b1c/content/content_common.gypi |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Jul 22 2016