"sans serif" selected in Google Docs doesn't use a sans serif font
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
People
(Reporter: mavladi, Unassigned)
Details
Attachments
(1 file)
|
14.98 KB,
image/png
|
Details |
sans_serif_isnt_serif
+++ This bug was initially created as a clone of Bug #1567322 +++
A new description for the Bug #1567322.
Displaying a serif font in Google Docs and Sheets when a "Courier New" or a "sans serif" (sic! this is the name which Firefox displayed, although font with "sans serif" is not installed in my system) is requested.
Chromium browser on the same machine renders this fonts correctly, and named Arial font correctly too (Arial instead of "sans serif").
In my case serif font on screenshot which used by Firefox is Bitstream Vera Serif -- as for "sans serif" (top line), so as for "Courier New" (bottom line).
In case of the Bug #1567322, enabling Arial in MacOS FontBook fixes the bug, but in Linux Arial and Courier New is installed (/usr/share/fonts/TTF/arial.ttf for Arial and /usr/share/fonts/TTF/cour.ttf for Courier New, so I can use these fonts in other applications, such as LibreOffice, Inkscape and so on.
In addition, this bug is present in 84.0b8 Developer Edition.
As a temporary workariound, disabling loading of the 49-sansserif.conf file (part of the fontconfig package) via removing symlink, fixes the bug.
Before I has found Bug #1567322, I opened a issue on fontconfig https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/268
OS: Arch Lunux.
|
||
Comment 1•5 years ago
|
||
I don't really understand quite what's going on here, but it seems like there must be a quirk in the fontconfig setup that is leading to the font family name "Sans Serif" being included in the list of available fonts. This is not the same as the sans-serif (note: hyphenated!) CSS generic family that might be appended as a default; it appears to be a "real" font family name. Possibly corresponds to a legacy X11 bitmap font that fontconfig knows about, but that is not actually usable by current Firefox? In that case we'd likely end up using a default fallback.
|
|
||
Updated•5 years ago
|
A little update:
After reinstalling ttf-bitstream-vera package this bug is gone.
I decide to remove Bitstream Vera Serif font, with which Firefox substitute Arial and Courier New. My goal was to see -- which font Firefox will use next, if Bitstream Vera Serif font will no exists in system? So I removed whole ttf-bitstream-vera package, and fonts in Google Docs began to render normally; moreover, after I installed ttf-bitstream-vera again, Google Docs works correctly.
But what was the root cause for this? I don't know, but -- why it affect Firefox but Chromium and why Arial font was substituted with Bitstream marked as Serif is remain unanswered too.
Description
•