public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: CesarJ M <cesarjorgemartinez-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Help when convert to html and odt after
Date: Wed, 27 Sep 2017 08:12:11 -0700 (PDT)	[thread overview]
Message-ID: <58168725-4d76-48c6-bfa6-be150744cdd9@googlegroups.com> (raw)
In-Reply-To: <20170926175824.GA30272@protagoras>


[-- Attachment #1.1: Type: text/plain, Size: 1517 bytes --]

I catch the error finally, is a error un md file.

Thanks!

El martes, 26 de septiembre de 2017, 19:58:27 (UTC+2), John MacFarlane 
escribió:
>
> I can't reproduce this either with pandoc dev or pandoc 
> 1.19.2.1. 
>
> pandoc -o my.dot << EOF 
> Text line 
>
> <h2>Index</h2> 
>
> <!-- MDTOC maxdepth:6 firsth1:1 numbering:0 flatten:0 bullets:1 
> updateOnSave:0 --> 
>
> ... (the index generated automatically using mdtoc) 
>
> <!-- /MDTOC --> 
> EOF 
>
> I get an ODT without any literal HTML. 
>
> There was a bug where raw HTML was passed literally to 
> ODT, but it was fixed in 2013. 
>
> Now, I suppose you've actually got some HTML where you 
> put "(the index generated automatically)". 
>
> Is it, by chance, indented by at least four spaces?  If so, 
> that could explain what we're seeing ... since pandoc would 
> parse an indented section as a code block rather than raw 
> HTML. 
>
>

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/58168725-4d76-48c6-bfa6-be150744cdd9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 2153 bytes --]

  reply	other threads:[~2017-09-27 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 15:40 CesarJ M
     [not found] ` <b9ec5527-9376-4057-bb3b-4d35aa05f27f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-25 15:53   ` John MacFarlane
     [not found]     ` <20170925155355.GC61612-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-09-26  7:46       ` CesarJ M
     [not found]         ` <82fdd7f8-d9c0-48ee-b386-959ae529b6ff-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-26 16:06           ` John MACFARLANE
     [not found]             ` <20170926160635.GH70046-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2017-09-26 17:01               ` CesarJ M
     [not found]                 ` <5cbd73d7-4603-41bf-a52a-2083b706b41f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-26 17:09                   ` CesarJ M
2017-09-26 17:10                   ` CesarJ M
2017-09-26 17:58           ` John MACFARLANE
2017-09-27 15:12             ` CesarJ M [this message]
2017-09-26  7:50       ` CesarJ M

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=58168725-4d76-48c6-bfa6-be150744cdd9@googlegroups.com \
    --to=cesarjorgemartinez-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).