From: Farhan <khanzf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: UTF-8 error when converting Docx to Markdown
Date: Wed, 31 Dec 2014 01:54:16 -0800 (PST) [thread overview]
Message-ID: <74660d48-9d88-4126-a34a-f815e542b4c7@googlegroups.com> (raw)
In-Reply-To: <5305b92a-418f-44dc-87cc-8a42ae30fffd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1831 bytes --]
Sorry to answer my own question, but a few hours of Googling for me the
answer. You can use the tool unoconv to accomplish this task:
unoconv --stdout -f html test.docx | pandoc -f html -t markdown -o test.md
Hope this helps the next guy!
On Wednesday, December 31, 2014 3:56:51 AM UTC-5, Farhan wrote:
>
> I forgot to mention, when I attempt to use iconv, as the documentation
> suggests, I receive a similar error:
>
> $ iconv -t utf-8 test.docx
> P)Ficonv: illegal input sequence at position 12
>
> On Wednesday, December 31, 2014 3:54:11 AM UTC-5, Farhan wrote:
>>
>> Hi,
>>
>> I can convert a markdown file to docx:
>>
>> $ pandoc test.md -o test.docx
>>
>> The resulting file "test.docx" opens just fine with both MS Word 2013 and
>> LibreOffice. However, when I attempt to convert that same resultant Docx
>> file back to markdown, I get an error:
>>
>> $ pandoc test.docx -t markdown -o test.md
>> pandoc: Cannot decode byte '\x9f': Data.Text.Encoding.Fusion.streamUtf8:
>> Invalid UTF-8 stream
>>
>> I get the same error when I try to convert Docx to any other format as
>> well, such as HTML. The issue seems to be that there is an invalid UTF-8
>> character. Is there a way to resolve this issue? Please let me know.
>>
>> Thanks!
>>
>
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/74660d48-9d88-4126-a34a-f815e542b4c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 6085 bytes --]
next prev parent reply other threads:[~2014-12-31 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 8:54 Farhan
[not found] ` <9d171289-7a60-4ea0-907d-333e4cfba86e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-31 8:56 ` Farhan
[not found] ` <5305b92a-418f-44dc-87cc-8a42ae30fffd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-31 9:54 ` Farhan [this message]
[not found] ` <74660d48-9d88-4126-a34a-f815e542b4c7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-31 12:05 ` Jesse Rosenthal
[not found] ` <m1tx0crpmx.fsf-4GNroTWusrE@public.gmane.org>
2014-12-31 21:54 ` Farhan Khan
2014-12-31 22:34 Jesse Rosenthal
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=74660d48-9d88-4126-a34a-f815e542b4c7@googlegroups.com \
--to=khanzf-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).