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: Re: Pandoc JSON schema
Date: Wed, 2 Nov 2022 08:24:01 -0700 (PDT)	[thread overview]
Message-ID: <81054dc7-a893-4f84-9ce4-ea90f997b12fn@googlegroups.com> (raw)
In-Reply-To: <87pme55qyx.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>


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

Seems great, will try it out
Anything non-haskell? Not so great with coding in haskell yet.

Again, thanks! It has been best to work around with pandoc and it's 
community!

On Wednesday, 2 November 2022 at 20:44:06 UTC+5:30 Albert Krewinkel wrote:

>
> Harsh Donga <ha...-7+aFW328pE6p1wGUEcWPqti2O/JbrIOy@public.gmane.org> writes:
>
> > Do we have any schema validation now, I would like to use it in my
> > custom script which creates pandoc JSON eventually to convert into
> > different formats (HTML. DOCX...).
>
> The schema posted before does not include the new table structure yet.
> Other than that it should remain usable.
>
> I believe that our best path forward would be to use autodocodec:
> https://github.com/NorfairKing/autodocodec
>
>
> -- 
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>

-- 
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/81054dc7-a893-4f84-9ce4-ea90f997b12fn%40googlegroups.com.

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

  parent reply	other threads:[~2022-11-02 15:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 11:16 Albert Krewinkel
     [not found] ` <87bmkwdcdr.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2017-10-24 16:47   ` John MACFARLANE
2017-10-24 16:53     ` John MACFARLANE
2017-10-25  7:47       ` Albert Krewinkel
     [not found]         ` <877evjd5yg.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-02 14:41           ` Harsh Donga
     [not found]             ` <8d53751b-a59c-43fb-a7e1-4f5079903e28n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-02 15:11               ` Albert Krewinkel
     [not found]                 ` <87pme55qyx.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-02 15:24                   ` Harsh Donga [this message]
     [not found]                     ` <81054dc7-a893-4f84-9ce4-ea90f997b12fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-02 15:58                       ` Albert Krewinkel
     [not found]                         ` <87leot5otd.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-12-06  1:04                           ` John MacFarlane
     [not found]                             ` <AC7F0C0B-122B-4BF6-BC02-81FC4BA4B37C-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-12-06 15:44                               ` Albert Krewinkel
     [not found]                                 ` <874ju8wn22.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-12-28  9:44                                   ` Harsh Donga
     [not found]                                     ` <4e6dd89d-1dd0-40bb-a760-e3468c5b2403n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-29 20:37                                       ` John MacFarlane
     [not found]                                         ` <CE12DC92-2BD1-429F-B266-EF9D3231A982-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-19  9:32                                           ` Jörn K

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=81054dc7-a893-4f84-9ce4-ea90f997b12fn@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).