From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: customize to handle image not exists
Date: Thu, 30 Mar 2023 22:37:20 -0700 [thread overview]
Message-ID: <8826C552-7F45-499B-A4A2-59ADA868D720@gmail.com> (raw)
In-Reply-To: <u05hs8$n7c$1@ciao.gmane.io>
> On Mar 30, 2023, at 7:51 PM, jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org> wrote:
>
> Well, I am still confused about the difference between the two processes.
>
> In the process "html->latex->pdf", I use pandoc to convert html to latex first, and call latex engine to produce pdf manually. While in the process "html->pdf", pandoc
> does everything by itself.
>
> I passed the same cli parameters to pandoc during the two processes. The final pdfs are all the same except for the non-existing images. So I guess in "html->pdf" it also generates latex temporary file first before producing pdf, right?
Yes.
> If the answer is yes, it seems an inconsistent behavior of pandoc treating resources, which could surprise users.
> IMHO, a warning is enough, but do not modify the content by replacing image with description.
Well, then the latex process would raise an error, without special custom handling (as you seem to have). I think current behavior is better.
>
> BTW, I did not see the description in the pdf for the non-existing image. Is it a bug?
Maybe there was no alt text in the input?
next prev parent reply other threads:[~2023-03-31 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 4:12 jiewuza
2023-03-30 16:03 ` John MacFarlane
2023-03-31 2:51 ` jiewuza
2023-03-31 5:37 ` John MacFarlane [this message]
2023-04-01 6:47 ` jiewuza
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=8826C552-7F45-499B-A4A2-59ADA868D720@gmail.com \
--to=fiddlosopher-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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.
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 NNTP newsgroup(s).