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: Re: customize to handle image not exists
Date: Sat, 1 Apr 2023 14:47:05 +0800 (GMT+08:00)	[thread overview]
Message-ID: <u08k1a$du1$1@ciao.gmane.io> (raw)
In-Reply-To: <8826C552-7F45-499B-A4A2-59ADA868D720@gmail.com>

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

You are right. I removed "alt" in my filter.

But replacing images with description quietly could result in an unwanted document if people neglect the warning and do not check the documeng carefully.
So IMHO an error without generating the document is better, as people definitely would notice the warning and error what are missing. And an option to enable this raplacing behavior would be even better, since people know and agree what may happen when they set it.

-- 


John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 写入消息新闻:
> 
> 
>> On Mar 30, 2023, at 7:51 PM, jiewuza <jiewuza-9Onoh4P/yGk-XMD5yJDbdMSQIYZ4X/+iSw@public.gmane.orgrg> wrote:
>> 
>> Well, I am still confused about the difference between the two processes. 

----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/u08k1a%24du1%241%40ciao.gmane.io.

      reply	other threads:[~2023-04-01  6:47 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
2023-04-01  6:47       ` jiewuza [this message]

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='u08k1a$du1$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).