unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Visuwesh <visuweshm@gmail.com>
Cc: 62713@debbugs.gnu.org, Gregor Zattler <grfz@gmx.de>,
	Tassilo Horn <tsdh@gnu.org>
Subject: bug#62713: 29.0.60; DocView shows wrong conversion indicator when configured to use svg images
Date: Tue, 26 Sep 2023 04:43:05 -0700	[thread overview]
Message-ID: <CADwFkmmU8t9VXxbM7Wx_OZqmi0aBF0GZNNWN8EMp-mY5WdTyMQ@mail.gmail.com> (raw)
In-Reply-To: <87edimmncq.fsf@gmail.com>

Visuwesh <visuweshm@gmail.com> writes:

> [திங்கள் செப்டம்பர் 25, 2023] Visuwesh wrote:
>
>> It is better solved by writing a separate pdf->svg converter function.
>> Right now, the svg conversion is tacked on top of pdf->png converter
>> function used for MuPDF.  This was done because I thought only MuPDF
>> supported pdf->svg conversion but later I was informed that poppler has
>> utilities to do too.
>
> And looks like the poppler utility pdftocairo does not work the doc-view
> expects it to when generating svg images.  AFAICT, there is no way to
> make pdftocairo to generate a svg image per page like other tools do.  I
> cannot loop either as there is also no way to know the number of pages
> beforehand.  The png function also has hacks since pdftocairo is not
> cooperative, and changing doc-view to not use
> doc-view--image-file-pattern does not seem to be easy.  I attach the
> patch named "doc-view-general-svg-wip.patch" which has my WIP and it
> works just fine for MuPDF.
>
> This particular problem can be easily solved by the following simple
> patch instead:

Tassilo, could you perhaps take a look at this patch?





  reply	other threads:[~2023-09-26 11:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 16:02 bug#62713: 29.0.60; DocView shows wrong conversion indicator when configured to use svg images Gregor Zattler
2023-09-24 23:31 ` Stefan Kangas
2023-09-25  4:30   ` Visuwesh
2023-09-25  8:20     ` Stefan Kangas
2023-09-25 12:47     ` Visuwesh
2023-09-26 11:43       ` Stefan Kangas [this message]
2023-09-29  9:34         ` Tassilo Horn
2023-09-29  9:43           ` Stefan Kangas
2023-09-29 14:55             ` Visuwesh
2023-10-01 13:00               ` Stefan Kangas

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=CADwFkmmU8t9VXxbM7Wx_OZqmi0aBF0GZNNWN8EMp-mY5WdTyMQ@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=62713@debbugs.gnu.org \
    --cc=grfz@gmx.de \
    --cc=tsdh@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 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).