public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Russ <info-ckBjHRpK5r9MPTj2movljOTW4wlIGRCZ@public.gmane.org>
To: 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: Mon, 24 Jan 2022 02:46:03 -0800 (PST)	[thread overview]
Message-ID: <761a5c9b-aa9e-4164-90b2-082085dbc85an@googlegroups.com> (raw)
In-Reply-To: <yh480kwnis7udi.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>


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

Thanks for your suggestion John, I did try this and it did work, so 
apologies. I realised it had to be something to do with our build script. 
We have it working now so many thanks for everyone with their help.

On Friday, 21 January 2022 at 19:37:53 UTC John MacFarlane wrote:

>
> > 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.
>

-- 
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/761a5c9b-aa9e-4164-90b2-082085dbc85an%40googlegroups.com.

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

      parent reply	other threads:[~2022-01-24 10:46 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
     [not found]                     ` <yh480kwnis7udi.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-01-24 10:46                       ` Russ [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=761a5c9b-aa9e-4164-90b2-082085dbc85an@googlegroups.com \
    --to=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).