public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Antoine vidal
	<antoinevidal98-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Utf8 and docx
Date: Tue, 13 Aug 2019 11:33:08 -0700	[thread overview]
Message-ID: <yh480kftm4lxuj.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <9c5b4ae3-6e1c-4bb3-a504-f472dec69bc2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


What is the exact command line you're using, and the exact output
(error message)?

Antoine vidal <antoinevidal98-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Hello
>
> I am using the latest version of pandoc (2.7.3) on Ubuntu.
>
> I am trying to merge a markdown file with a docx file.
>
> but I have this errror : The input must be a UTF-8 encoded text.
> I cheked the xml files of the docx, and they are in utf8.
>
> docx file are supported as input file. However docx file are binary file 
> but it said that they are supported as input file.
>
> Can you help me with this issue?
>
> Kind regards
>
> Antoine
>
> -- 
> 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/9c5b4ae3-6e1c-4bb3-a504-f472dec69bc2%40googlegroups.com.


  parent reply	other threads:[~2019-08-13 18:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 15:55 Antoine vidal
     [not found] ` <9c5b4ae3-6e1c-4bb3-a504-f472dec69bc2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-13 18:33   ` John MacFarlane [this message]
     [not found]     ` <yh480kftm4lxuj.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-14  7:57       ` Antoine vidal
     [not found]         ` <1bdfdfc0-e6bd-4530-866b-738d53ca3dfc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-14 10:42           ` Dmitriy Krasilnikov
     [not found]             ` <6da54d4c-f86f-4fa8-9b32-2d6349184ade-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-14 11:21               ` Antoine vidal
     [not found]                 ` <fddff39a-71c6-4f05-bcd8-c0a4553a3b23-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-14 22:27                   ` John MacFarlane
     [not found]                     ` <yh480ktvaj5qo5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-19  8:43                       ` Antoine vidal
     [not found]                         ` <42c13a39-67e3-47e1-be96-ebddfd3e3298-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-20  6:25                           ` John MacFarlane
     [not found]                             ` <m2k1b8icaa.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-22 10:31                               ` Antoine vidal

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=yh480kftm4lxuj.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=antoinevidal98-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).