From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc takes over 30 Hours (twiki to docx)
Date: Wed, 7 Jun 2023 09:44:20 -0700 [thread overview]
Message-ID: <297CC875-56A0-4B97-BFBC-087862BD09CB@gmail.com> (raw)
In-Reply-To: <67533cd1-9d9c-46cd-a55c-d47cab961d02n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
There are some cases where the parsers have exponential performance:
E.g. https://github.com/jgm/pandoc/issues/7558
Try trimming things to figure out where the problematic part is -- if you can get a good minimal test case you can submit a bug report.
> On Jun 6, 2023, at 11:48 PM, Jonathan Saile <jonathan.saile2512-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Hello *,
>
> I am trying to convert a foswiki to a docx format. Some files take hours to convert. Right now a job is runnning for well over 24h. Is this normal? Any google search I did, didn't give me any indication, that this should take so long!
>
> Kind regards,
> Jonathan
>
> --
> 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/67533cd1-9d9c-46cd-a55c-d47cab961d02n%40googlegroups.com.
prev parent reply other threads:[~2023-06-07 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 6:48 Jonathan Saile
[not found] ` <67533cd1-9d9c-46cd-a55c-d47cab961d02n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-07 16:44 ` John MacFarlane [this message]
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=297CC875-56A0-4B97-BFBC-087862BD09CB@gmail.com \
--to=fiddlosopher-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).