From: Isaac Van Doren <ivando5522-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Adding a reader for Cooklang and a question about Megaparsec
Date: Thu, 19 Jan 2023 08:50:12 -0800 (PST) [thread overview]
Message-ID: <fec9d677-eb00-4da1-9199-2b480c67f1e4n@googlegroups.com> (raw)
In-Reply-To: <CC6D5774-540D-4B62-B087-AD01C40CC502-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 856 bytes --]
Alright, thanks!
On Thursday, January 19, 2023 at 10:44:25 AM UTC-6 fiddlosopher wrote:
> I think that cooklang may be a bit too specialized to add as a regular
> reader. We try to cover commonly used formats that are general purpose.
>
> However, this is a perfect use case for a custom reader, as Albert
> suggests.
>
> There is some helpful documentation on the website, including examples:
>
> https://pandoc.org/custom-readers.html
>
>
--
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/fec9d677-eb00-4da1-9199-2b480c67f1e4n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1648 bytes --]
prev parent reply other threads:[~2023-01-19 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 3:07 Isaac Van Doren
[not found] ` <08647ee9-9616-482c-bae8-2657d16df33fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-18 23:26 ` Albert Krewinkel
[not found] ` <87lelzmn0l.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-01-19 10:19 ` BPJ
2023-01-19 16:44 ` John MacFarlane
[not found] ` <CC6D5774-540D-4B62-B087-AD01C40CC502-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-01-19 16:50 ` Isaac Van Doren [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=fec9d677-eb00-4da1-9199-2b480c67f1e4n@googlegroups.com \
--to=ivando5522-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).