From: Axel Rauschmayer <rauschma-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Running Pandoc via JavaScript?
Date: Wed, 25 Aug 2021 06:31:21 -0700 (PDT) [thread overview]
Message-ID: <8cff6ffd-e85f-4937-a57c-b23093b72bben@googlegroups.com> (raw)
In-Reply-To: <5d75f991-ac8c-ef59-97ba-5edfc0adb57e-Jdbf3xiKgS8@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1800 bytes --]
Thanks for your reply!
These options are perfectly fine, I was mainly wondering if I was missing
anything simple and/or obvious.
My use case: Converting Markdown stored in files to HTML (one file at a
time).
On Wednesday, August 25, 2021 at 3:29:13 PM UTC+2 DSt...-Jdbf3xiKgS8@public.gmane.org wrote:
> On 8/25/21 4:57 AM, Axel Rauschmayer wrote:
> > I’d like to use Pandoc as a Markdown parser from JavaScript in Node.js.
> > I’m aware of the following options:
> >
> > * Running Pandoc as a shell script, providing input via stdin and
> > getting the output via stdout
> > * Running Pandoc via WebAssembly:
> https://github.com/y-taka-23/wasm-pandoc
> >
> > Any other tips or suggestions?
>
> What's wrong with those options and/or what are you trying to do? Any
> tips would be geared towards whatever issues you're trying to overcome.
>
> Daniel T. Staal
>
> --
> ---------------------------------------------------------------
> This email copyright the author. Unless otherwise noted, you
> are expressly allowed to retransmit, quote, or otherwise use
> the contents for non-commercial purposes. This copyright will
> expire 5 years after the author's death, or in 30 years,
> whichever is longer, unless such a period is in excess of
> local copyright law.
> ---------------------------------------------------------------
>
--
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/8cff6ffd-e85f-4937-a57c-b23093b72bben%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2699 bytes --]
next prev parent reply other threads:[~2021-08-25 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 8:57 Axel Rauschmayer
[not found] ` <8f9a1732-06bc-446d-a566-005a4f1ab9f7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-25 13:29 ` Daniel Staal
[not found] ` <5d75f991-ac8c-ef59-97ba-5edfc0adb57e-Jdbf3xiKgS8@public.gmane.org>
2021-08-25 13:31 ` Axel Rauschmayer [this message]
[not found] ` <8cff6ffd-e85f-4937-a57c-b23093b72bben-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-26 12:43 ` Leon Bartz
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=8cff6ffd-e85f-4937-a57c-b23093b72bben@googlegroups.com \
--to=rauschma-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).