From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: 60308-done@debbugs.gnu.org, stephen.berman@gmx.net,
yantar92@posteo.net, bugs@gnu.support
Subject: bug#60308: 30.0.50; Can't read some PDF files any more
Date: Fri, 06 Jan 2023 14:55:56 +0200 [thread overview]
Message-ID: <83o7rbvn37.fsf@gnu.org> (raw)
In-Reply-To: <371ba1d0bef310cee63c@heytings.org> (message from Gregory Heytings on Fri, 06 Jan 2023 12:22:44 +0000)
> Date: Fri, 06 Jan 2023 12:22:44 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: Eli Zaretskii <eliz@gnu.org>, 60308@debbugs.gnu.org, yantar92@posteo.net,
> bugs@gnu.support
>
>
> >> Thanks. So this looks like a mutool bug, which generates incorrect SGV
> >> files, right?
> >
> > Yep. I just converted the PDF to SVG with mutool 1.19.0 and the
> > resulting image displays correctly and there is no "<" in the file.
> >
>
> Okay, so this bug should be reported to mupdf instead
They already released version 1.21.1, maybe it fixes this problem?
> and this one can be closed.
Right, done.
next prev parent reply other threads:[~2023-01-06 12:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 21:39 bug#60308: 30.0.50; Can't read some PDF files any more Jean Louis
2023-01-05 16:50 ` Jean Louis
2023-01-05 17:12 ` Ihor Radchenko
2023-01-05 18:31 ` Eli Zaretskii
2023-01-05 20:58 ` Gregory Heytings
2023-01-06 6:40 ` Eli Zaretskii
2023-01-06 9:58 ` Stephen Berman
2023-01-06 10:10 ` Gregory Heytings
2023-01-06 10:22 ` Gregory Heytings
2023-01-06 12:51 ` Jean Louis
2023-01-06 10:32 ` Stephen Berman
2023-01-06 11:12 ` Gregory Heytings
2023-01-06 11:44 ` Stephen Berman
2023-01-06 12:04 ` Eli Zaretskii
2023-01-06 12:22 ` Gregory Heytings
2023-01-06 12:55 ` Eli Zaretskii [this message]
2023-01-06 20:38 ` Stephen Berman
2023-01-07 15:48 ` Manuel Giraud
2023-01-07 18:25 ` Gregory Heytings
2023-01-07 18:35 ` Eli Zaretskii
2023-01-07 18:45 ` Gregory Heytings
2023-01-07 18:37 ` Manuel Giraud
2023-01-07 18:59 ` Gregory Heytings
2023-01-07 20:07 ` Eli Zaretskii
2023-01-07 20:58 ` Manuel Giraud
2023-01-07 22:19 ` Gregory Heytings
2023-01-08 12:57 ` Manuel Giraud
2023-01-10 10:59 ` Gregory Heytings
2023-01-11 10:35 ` Manuel Giraud
2023-01-11 16:26 ` Gregory Heytings
2023-01-11 17:03 ` Eli Zaretskii
2023-01-11 19:33 ` Gregory Heytings
2023-01-14 8:53 ` Eli Zaretskii
2023-01-07 20:53 ` Manuel Giraud
2023-01-06 12:48 ` Jean Louis
2023-01-05 23:54 ` Jean Louis
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o7rbvn37.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60308-done@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=gregory@heytings.org \
--cc=stephen.berman@gmx.net \
--cc=yantar92@posteo.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).