public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Antonio Piccolboni <antonio-JxjfdnYl9jjeHsu01rjbxw@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: missing figures in latex/pdf output
Date: Wed, 28 Sep 2022 08:48:58 -0700	[thread overview]
Message-ID: <C357174C-A074-4646-9149-B3102B6FAB8F@piccolboni.info> (raw)
In-Reply-To: <ADAB9DB0-E0D5-4933-A83A-589C7EF14F61-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>



> On Sep 27, 2022, at 11:04 PM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> 
> 
>> On Sep 27, 2022, at 8:41 PM, Antonio Piccolboni <piccolbo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> 
>> Until now I had assumed that markdown was a superset of html. It wasn't a pandoc extension, it is what the Markdown format says: you can mix in html when markdown syntax is not enough. It was the backstop that made it easy to pick markdown without future regret.  So not converting the html in markdown is not in keeping with the format definition according to my assumptions. That said, markdown doesn't have an official standard and I may very well be wrong. 
> 
> Well, original Markdown.pl was just a markdown -> HTML converter, with no aspirations to support any other formats.  So the HTML was passed through literally to the output, and that is what we still do.  I think either approach would be equally consistent with the original.  But the literal passthrough approach is what we stick with, for a number of reasons.
> 
> The main one is that HTML is strictly more expressive than what can be represented with pandoc's types. Allowing HTML in markdown was a way of avoiding expressive limitations; if you want to do something fancy, you can pass through HTML. If we parsed the HTML and re-rendered, we'd often lose something (although over time pandoc's types have gotten more expressive, they are still not as expressive as HTML).

It makes sense.

> 
>> In my specific case the solution is to use just markdown as Martin suggested. The reason I had switched to html is that, for some reason, the calibre epub viewer ignores the caption when using the Markdown syntax. Apple books doesn't have this problem. So I will just ignore the calibre viewer. I had a few other uses for html tags like sup and span, but I can work around those, mostly. Thanks!
> 
> You could use a filter to generate special HTML from pandoc figures, for HTML output only.
> 
> Note also that pandoc's markdown includes syntax for sup and span.


Thanks, my bad for not RFM. 


Antonio



> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google Groups "pandoc-discuss" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/pandoc-discuss/-yzmZBWG818/unsubscribe.
> To unsubscribe from this group and all its topics, 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/ADAB9DB0-E0D5-4933-A83A-589C7EF14F61%40gmail.com.

-- 
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/C357174C-A074-4646-9149-B3102B6FAB8F%40piccolboni.info.


  parent reply	other threads:[~2022-09-28 15:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 20:26 Antonio Piccolboni
     [not found] ` <8bd75451-cad3-4a83-80e3-7a983091bcadn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-27 21:06   ` John MacFarlane
     [not found]     ` <D0DAD6A1-3B30-4F46-8FAB-5F484F65D700-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-09-28  1:11       ` Martin Hepp
     [not found]         ` <1AF44C44-B3C7-4872-BA10-980739F20F72-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-09-28  3:41           ` Antonio Piccolboni
     [not found]             ` <c2b0c867-fb97-4aee-86f4-fcf160ff0303n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-28  6:04               ` John MacFarlane
     [not found]                 ` <ADAB9DB0-E0D5-4933-A83A-589C7EF14F61-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-09-28 15:48                   ` Antonio Piccolboni [this message]
     [not found]                     ` <C357174C-A074-4646-9149-B3102B6FAB8F-JxjfdnYl9jjeHsu01rjbxw@public.gmane.org>
2022-10-02 16:01                       ` 'Marek Stepanek' via pandoc-discuss

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=C357174C-A074-4646-9149-B3102B6FAB8F@piccolboni.info \
    --to=antonio-jxjfdnyl9jjehsu01rjbxw@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).