public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Farhan Khan <khanzf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jesse Rosenthal <jrosenthal-4GNroTWusrE@public.gmane.org>
Cc: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: UTF-8 error when converting Docx to Markdown
Date: Wed, 31 Dec 2014 16:54:22 -0500	[thread overview]
Message-ID: <CAFd4kYAczfd6tfWYJBiJm47itpRzZQ6fY-B3y7k252N1Q11SZQ@mail.gmail.com> (raw)
In-Reply-To: <m1tx0crpmx.fsf-4GNroTWusrE@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2458 bytes --]

My version information below:

I am using Ubuntu 14.04.

$ pandoc -v
pandoc 1.12.2.1
Compiled with texmath 0.6.5.2, highlighting-kate 0.5.5.1.
Syntax highlighting is supported for the following languages:
    actionscript, ada, apache, asn1, asp, awk, bash, bibtex, boo, c,
changelog,
    clojure, cmake, coffee, coldfusion, commonlisp, cpp, cs, css, curry, d,
    diff, djangotemplate, doxygen, doxygenlua, dtd, eiffel, email, erlang,
    fortran, fsharp, gnuassembler, go, haskell, haxe, html, ini, java,
javadoc,
    javascript, json, jsp, julia, latex, lex, literatecurry,
literatehaskell,
    lua, makefile, mandoc, markdown, matlab, maxima, metafont, mips,
modelines,
    modula2, modula3, monobasic, nasm, noweb, objectivec, objectivecpp,
ocaml,
    octave, pascal, perl, php, pike, postscript, prolog, python, r,
    relaxngcompact, rhtml, roff, ruby, rust, scala, scheme, sci, sed, sgml,
sql,
    sqlmysql, sqlpostgresql, tcl, texinfo, verilog, vhdl, xml, xorg, xslt,
xul,
    yacc, yaml
Default user data directory: /home/farhan/.pandoc
Copyright (C) 2006-2013 John MacFarlane
Web:  http://johnmacfarlane.net/pandoc
This is free software; see the source for copying conditions.  There is no
warranty, not even for merchantability or fitness for a particular purpose.


On Wed, Dec 31, 2014 at 7:05 AM, Jesse Rosenthal <jrosenthal-4GNroTWusrE@public.gmane.org> wrote:

>
> Hi,
>
> Farhan <khanzf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > 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!
>
> That still seems weird -- are you sure you're using a pandoc version
> that actually supports reading docx?
>
> What's the output of `pandoc -v`?
>

-- 
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/CAFd4kYAczfd6tfWYJBiJm47itpRzZQ6fY-B3y7k252N1Q11SZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 3694 bytes --]

  parent reply	other threads:[~2014-12-31 21: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
     [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 [this message]
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=CAFd4kYAczfd6tfWYJBiJm47itpRzZQ6fY-B3y7k252N1Q11SZQ@mail.gmail.com \
    --to=khanzf-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=jrosenthal-4GNroTWusrE@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).