public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Samuel Viscapi <sviscapi-KK0ffGbhmjU@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: [Pandoc 1.12.3.1] Never ending docx to HTML conversion with 100% CPU usage
Date: Wed, 8 Apr 2020 02:45:17 -0700 (PDT)	[thread overview]
Message-ID: <319d4b4b-be6b-439b-931b-a85c5ce4a00b@googlegroups.com> (raw)


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

Dear all,

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 ?).

At first the conversion failed because of some UTF-8 related errors, but 
those are well documented in the manual:

https://pandoc.org/MANUAL.html#character-encoding

Now, I'm faced with a never ending process silently eating ~100% CPU time 
for hours (before eventually getting terminated by the system).

My command reads as follows:

iconv -f latin1 -t utf-8 file.docx | pandoc -o output.html

Since the docx file originated from Windows, its character encoding is 
"Western Alphabet", thus I hope "latin1" is a close enough approximation.

I tried to explicitly tell pandoc about the input and output formats (-f 
docx -t html) but to no avail... (pandoc: Unknown reader: docx)

I also played a while with extensions (--from docx+empty_paragraphs, --from 
docx+styles, etc...), no luck so far.

What am I doing wrong ?

Best regards,

Samuel, from CINES (Montpellier, France)

https://www.cines.fr/en/

-- 
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/319d4b4b-be6b-439b-931b-a85c5ce4a00b%40googlegroups.com.

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

             reply	other threads:[~2020-04-08  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08  9:45 Samuel Viscapi [this message]
     [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
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=319d4b4b-be6b-439b-931b-a85c5ce4a00b@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).