public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pandoc: Error in array index
Date: Thu, 02 Jun 2022 15:14:23 +0200	[thread overview]
Message-ID: <87y1yf4347.fsf@zeitkraut.de> (raw)
In-Reply-To: <718c53ee-f005-4049-a56c-1ccbfb4300c0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Harsh Donga <harsh-7+aFW328pE6p1wGUEcWPqti2O/JbrIOy@public.gmane.org> writes:

> 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

Wow, that's a big file. The error makes me believe that this could be a
problem with tables. Can you try to cut the file down such that it
contains only the tables?

-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


  parent reply	other threads:[~2022-06-02 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 11:19 Harsh Donga
     [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 [this message]
     [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=87y1yf4347.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).