public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Amy de Buitléir" <amy-x92Y4IBCQKU6Cx7ujrKbww@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How to make writeNative include metadata?
Date: Tue, 3 Jan 2023 13:22:16 -0800 (PST)	[thread overview]
Message-ID: <ab602db1-e8d7-4bd5-b077-0f454edc6e3fn@googlegroups.com> (raw)


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

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.

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

             reply	other threads:[~2023-01-03 21:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 21:22 Amy de Buitléir [this message]
     [not found] ` <ab602db1-e8d7-4bd5-b077-0f454edc6e3fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-03 22:02   ` John MacFarlane

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=ab602db1-e8d7-4bd5-b077-0f454edc6e3fn@googlegroups.com \
    --to=amy-x92y4ibcqku6cx7ujrkbww@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).