From: Martin Post <martinpostberlin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Parse metadata in defaults files as Markdown?
Date: Sat, 30 Sep 2023 02:03:16 -0700 (PDT) [thread overview]
Message-ID: <7f96f150-6981-4163-8f6d-54de50a90c4fn@googlegroups.com> (raw)
In-Reply-To: <87r0mgof6d.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1897 bytes --]
Thank you, Albert! While this looks feasible & helpful, I have now (after
many years of using Pandoc…) finally “seen the light”, and I’ll separate
default files and metadata files, as it should be. 😊
Albert Krewinkel schrieb am Freitag, 29. September 2023 um 23:14:28 UTC+2:
>
> Martin Post <martinpo...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > In a Pandoc document’s YAML metadata block, or in a Pandoc metadata
> file, I can do this:
> >
> > variable1: __content__
> >
> > …and it will be rendered as <strong>content</strong> for HTML.
> >
> > Doing this in a Pandoc DEFAULTS file:
> >
> > metadata:
> > variable1: __content__
> >
> > …will render $variable1$ as “__content__”
> >
> > So – is it possible to have metadata in a defaults file interpreted as
> Markdown?
>
> I think the only way would be to write a Lua filter that convert strings
> to Inlines.
>
> E.g.:
>
>
> local strings2md
> strings2md = function (meta)
> for key, value in pairs(meta) do
> if pandoc.utils.type(value) == 'string' then
> -- Convert strings to Markdown
> local blocks = pandoc.read(value).blocks
> meta[key] = pandoc.utils.blocks_to_inlines(blocks)
> elseif pandoc.utils.type(value) == 'List' then
> -- Recurse on lists
> meta[key] = strings2md(value)
> end
> end
>
> return meta
> end
>
> Meta = strings2md
>
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>
--
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/7f96f150-6981-4163-8f6d-54de50a90c4fn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2689 bytes --]
next prev parent reply other threads:[~2023-09-30 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 16:20 Martin Post
[not found] ` <a4843b38-f508-4d55-8dd0-35136f401bd1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-09-29 18:37 ` Albert Krewinkel
[not found] ` <87r0mgof6d.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-09-30 9:03 ` Martin Post [this message]
2023-10-01 10:50 ` Markdown in JSON (was: Parse metadata in defaults files as Markdown?) BPJ
[not found] ` <CADAJKhC6T=UHG49Rtd40nYsQFgfMxuiwyjqK3A+9CQ0QwjYXzQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-10-02 19:08 ` Albert Krewinkel
[not found] ` <87edicolz7.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-10-05 10:14 ` BPJ
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=7f96f150-6981-4163-8f6d-54de50a90c4fn@googlegroups.com \
--to=martinpostberlin-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).