From: jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: customize to handle image not exists
Date: Fri, 31 Mar 2023 10:51:51 +0800 (GMT+08:00) [thread overview]
Message-ID: <u05hs8$n7c$1@ciao.gmane.io> (raw)
In-Reply-To: <17DDA913-35EA-4F94-99EB-378C0572C454@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]
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?
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.
BTW, I did not see the description in the pdf for the non-existing image. Is it a bug?
--
John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 写入消息新闻:
> No, it isn't customizable.
>
>> On Mar 29, 2023, at 9:12 PM, jiewuza <jiewuza-9Onoh4P/yGk-XMD5yJDbdMSQIYZ4X/+iSw@public.gmane.orgrg> wrote:
----Android NewsGroup Reader----
http://www.piaohong.tk/newsgroup
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/u05hs8%24n7c%241%40ciao.gmane.io.
next prev parent reply other threads:[~2023-03-31 2:51 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 [this message]
2023-03-31 5:37 ` John MacFarlane
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='u05hs8$n7c$1@ciao.gmane.io' \
--to=jiewuza-9onoh4p/ygk@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).