From: Harsh Donga <harsh-7+aFW328pE6p1wGUEcWPqti2O/JbrIOy@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: pandoc: Error in array index
Date: Thu, 2 Jun 2022 04:19:26 -0700 (PDT) [thread overview]
Message-ID: <9cbed52f-ee9b-4ab2-b41b-efbe55264aefn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 768 bytes --]
Hey guys,
I am having problem converting pandoc AST (json) to DOCX
Error displayed : "pandoc: Error in array index"
It works well while converting to HTML.
Can someone please help out please? Huge thanks in advance!!!
Pandoc AST JSON : outPandoc.json
<https://drive.google.com/file/d/1xbM2XnvbXsv9Z_28J5QlTEcvocQeyp9n/view?usp=sharing>
Regards,
Harsh
--
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/9cbed52f-ee9b-4ab2-b41b-efbe55264aefn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1209 bytes --]
next reply other threads:[~2022-06-02 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 11:19 Harsh Donga [this message]
[not found] ` <9cbed52f-ee9b-4ab2-b41b-efbe55264aefn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-02 11:20 ` Harsh Donga
[not found] ` <718c53ee-f005-4049-a56c-1ccbfb4300c0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-02 13:14 ` Albert Krewinkel
[not found] ` <87y1yf4347.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-03 10:35 ` Harsh Donga
[not found] ` <6007f4ef-8fd2-4e75-a1b0-1073738cbd04n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-03 13:07 ` Albert Krewinkel
[not found] ` <87a6atoolg.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-03 16:41 ` Harsh Donga
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=9cbed52f-ee9b-4ab2-b41b-efbe55264aefn@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).