public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Harsh Donga <harsh-7+aFW328pE6p1wGUEcWPqti2O/JbrIOy@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: FIguring out pandoc AST and types
Date: Thu, 9 Sep 2021 01:45:55 -0700 (PDT)	[thread overview]
Message-ID: <4bd5ecbc-bd1d-442a-9558-6724174f77fcn@googlegroups.com> (raw)


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


Okay, being new to Haskell some of the questions might seem vague and some 
straightforward to you, I apologize in advance for that.

1. How can I create pandoc type variables, where exactly do I look if I 
want to make a table object purely using Haskell then convert it to JSON 
AST/other formats
2. How can I convert my own JSON (storing elements analogous to HTML) to 
pandoc AST
3. is there any way possible to make pandoc type variables using other 
languages like JS, Python...


Few more questions as follow-ups to these, your help is appreciated a lot!

-- 
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/4bd5ecbc-bd1d-442a-9558-6724174f77fcn%40googlegroups.com.

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

             reply	other threads:[~2021-09-09  8:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09  8:45 Harsh Donga [this message]
     [not found] ` <4bd5ecbc-bd1d-442a-9558-6724174f77fcn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-09 17:20   ` John MacFarlane
     [not found]     ` <m24kat3btu.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-09-14 12:28       ` Harsh Donga
2021-09-14 12:30       ` Harsh Donga
     [not found]         ` <3a59eb3c-352f-49f4-89f8-465aa7e86750n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-14 23:39           ` John MacFarlane
     [not found]             ` <yh480k35q63exs.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-09-16 11:52               ` Harsh Donga
     [not found]                 ` <68431aed-736c-425d-8745-14ffdc5468a9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-16 16:40                   ` John MacFarlane
     [not found]                     ` <m2ilz0lbie.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-09-17  4:18                       ` Harsh Donga
     [not found]                         ` <4b3e7960-d144-44e0-9b48-a044db45f885n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-17 19:25                           ` 'Daniel Gnoutcheff' via pandoc-discuss
     [not found]                             ` <b467908f-a4ce-35b9-ba30-ef55e9e70958-rbQqYLFhARYurNyw8EiOWEB+6BGkLq7r@public.gmane.org>
2021-09-18 10:53                               ` BPJ

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=4bd5ecbc-bd1d-442a-9558-6724174f77fcn@googlegroups.com \
    --to=harsh-7+afw328pe6p1wguecwpqti2o/jbrioy@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).