From: dmccunney <dennis.mccunney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Request for .mobi input
Date: Wed, 7 Feb 2018 12:32:11 -0500 [thread overview]
Message-ID: <CAF4AJDyOei=MrvTo3=hS2C_Q4=G5L7na=pv4f+kxFnv8S0o0Zg@mail.gmail.com> (raw)
In-Reply-To: <3ec97804-2145-47d6-9311-1e834333d2b7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
On Wed, Feb 7, 2018 at 12:20 PM, David Macfarlane <dmac-HuPk6NEp4MX2eFz/2MeuCQ@public.gmane.org> wrote:
> It would be helpful if pandoc could read .mobi files for conversion into
> .epub or whatever.
>
> I have pandoc v 2.1.1 and I tried .mobi input and it failed with "pandoc:
> Cannot decode byte '\x88': Data.Text.Internal.Encoding.decodeUtf8: Invalid
> UTF-8 stream". I checked the documentation and it doesn't look like .mobi
> input is supported (yet).
Calibre (https://calibre-ebook.com) handles Mobi->ePub conversions.
Its primary purpose is to create and maintain an eBook database, but
it converts between supported formats. Calibre is written in Python,
and cross-platform, available for Windows, Linux, and OS/X.
I haven't tried it, but I believe the conversion can be done from the
command line, calling the conversion module directly instead of going
through the GUI.
(I've converted files I got in Mobi format to ePub without issue.)
______
Dennis
https://plus.google.com/u/0/105128793974319004519
next prev parent reply other threads:[~2018-02-07 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 17:20 David Macfarlane
[not found] ` <3ec97804-2145-47d6-9311-1e834333d2b7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-02-07 17:23 ` Fred Zimmerman
2018-02-07 17:24 ` John MacFarlane
2018-02-07 17:32 ` dmccunney [this message]
[not found] ` <CAF4AJDyOei=MrvTo3=hS2C_Q4=G5L7na=pv4f+kxFnv8S0o0Zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-07 17:45 ` Fred Zimmerman
[not found] ` <CAJ4fGLtvWGW30OwP3sBCVAR+567nyx4y6OikY7CVVx+4Uh4pNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-07 17:51 ` dmccunney
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='CAF4AJDyOei=MrvTo3=hS2C_Q4=G5L7na=pv4f+kxFnv8S0o0Zg@mail.gmail.com' \
--to=dennis.mccunney-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).