public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
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 09:03:56 -0700	[thread overview]
Message-ID: <17DDA913-35EA-4F94-99EB-378C0572C454@gmail.com> (raw)
In-Reply-To: <u0328r$15ia$1@ciao.gmane.io>

No, it isn't customizable.

> On Mar 29, 2023, at 9:12 PM, jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org> wrote:
> 
> 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?
> 
> -- 
> 
> 
> -- 
> 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/u0328r%2415ia%241%40ciao.gmane.io.


  reply	other threads:[~2023-03-30 16:03 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 [this message]
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=17DDA913-35EA-4F94-99EB-378C0572C454@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).