From: Samuel Viscapi <sviscapi-KK0ffGbhmjU@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: [Pandoc 1.12.3.1] Never ending docx to HTML conversion with 100% CPU usage
Date: Thu, 9 Apr 2020 00:42:53 -0700 (PDT) [thread overview]
Message-ID: <82f0dfad-4499-4daa-8714-17f4396869ac@googlegroups.com> (raw)
In-Reply-To: <m2zhbmaqf9.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1949 bytes --]
Thank you John and Jesse for you quick replies, that's really appreciated.
I just gave a go at the binary release from Github:
iconv -f latin1 -t utf-8 file.docx | /path/to/pandoc-2.9.2.1/bin/pandoc -o
output.html
Again, 100% CPU usage for some minutes. The new thing is: 80%+ of RAM usage
too, out of 8GB.
The system had to terminate the process.
Output.html was successfully created, but empty.
What am I missing ?
Best regards,
Samuel
On Wednesday, April 8, 2020 at 6:33:15 PM UTC+2, John MacFarlane wrote:
>
>
> You can try the linux binary on our GitHub releases page.
> It's statically linked and I imagine it will work on your
> system.
>
> Jesse Rosenthal <jrose...-4GNroTWusrE@public.gmane.org <javascript:>> writes:
>
> > Samuel Viscapi <svis...-KK0ffGbhmjU@public.gmane.org <javascript:>> writes:
> >
> >> I'm trying to turn a "simple", one-page DOCX document into an HTML
> page,
> >> using pandoc 1.12.3.1 on CentOS 7.7 x86_64 (yeah, it's fairly old I
> know,
> >> should I try to compile the newest version from source ?).
> >
> > Way too old -- conversion from docx wasn't introduced until 1.13.
> >
> > --
> > 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/87k12qds0n.fsf%40jhu.edu.
>
>
--
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/82f0dfad-4499-4daa-8714-17f4396869ac%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3661 bytes --]
next prev parent reply other threads:[~2020-04-09 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 9:45 Samuel Viscapi
[not found] ` <319d4b4b-be6b-439b-931b-a85c5ce4a00b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-08 13:30 ` Jesse Rosenthal
[not found] ` <87k12qds0n.fsf-4GNroTWusrE@public.gmane.org>
2020-04-08 16:32 ` John MacFarlane
[not found] ` <m2zhbmaqf9.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-04-09 7:42 ` Samuel Viscapi [this message]
2020-04-09 8:33 ` Samuel Viscapi
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=82f0dfad-4499-4daa-8714-17f4396869ac@googlegroups.com \
--to=sviscapi-kk0ffgbhmju@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).