ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
* ebook from project: observations/oddities
@ 2012-06-04 10:24 Henning Hraban Ramm
  2012-06-04 10:58 ` Andy Thomas
  0 siblings, 1 reply; 2+ messages in thread
From: Henning Hraban Ramm @ 2012-06-04 10:24 UTC (permalink / raw)
  To: mailing ConTeXt users list for

(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
___________________________________________________________________________________


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: ebook from project: observations/oddities
  2012-06-04 10:24 ebook from project: observations/oddities Henning Hraban Ramm
@ 2012-06-04 10:58 ` Andy Thomas
  0 siblings, 0 replies; 2+ messages in thread
From: Andy Thomas @ 2012-06-04 10:58 UTC (permalink / raw)
  To: mailing list for ConTeXt users

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
___________________________________________________________________________________


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-06-04 10:58 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-06-04 10:24 ebook from project: observations/oddities Henning Hraban Ramm
2012-06-04 10:58 ` Andy Thomas

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).