public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: customize to handle image not exists
Date: Thu, 30 Mar 2023 12:12:50 +0800 (GMT+08:00)	[thread overview]
Message-ID: <u0328r$15ia$1@ciao.gmane.io> (raw)

[-- Attachment #1: Type: text/plain, Size: 490 bytes --]

I use pandoc to convert html to pdf with my personal latex documentclass, in which images not exists would be replaced with boxes.

For
```
<img src="not-exists.jpg">
```
if I convert it to latex first, and then to pdf, everything works as expected.

But if I convert it to pdf directly, pandoc reports a warning: could not fetch resource, replacing image with description.

I hope it does what the "html->latex->pdf" process did, without checking the resource. Is this customizable?

-- 


             reply	other threads:[~2023-03-30  4:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  4:12 jiewuza [this message]
2023-03-30 16:03 ` John MacFarlane
2023-03-31  2:51   ` jiewuza
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='u0328r$15ia$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).