From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Paul <freack1208-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Converting a bunch of .docx to .epub
Date: Fri, 27 Apr 2018 09:26:00 -0700 [thread overview]
Message-ID: <m2sh7gmx9j.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <37f5bb94-8fd5-4d8a-b5a8-4b61ff7bd635-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
This should work. I just tried it with a simple test.
You may need to upload something we can use to test.
And, what version of pandoc are you using?
Paul <freack1208-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hello!
>
> I tried to convert some .docx files to a single .epub but when running
> `pandoc -f docx -t epub -o book.epub <the files>` I receive warnings about
> an empty title element, and the resulting .epub only contains the text from
> the first .docx.
>
> Any ideas?
>
> --
> 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/37f5bb94-8fd5-4d8a-b5a8-4b61ff7bd635%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2018-04-27 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 15:19 Paul
[not found] ` <37f5bb94-8fd5-4d8a-b5a8-4b61ff7bd635-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-04-27 16:26 ` John MacFarlane [this message]
[not found] ` <m2sh7gmx9j.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2018-04-27 16:50 ` Paul
2018-04-27 16:52 ` Paul
[not found] ` <d49229fd-bf6e-4fe0-8670-f818a00376c3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-04-27 20:53 ` John MacFarlane
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=m2sh7gmx9j.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=freack1208-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).