From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] `google-fonts-ttf` bugs out with regard to `AdobeBlank-Regular.ttf`
Date: Sun, 21 Aug 2022 05:54:18 +0200 [thread overview]
Message-ID: <20220821035418.6sV3hii41KKpR38p65Ad-MPsIbz064DJQ5TGm48G04Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38802@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Closed issue by endigma on void-packages repository
https://github.com/void-linux/void-packages/issues/38802
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.17_1 x86_64 AuthenticAMD notuptodate rFFFFF
### Package(s) Affected
google-fonts-ttf-20210628_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://aur.archlinux.org/packages/ttf-google-fonts-git (ctrl+f `blank`)
### Expected behaviour
The package should do `sudo rm -fr /usr/share/fonts/TTF/AdobeBlank-Regular.ttf` during the install process, this font is broken. https://aur.archlinux.org/packages/ttf-google-fonts-git#comment-574519 could also be a fix if included.
### Actual behaviour
`google-fonts-ttf` includes `/usr/share/fonts/TTF/AdobeBlank-Regular.ttf` which when installed breaks CJK (? other) character rendering in at least chrome, firefox (? others).
### Steps to reproduce
1. Install `google-fonts-ttf`
2. Open firefox/chromium
3. Visit yandex or google translate or deepl and translate `hello` to chinese simplified
4. Do it again after `sudo rm -fr /usr/share/fonts/TTF/AdobeBlank-Regular.ttf` (it will fix it)
prev parent reply other threads:[~2022-08-21 3:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 0:34 [ISSUE] `google-fonts-ttf` needs removal of `AdobeBlank-Regular.ttf` endigma
2022-08-21 0:37 ` endigma
2022-08-21 2:17 ` `google-fonts-ttf` bugs out with regard to `AdobeBlank-Regular.ttf` sgn
2022-08-21 2:20 ` sgn
2022-08-21 3:54 ` sgn
2022-08-21 3:54 ` sgn [this message]
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=20220821035418.6sV3hii41KKpR38p65Ad-MPsIbz064DJQ5TGm48G04Y@z \
--to=sgn@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).