public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Isaac Van Doren <ivando5522-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Adding a reader for Cooklang and a question about Megaparsec
Date: Sun, 15 Jan 2023 19:07:33 -0800 (PST)	[thread overview]
Message-ID: <08647ee9-9616-482c-bae8-2657d16df33fn@googlegroups.com> (raw)


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

Hello,

*About Cooklang:*
I am interested in adding a reader to Pandoc for the Cook 
<https://cooklang.org> markdown language. Cooklang is a concise, 
standardized way to format recipes. You write down the instructions for a 
recipe and whenever you mention a new ingredient or piece of cookware you 
annotate it and can specify the quantity and more. Then that document can 
be rendered by a variety of tools (e.g. a vscode extension 
<https://marketplace.visualstudio.com/items?itemName=isaacvando.cookrender> 
I wrote) into a consistent format. This language seems like a natural 
addition to Pandoc and one that the Cooklang community would benefit from 
greatly. 

I've written a parser <https://github.com/isaacvando/cooklang-hs> for Cook 
in Haskell which would be a good start. It complies with the official 
Cooklang canonical tests. 

*Questions:*
Currently my parser uses Megaparsec. Do I need to refactor it to use Parsec 
instead or is it okay to add Megaparsec as a dependency?

Currently my parser uses String instead of Text. Is it necessary for the 
parser to use Text to be used by Pandoc or could I get away with the reader 
converting its Text input to String when parsing?

Is there anything else I should know before I start working on a PR? Does 
this seem like a suitable addition to Pandoc?

Thanks!
Isaac Van Doren

-- 
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/08647ee9-9616-482c-bae8-2657d16df33fn%40googlegroups.com.

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

             reply	other threads:[~2023-01-16  3:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16  3:07 Isaac Van Doren [this message]
     [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

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=08647ee9-9616-482c-bae8-2657d16df33fn@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).