From: sburris0 <sburris0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Helvetica shouldn't be a bitmap font provided by xorg-fonts-75dpi
Date: Sun, 31 May 2020 21:19:03 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22477@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
New issue by sburris0 on void-packages repository
https://github.com/void-linux/void-packages/issues/22477
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.4.43_1 x86_64 AuthenticAMD uptodate rrmFF
* package:
firefox
xorg-fonts
### Expected behavior
Fonts in Firefox should look nice
### Actual behavior
Pages such as https://github.com/void-linux/void-packages have jagged, ugly fonts everywhere.
### Steps to reproduce the behavior
1. Install a font package
2. Open Firefox to a page such as this
### Fix
I found this fix on r/voidlinux: https://www.reddit.com/r/voidlinux/comments/fa9wyk/solution_for_non_antialiased_fonts_in_firefox_and/
The solution is to symlink fontconfig config files then update the font cache.
```
ln -s /usr/share/fontconfig/conf.avail/70-no-bitmaps.conf /etc/fonts/conf.d/70-no-bitmaps.conf
fc-cache -fv
```
The issue explained on arch wiki, in the context of PDFs: https://wiki.archlinux.org/index.php/Font_configuration#Helvetica_font_problem_in_generated_PDFs
I think that if this can't be fixed with a `post_install()` in a package, then a message following installation or a mention in the handbook would be helpful.
next reply other threads:[~2020-05-31 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 19:19 sburris0 [this message]
2020-05-31 21:25 ` abenson
2020-05-31 21:26 ` abenson
2020-05-31 21:39 ` ericonr
2020-05-31 21:39 ` ericonr
2021-04-27 18:46 ` [ISSUE] [CLOSED] " sburris0
2023-07-15 16:07 ` StreetStrider
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22477@inbox.vuxu.org \
--to=sburris0@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).