[arch-general] Firefox dropping support for OTB fonts as well?
Hello ! After pango moved to use Harfbuzz, the Terminus bitmap fonts no longer were shown as a font on could select on firefox, so Terminus bitmap fonts were actually dropped. Then later kept showing up on Firefox as they used to, like xos4 Terminus, but I don't know if they kept working as before... At that time though, Terminus OTB (openTypeBitmap) were still showing up as an option on Firefox, as just Terminus, and were working fine. Even until versions 88+. With Firefox 89, the Terminus OTB and the Terminus bitmap fonts can be selected still, but they don't really work anymore. When one zooms out or zooms in a web site, the mono space fonts using whether Terminus or xos4 Terminus do NOT zoom at all, they remain the same pretty small size. And manually changing the monospace (which are the ones I set with terminus fonts) size through preferences don't make the fonts change size at all. So it seems neither bitmap, nor OTP, Terminus fonts are working on Firefox any more. On AUR there's a terminus-font-ttf, meant for Java applications it seems, which are apparently working on Firefox. I tried them before on virtual terminals like rxvt-unicode and qterminal, and they look pretty bad (blurry actually), so I wouldn't dare using those fonts on any virtual terminal. However they seem to work on Firefox. Has Firefox finally dropped support for non TTF fonts? Are the TTF Terminus fonts, the definite work around? If someone knows, please provide some light, :) Thanks a lot ! -- Javier
Hello,
From https://blogs.gnome.org/mclasen/2019/05/25/pango-future-directions/ "Using Harfbuzz for font loading means that we will lose support for bitmap and type1 fonts. We think this is an acceptable trade-off, but others might disagree."
----- quote ----- *Stop using **freetype* Freetypes FT_Face object has locking semantics that are broken and hard to work with; they are constantly getting in the way as we are juggling hb_fonts, FT_Face and cairo scaled font objects. We’ve concluded that the best way forward is to stop using freetype for font loading or accessing font and glyph metrics. We can use Harfbuzz for all of these (a small gap[https://github.com/harfbuzz/harfbuzz/pull/1432] will be closed soon). Using Harfbuzz for font loading means that we will lose support for bitmap and type1 fonts. We think this is an acceptable trade-off, but others might disagree. Note that Harfbuzz /does/ support loading bitmap-only OpenType fonts. ----- endquote -----
On 6/9/21 12:52 PM, Samir Nassar via arch-general wrote:
Hello,
From https://blogs.gnome.org/mclasen/2019/05/25/pango-future-directions/ "Using Harfbuzz for font loading means that we will lose support for bitmap and type1 fonts. We think this is an acceptable trade-off, but others might disagree."
I understood that, that's why I moved to Terminus OTP instead of Terminus bitmap. Open Type fonts are supported by harfbuzz, and what I see right now is that Terminus OTP is not working on Firefox, :( And BTW, the terminus-fonts package merged with the terminus-otp one, and for some time it's been providing both, OTP and bitmaps fonts... So, even OTPs are not supported now? -- Javier
BTW, I just realized I mistakenly used OTP... Wherever you read that, please replace it with OTB (OpenTypeBitmap)... s/OTP/OTB/g s/otp/otb/g Sorry ! -- Javier
Hi, On Wed, Jun 09, 2021 at 12:37:07PM -0600, Javier via arch-general wrote:
With Firefox 89, the Terminus OTB and the Terminus bitmap fonts can be selected still, but they don't really work anymore. When one zooms out or zooms in a web site, the mono space fonts using whether Terminus or xos4 Terminus do NOT zoom at all, they remain the same pretty small size.
I think this is just a bug in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1714282#c13 The workaround (setting gfx.e10s.font-list.shared to false) works fine for me. Cheers Peter
On 6/10/21 9:08 AM, Peter via arch-general wrote:
I think this is just a bug in Firefox:
https://bugzilla.mozilla.org/show_bug.cgi?id=1714282#c13
The workaround (setting gfx.e10s.font-list.shared to false) works fine for me.
Yep, I tried the work around, and it works great. Thanks ! -- Javier
participants (3)
-
Javier
-
Peter
-
Samir Nassar