all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: manuel@ledu-giraud.fr, emacs-devel@gnu.org
Subject: Re: DocView, mupdf and librsvg
Date: Sat, 07 Jan 2023 15:31:01 +0200	[thread overview]
Message-ID: <83lemesc8a.fsf@gnu.org> (raw)
In-Reply-To: <87cz7q352t.fsf@gmx.net> (message from Stephen Berman on Sat, 07 Jan 2023 13:24:42 +0100)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: "emacs-devel" <emacs-devel@gnu.org>
> Date: Sat, 07 Jan 2023 13:24:42 +0100
> 
> On Sat, 07 Jan 2023 13:07:22 +0100 Manuel Giraud <manuel@ledu-giraud.fr> wrote:
> 
> > Hi,
> >
> > From some month now, to read PDF, DocView has switched from producing
> > PNG files for its page cache to producing SVG files.  I think it is a
> > good idea but I have found a bug (that is outside the scope of Emacs
> > that's why I'm reporting here): mutool could generate SVG files that
> > librsvg is not able to read back.
> >
> > FTR, I'm using mupdf 1.21.1 and librsvg 2.54.5.  I've attached a sample
> > PDF and the produced SVG if you want to test on your setting.
> 
> Yes, this is apparently a bug in how mutool processes "<" since at least
> version 1.21.0, see also bug#60308.
> 
> > I think it would be wise to defaults `doc-view-mupdf-use-svg' to nil in
> > the upcoming Emacs 29.

I think instead of changing the default unconditionally, we should
probe the version of mutool, and change it only for affected versions.
Would someone like to propose a patch along those lines?



  reply	other threads:[~2023-01-07 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07 12:07 DocView, mupdf and librsvg Manuel Giraud
2023-01-07 12:24 ` Stephen Berman
2023-01-07 13:31   ` Eli Zaretskii [this message]
2023-01-07 15:03     ` Manuel Giraud
2023-01-08 10:30       ` Stephen Berman

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=83lemesc8a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    --cc=stephen.berman@gmx.net \
    /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.