From: Alan L Tyree <alantyree@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Making ePub books
Date: Sun, 11 Dec 2011 18:25:45 +1100 [thread overview]
Message-ID: <1323588345.20628.13@windy> (raw)
In-Reply-To: <6723.1323587268@alphaville.dokosmarshall.org> (from nicholas.dokos@hp.com on Sun Dec 11 18:07:48 2011)
On 11/12/11 18:07:48, Nick Dokos wrote:
> Alan L Tyree <alantyree@gmail.com> wrote:
>
> > Debian Squeeze; org 7.7; emacs 23.2.1
> >
> > I am back to trying to make ePub books from org articles/books. I
> am=20
> > working on a book which currently produces about 100 pages in
> LaTeX=20
> > export. It will be about 200 pages when finished.
> >
> > ePub uses XHTML for the main content. So, I export the org file
> to=20
> > HTML. It verifies as a valid XHTML1.0 file at the w3c
> verification=20
> > site: http://validator.w3.org/
> >
> > OK. Then wrap it up in the mess that is the ePub specification.
> It=20
> > actually reads OK in FBReader and in Iceweasel with the ePub add
> on,=20
> > BUT it does not validate. There are several problems, but most of
> the=20
> > errors involve the "name" attribute. For example:
> >
> > <h2 id=3D"history"><a name=3D"sec-1" id=3D"sec-1"></a><span
> class=3D"sectio=
> > n-
> > number-2">1</span> History</h2>
> >
> > ePub does not like the name in there. Wipe out all the name=3D"xxx"
> and=20
> > the problem goes away. Everything else still works.
> >
> > I know that I can do a post export clean up of the XHTML file, but
> I=20
> > wonder if this is set in some variable that I cannot find.
> >
> > And, as a general question, whay have both name=3D"sec-1" and
> id=3D"sec-1"=20
> > in the same element?
> >
> > I would like to automate everything to go from org to ePub. It
> doesn't=20
> > seem too hard, but I'm a legal academic, not a programmer :-).
> Any=20
> > pointers appreciated.
> >
>
> Back when Avdi Green was working on his book, there was some
> discussion
> of this and Anthony Lander provided a pointer to
> http://calibre-ebook.com/
> - see
>
> http://thread.gmane.org/gmane.emacs.orgmode/41826/focus=41849
Yes, Calibre does a nice job of converting XHTML to ePub; it can be
read in all the readers that I use, but it won't pass the validation
tests. OK unless you want to publish on sites that require validation.
Cheers,
Alan
> Nick
>
>
--
Alan L Tyree http://www2.austlii.edu.au/~alan
Tel: 04 2748 6206 sip:172385@iptel.org
next prev parent reply other threads:[~2011-12-11 7:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 6:59 Making ePub books Alan L Tyree
2011-12-11 7:07 ` Nick Dokos
2011-12-11 7:25 ` Alan L Tyree [this message]
2011-12-11 7:42 ` Nick Dokos
2011-12-11 8:28 ` Alan L Tyree
2011-12-11 9:41 ` Making ePub books: further report Alan L Tyree
2011-12-11 9:52 ` Alan L Tyree
2011-12-11 10:02 ` Jambunathan K
2011-12-11 19:29 ` Alan L Tyree
2011-12-11 15:52 ` Bastien
2011-12-11 15:51 ` Bastien
2011-12-11 20:47 ` Alan L Tyree
2011-12-11 7:50 ` Making ePub books Nick Dokos
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1323588345.20628.13@windy \
--to=alantyree@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).