public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Gregory D. Weber" <spottedmetal-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: YAML metadata block + HTML input file
Date: Tue, 07 Dec 2021 18:57:43 -0500	[thread overview]
Message-ID: <cf4a051b561c0c09b9168da64de668c5b3458cae.camel@gmail.com> (raw)
In-Reply-To: <yh480kczm82mn9.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>

On Tue, 2021-12-07 at 12:19 -0800, John MacFarlane wrote:
> Since YAML metadata is a markdown extension, you can't include
> it in HTML input.
> 

Understood, thanks.

I was trying to use HTML source because the file contained <form> and
<canvas> elements, which, when the input file was turned into markdown,
were rendered as formatted code instead of being copied straight through.

However, I've been able to fix this with proper indenting, ```{=html5},
and --from=markdown-smart.

It is working well now, with markdown source files, and I don't need the
extra YAML files!



      parent reply	other threads:[~2021-12-07 23:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 19:09 Gregory D. Weber
     [not found] ` <91104b9d67992600aa9acc26fa32b2cfcde60056.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-12-07 20:19   ` John MacFarlane
     [not found]     ` <yh480kczm82mn9.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-12-07 21:02       ` Martin Hepp
     [not found]         ` <76E923B2-4D96-4654-8D11-B5B2A261C21F-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-12-08  2:44           ` John MacFarlane
2021-12-07 23:57       ` Gregory D. Weber [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=cf4a051b561c0c09b9168da64de668c5b3458cae.camel@gmail.com \
    --to=spottedmetal-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=jgm-TVLZxgkOlNX2fBVCVOL8/A@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).