From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How to make writeNative include metadata?
Date: Tue, 3 Jan 2023 14:02:57 -0800 [thread overview]
Message-ID: <FC6C8CCA-59EE-43BF-82C7-582EEFCE2F6A@gmail.com> (raw)
In-Reply-To: <ab602db1-e8d7-4bd5-b077-0f454edc6e3fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
You need to set `writerTemplate` to `Just “”`.
We removed the old `writerStandalone` on grounds that it is redundant with `writerTemplate`. Of course, this is a bit odd for formats like native that don’t have templates, but in that case as long as `writerTemplate` is a Just value it will consider it standalone.
> On Jan 3, 2023, at 1:22 PM, Amy de Buitléir <amy-x92Y4IBCQKU6Cx7ujrKbww@public.gmane.org> wrote:
>
> The command `pandoc myfile --to=native --standalone` produces output that includes the metadata.
>
> My program needs to sereialise and deserialise Pandoc documents. I assume could use the native file for this. However, the output produced by`Text.Pandoc.Writers.writeNative` does not include metadata. I don't see a "standalone" option or anything similar in `WriterOptions`.
>
> Is there a way to make `writeNative` include the metadata?
>
>
> --
> 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/ab602db1-e8d7-4bd5-b077-0f454edc6e3fn%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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/FC6C8CCA-59EE-43BF-82C7-582EEFCE2F6A%40gmail.com.
prev parent reply other threads:[~2023-01-03 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 21:22 Amy de Buitléir
[not found] ` <ab602db1-e8d7-4bd5-b077-0f454edc6e3fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-03 22:02 ` John MacFarlane [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=FC6C8CCA-59EE-43BF-82C7-582EEFCE2F6A@gmail.com \
--to=fiddlosopher-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).