all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Zhu Zihao <all_but_last@163.com>
To: 54297@debbugs.gnu.org
Subject: bug#54297: Qutebrowser failed to render local fonts.
Date: Tue, 08 Mar 2022 21:29:15 +0800	[thread overview]
Message-ID: <86lexka7o0.fsf@163.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 459 bytes --]

Commit 9e154465b2265359a8ec7bb27defc4449a3a15ff, install qutebrowser and
browse some website(in example: gnu.org), qutebrowser cannot display text. screenshot
attached.

But I visit the https://lichess.org, it can display some text. I guess
that those text use font specified by website (webfont), but other text
are using local font, but qutebrowser failed to render them.

I also test with other qtwebengine based application, they suffer from
same issue.


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]

[-- Attachment #2: bad-font-rendering-on-gnu-org.png --]
[-- Type: image/png, Size: 371137 bytes --]

[-- Attachment #3: some-fonts-are-available-on-lichess.png --]
[-- Type: image/png, Size: 177754 bytes --]

[-- Attachment #4: Type: text/plain, Size: 101 bytes --]



-- 
Retrieve my PGP public key:

  gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F

Zihao

             reply	other threads:[~2022-03-08 14:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 13:29 Zhu Zihao [this message]
     [not found] ` <handler.54297.B.16467475122349.ack@debbugs.gnu.org>
2022-03-08 14:42   ` bug#54297: Acknowledgement (Qutebrowser failed to render local fonts.) Zhu Zihao
2022-05-02  9:00 ` bug#54297: Qutebrowser failed to render local fonts Lars-Dominik Braun
2022-05-02 14:15   ` Zhu Zihao
2022-05-28  3:18 ` Edison Ibáñez
2022-05-28 15:41   ` bdju via Bug reports for GNU Guix

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=86lexka7o0.fsf@163.com \
    --to=all_but_last@163.com \
    --cc=54297@debbugs.gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.