From: Andy Thomas <andythomas@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ebook from project: observations/oddities
Date: Mon, 4 Jun 2012 12:58:41 +0200 [thread overview]
Message-ID: <FACAFC35-DD69-4651-B1B7-D85B8BFB8740@web.de> (raw)
In-Reply-To: <9C95CCD3-B4FC-4476-BA9F-F43B6B8DDDC2@fiee.net>
I might not be able to help you with an automated output using context, but I can recommend a very good book on e-book creation. Elizabeth Castro (ISBN 978-0321734686) discusses a sample e-book line by line of the source code, how to create it, validate it (http://code.google.com/p/epubcheck/) etc. You can find the sources of her sample e-book online at: http://www.elizabethcastro.com/epub/examples/ . There is some other useful stuff, too.
I just started to implement some of the info I gathered in my context module for my book project, so I cannot give concrete advise,yet :( But I made the TOC etc. 'by hand' to to try if it would work with the validator, kindle, calibre and so on. Just the xhtml was automatically created (and tweaked a little). It does not take as much time as it seems, we were able to have a validated e-pub with a sample chapter in a day.
Hope this help a little,
Andy
On 04.06.2012, at 12:24, Henning Hraban Ramm wrote:
> (Yesterday’s beta in suite=minimals, OSX-Intel)
>
> With
>
> \setupbackend[export=example.xml,xhtml=example.xhtml,css=example.css]
>
> in my project’s environment,
> I get both "example.xml" and "example.xhtml" (as well as "example-images.css" and "example-style.css"), starting with the same content (up to line 857 in my case), but the .xhtml stops after the first \stoppart, while the .xml contains all four parts.
>
>
> mtxrun --script epub --make example
> insists on copying a file named exactly "example.xhtml" to the ePub tree.
>
> Using
> \setupbackend[export=example.xhtml,xhtml=test.xhtml,css=example.css]
> both "example.xhtml" and "test.xhtml" are identical, complete *and* both copied to the epub tree (ToC refers to test.xhtml, the other is ignored).
>
> Since none of my browsers or epub readers likes this XML format, I guess I’ll need to apply a XSL transformation to create HTML.
>
> Ok... Looking at "mtx-epub.lua" I understand why none of my setups (i.e. author, title) has any effect on the output.
> Seems like we need to fix that manually - unzip the epub, fix it, re-pack... But create the ToC manually??
>
>
>
> Greetlings, Hraban
> ---
> http://www.fiee.net/texnique/
> http://wiki.contextgarden.net
> https://www.cacert.org (I'm an assurer)
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2012-06-04 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 10:24 Henning Hraban Ramm
2012-06-04 10:58 ` Andy Thomas [this message]
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=FACAFC35-DD69-4651-B1B7-D85B8BFB8740@web.de \
--to=andythomas@web.de \
--cc=ntg-context@ntg.nl \
/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).