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: Fri, 21 Jan 2022 01:01:35 -0800 (PST)	[thread overview]
Message-ID: <cef14d70-eda9-4555-85ec-a39e71fabf29n@googlegroups.com> (raw)
In-Reply-To: <CADAJKhBEViWZsLRRtAr78yn3Q3fSZswg85vut21vkrpfsvszXQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


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

Firstly, thanks to everyone for their help and suggestions. Sorry John, I 
could not go back to an older version (homebrew). So I guess something else 
has changed? Perhaps a fuller explanation might help:

What we are doing is extracting some YAML frontmatter metadata into 
variables for a bash script. We use the following (simplified) command 
pandoc --lua-filter *remove-meta-html.lua* -f markdown+yaml_metadata_block 
 book-metadata-file.md --template *meta-data.template*  --to html -o 
file.tmp

*remove-meta-html.lua*
function Pandoc(doc)
 for k,v in pairs(doc.meta) do
  if v.t == 'MetaBlocks' then
   for i,x in ipairs(v) do
     if x.t == 'Para' then v[i] = pandoc.Plain(v[i].c) end
   end 
  end
 end
 return doc
end


The *meta-data.template* has lines like:
$if(volume)$BOOK_VOLUME="$volume$"$endif$

We then read the variables from the created file.tmp. 

This has worked for some time, can anyone one see anything that would need 
to be corrected or could have changed in recent versions?
On Friday, 21 January 2022 at 08:24:36 UTC BP wrote:

> Or if needed use single quotes around the value to protect punctuation 
> marks, noting that to include a single quote in a YAML single-quoted string 
> you use two single quotes, as in `'don''t'`.
>
> Den tors 20 jan. 2022 22:42John MacFarlane <j...-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> skrev:
>
>>
>> One workaround is to use a Lua filter that
>> applies pandoc.utils.stringify to the contents of the
>> 'volume' field in metadata.
>>
>> Russ <in...-ckBjHRpK5r9MPTj2movljOTW4wlIGRCZ@public.gmane.org> writes:
>>
>> > pandoc 2.17.0.1
>> > Reading a multi line YAML front matter and outputing the text now gets 
>> a 
>> > text string with html <p> tags.
>> >
>> > For example
>> > ```yaml
>> > volume: | Volume 16: A Subtitle ```
>> > Should produce:
>> > "Volume 16: A Subtitle"
>> >
>> > But now produces:
>> > "<p>Volume 16: A Subtitle</p>"
>> >
>> > Is there a way to avoid these html tags or is it a bug? I cannot say 
>> for 
>> > sure that this has changed in this specific version, but it is 
>> certainly 
>> > quite a recent change.
>> >
>> > -- 
>> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/e17cd72d-2900-476c-a945-77d9e2e722bcn%40googlegroups.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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/yh480ksfti2igy.fsf%40johnmacfarlane.net
>> .
>>
>

-- 
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/cef14d70-eda9-4555-85ec-a39e71fabf29n%40googlegroups.com.

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

  parent reply	other threads:[~2022-01-21  9:01 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 [this message]
     [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

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=cef14d70-eda9-4555-85ec-a39e71fabf29n@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).