From: Lars Ingebrigtsen <larsi@gnus.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: 58041@debbugs.gnu.org
Subject: bug#58041: [PATCH] docview: Use svg images when using mupdf for conversion
Date: Sat, 24 Sep 2022 14:10:08 +0200 [thread overview]
Message-ID: <871qs1ynvj.fsf@gnus.org> (raw)
In-Reply-To: <87k05t848c.fsf@gmail.com> (Visuwesh's message of "Sat, 24 Sep 2022 15:48:59 +0530")
Visuwesh <visuweshm@gmail.com> writes:
> Attached patch makes mupdf produce svg images rather than png when svg
> support is available. This makes a noticeable improvement in image
> quality when zooming in. This also improves epub, odt, docx,
> etc. rendering since they also end up using mupdf.
> I'm not sure if this is NEWS worthy though.
>
> I've also attached two images before.png and after.png to illustrate the
> difference in rendering before and after applying this patch.
Looks good; pushed to Emacs 29.
next prev parent reply other threads:[~2022-09-24 12:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 10:18 bug#58041: [PATCH] docview: Use svg images when using mupdf for conversion Visuwesh
2022-09-24 12:10 ` Lars Ingebrigtsen [this message]
[not found] ` <jwva62yxevs.fsf-monnier+emacs@gnu.org>
2023-01-08 6:09 ` Visuwesh
2023-01-09 14:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-09 16:32 ` Visuwesh
2023-01-09 17:18 ` Gregory Heytings
2023-01-09 23:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-12 6:43 ` Visuwesh
2023-01-12 8:11 ` Eli Zaretskii
2023-01-12 8:20 ` Visuwesh
2023-01-12 8:48 ` Eli Zaretskii
2023-01-12 16:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-14 8:33 ` Eli Zaretskii
2023-01-12 16:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-12 16:47 ` Visuwesh
2023-01-12 21:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=871qs1ynvj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58041@debbugs.gnu.org \
--cc=visuweshm@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.