From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Russ <info-ckBjHRpK5r9MPTj2movljOTW4wlIGRCZ@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Reading a multi line yaml key - results in text surrounded in html <p> tags?
Date: Fri, 21 Jan 2022 11:37:29 -0800 [thread overview]
Message-ID: <yh480kwnis7udi.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <899d9fd4-dfae-48d7-ab33-3d55b81f540cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
> description: |
> Some long, perhaps multi-line description.
>
> Sadly this *does not* appear in the epub (2) metadata when we build it, it
> used to work. This does seem like some sort of bug? Because if we use
> commas to surround the description text or use '>-' as suggested by
> Albert, the description *does* appear in the epub metadata. However, we
> have a lot of markdown which use the '|' formatting for multi-line so I'd
> rather not have to change this is I don't have to.
It works fine when I try it...
If you want us to look into it, upload a minimal markdown
source and exact command (and pandoc version) you used,
together with the resulting epub.
next prev parent reply other threads:[~2022-01-21 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 15:21 Russ
[not found] ` <e17cd72d-2900-476c-a945-77d9e2e722bcn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-20 21:37 ` John MacFarlane
2022-01-20 21:41 ` John MacFarlane
[not found] ` <yh480ksfti2igy.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-01-21 8:24 ` BPJ
[not found] ` <CADAJKhBEViWZsLRRtAr78yn3Q3fSZswg85vut21vkrpfsvszXQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-01-21 9:01 ` Russ
[not found] ` <cef14d70-eda9-4555-85ec-a39e71fabf29n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-21 9:35 ` Albert Krewinkel
2022-01-21 10:27 ` Albert Krewinkel
[not found] ` <87zgnpl6wc.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-01-21 16:37 ` Russ
[not found] ` <899d9fd4-dfae-48d7-ab33-3d55b81f540cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-21 19:37 ` John MacFarlane [this message]
[not found] ` <yh480kwnis7udi.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-01-24 10:46 ` Russ
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=yh480kwnis7udi.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=info-ckBjHRpK5r9MPTj2movljOTW4wlIGRCZ@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).