emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan L Tyree <alantyree@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: ePub and Org mode
Date: Sun, 20 Feb 2011 09:15:58 +1100	[thread overview]
Message-ID: <20110220091558.2cdbabfb.alantyree@gmail.com> (raw)
In-Reply-To: <4D603A1A.9020601@christianmoe.com>

On Sat, 19 Feb 2011 22:46:02 +0100
Christian Moe <mail@christianmoe.com> wrote:

> Hi,
> 
> I agree exporting 'chapters' in a single Org document to separate
> html files would be a nice option to have.
> 
> Pending someone writing an export function for this, you could
> 
> - post-process the HTML with one of the scripts out there for 
> splitting up web pages, like htsplit available on CPAN;
> 
> - or go the Org -> DocBook -> `chunked' HTML route?

Good idea. In fact, I just did a simple keyboard macro to go through
the file and export subtrees. Only 12 chapters, so not much of a call
for anything more difficult.

> 
> But just out of curiosity, why would you like this for the purpose of 
> making an ePub book? Are you using a tool that requires it? (Unlike, 
> e.g., Calibre, which takes a single HTML file as input, with TOC
> built from e.g. H2 as chapter headings.)

Fair question. Using something like Calibre is what I would normally
do. I have also used Sigil to build ePub books from a single html file.
It is good since you can add some final editing touches.

I got started on it because I was having a look at pandoc which purports
to build ePub directly. But it doesn't split the files.

Anyway, the (dumb) answer is that I was just fooling around looking at
the internals of ePub structure. Trying to avoid real work :-).

Alan

> 
> Yours,
> Christian
> 
> 
> On 2/19/11 10:25 AM, Alan L Tyree wrote:
> > Greetings from Down Under,
> > I am constructing an ePub formatted book. It came to me in plain
> > text and I have formatted in org-mode.
> >
> > It is easy to export to XHTML, the first step in ePub construction,
> > but I would like every chapter to be a separate file. It is easy
> > enough to do this with a macro or a simple function (even though I
> > am no elisp guru). Is there an export function that does this? I
> > didn't see it in the docs and I don't see anything about it doing a
> > Google search.
> >
> > What would really be nice, is a single command to create the ePub
> > file.
> >
> > Any help appreciated.
> >
> > Cheers,
> > Alan
> >
> 


-- 
Alan L Tyree                    http://www2.austlii.edu.au/~alan
Tel:  04 2748 6206

  reply	other threads:[~2011-02-19 22:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-19  9:25 ePub and Org mode Alan L Tyree
2011-02-19 10:54 ` Bastien
2011-02-19 19:14   ` Alan L Tyree
2011-02-19 21:46 ` Christian Moe
2011-02-19 22:15   ` Alan L Tyree [this message]
2011-02-20  7:53   ` Achim Gratz
2011-02-20  8:17     ` Eric Schulte
2011-02-21  1:34       ` Richard Lawrence
2011-02-20  9:54     ` Alan Tyree

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=20110220091558.2cdbabfb.alantyree@gmail.com \
    --to=alantyree@gmail.com \
    --cc=emacs-orgmode@gnu.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.
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).