public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Björn Stenborg" <bjorn.stenborg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Processing multiple documents on stdin
Date: Wed, 18 Jan 2023 04:20:33 -0800 (PST)	[thread overview]
Message-ID: <f0452de0-6214-43fd-b090-de2fc81c3f2an@googlegroups.com> (raw)


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

Our toolchain needs to perform separate markdown -> HTML conversion using 
pandoc for a large number of table cells (for various reasons), which for 
some documents currently entails making thousands of calls to the pandoc 
binary.

It would be really nice to be able to stream multiple documents on stdin to 
pandoc and get separate outputs. This is not currently supported e.g. by 
passing a file separator control character? Are there any other ways to 
achieve this?

We could spin up pandoc as a web server but this would be fairly awkward 
and i assume come with some additional overhead that isn't really needed 
since it will just be used locally anyway.

-- 
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/f0452de0-6214-43fd-b090-de2fc81c3f2an%40googlegroups.com.

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

             reply	other threads:[~2023-01-18 12:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 12:20 Björn Stenborg [this message]
     [not found] ` <f0452de0-6214-43fd-b090-de2fc81c3f2an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-18 14:53   ` 'William Lupton' via pandoc-discuss

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=f0452de0-6214-43fd-b090-de2fc81c3f2an@googlegroups.com \
    --to=bjorn.stenborg-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).