From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: Tim Ruffing <crypto@timruffing.de>, Eli Zaretskii <eliz@gnu.org>,
67810@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#67810: 29.1; fonts use synthetic bold on Linux / pgtk
Date: Mon, 15 Jan 2024 22:02:00 +0800 [thread overview]
Message-ID: <87mst6y9t3.fsf@yahoo.com> (raw)
In-Reply-To: <875xzuzoml.fsf@ledu-giraud.fr> (Manuel Giraud's message of "Mon, 15 Jan 2024 14:56:34 +0100")
Manuel Giraud <manuel@ledu-giraud.fr> writes:
> Po Lu <luangruo@yahoo.com> writes:
>
> [...]
>
>>> Ok but is there such usage of SVG icons into Emacs? If there is it
>>> would require a much more smarter cache or, even better, a fast
>>> rasterizer.
>>
>> Not as yet, but it's being proposed.
>
> You mean that you're working on a new SVG rasterizer? If so, great!
Alas, no. I was referring to increasing the number of SVG icons loaded
by Emacs.
> I don't know about your setup but if you use mupdf as a converter it
> could convert documents to SVG image (see 'doc-view-mupdf-use-svg').
Thanks. I will see if it is possible to install mupdf here.
prev parent reply other threads:[~2024-01-15 14:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 12:03 bug#67810: 29.1; fonts use synthetic bold on Linux / pgtk Tim Ruffing
2023-12-13 12:39 ` Eli Zaretskii
2023-12-13 13:28 ` Tim Ruffing
2023-12-13 13:39 ` Eli Zaretskii
2023-12-13 15:09 ` Tim Ruffing
2023-12-13 15:43 ` Tim Ruffing
2023-12-14 0:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-14 7:28 ` Eli Zaretskii
2023-12-14 9:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-14 9:54 ` Tim Ruffing
2023-12-14 10:04 ` Eli Zaretskii
2023-12-14 10:37 ` Tim Ruffing
2023-12-14 11:19 ` Eli Zaretskii
2023-12-14 11:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-14 15:06 ` Tim Ruffing
2023-12-14 22:55 ` Stefan Kangas
2024-01-11 15:50 ` Tim Ruffing
2024-01-12 1:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 8:37 ` Eli Zaretskii
2024-01-12 9:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 11:46 ` Eli Zaretskii
2024-01-12 12:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 12:30 ` Eli Zaretskii
2024-01-12 13:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 14:12 ` Eli Zaretskii
2024-01-13 0:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13 6:59 ` Eli Zaretskii
2024-01-14 1:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 6:24 ` Eli Zaretskii
2024-01-14 8:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 9:33 ` Eli Zaretskii
2024-01-14 13:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 14:03 ` Eli Zaretskii
2024-01-14 14:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 14:55 ` Eli Zaretskii
2024-01-15 13:11 ` Tim Ruffing
2024-01-13 6:37 ` Stefan Kangas
2024-01-14 0:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 5:23 ` Stefan Kangas
2024-01-14 10:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 12:21 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 14:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 16:37 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 0:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 13:56 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 14:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=87mst6y9t3.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=67810@debbugs.gnu.org \
--cc=crypto@timruffing.de \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=manuel@ledu-giraud.fr \
--cc=stefankangas@gmail.com \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.