From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Epub woes
Date: Fri, 16 Nov 2012 11:21:54 +0100 [thread overview]
Message-ID: <6D4E68EB-1FD2-4093-9A89-A3B5E93D988F@web.de> (raw)
In-Reply-To: <4A0D66A9-481B-47D4-B52A-5CE23233F108@web.de>
Hi All,
First off, I do not work with ConTexT, but with Lu(La)TeX.
I follow this list looking for pointers.
The way I understand how ConTexT produces output for
epubs is that it just creates HTML.
If ConTexT (or LuaTex) is to produce output for use in epubs
it should map the ConTexT structures to html and the epub format.
That is, it should produce separate files for each chapter.
Furthermore, it should be able to create files for the spine, ncx, css,
and cover page, etc automatically. This with reduce the amount of
postprocessing Considerable.
Furthermore, the method could be design to not only epub, but a
mobi format.
I have just started out on my own ideas for a Lau(La)Tex way of using
it for the creation of ebooks and pdfs from the same source.
Just my two cents, worth.
Sorry, if I am creating noise here.
regards
Keith.
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-11-16 10:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 18:58 Bill Meahan
2012-11-15 19:24 ` Wolfgang Schuster
2012-11-15 20:20 ` Bill Meahan
2012-11-15 23:55 ` Marcin Borkowski
2012-11-16 0:13 ` Aditya Mahajan
2012-11-16 0:48 ` Bill Meahan
2012-11-16 4:17 ` Aditya Mahajan
2012-11-16 15:41 ` Bill Meahan
2012-11-16 16:36 ` Aditya Mahajan
2012-11-16 6:49 ` Andy Thomas
2012-11-16 7:13 ` luigi scarso
2012-11-16 7:18 ` Andy Thomas
2012-11-16 23:18 ` Zenlima
2012-11-16 23:21 ` Zenlima
2012-11-16 23:41 ` Bill Meahan
2012-11-17 7:08 ` luigi scarso
2012-11-17 9:18 ` Alan BRASLAU
2012-11-17 16:48 ` Bill Meahan
2012-11-17 17:24 ` luigi scarso
2012-11-16 10:21 ` Keith J. Schultz [this message]
2013-11-16 15:16 EPUB woes Bill Meahan
2013-11-16 16:00 ` Keith J. Schultz
2013-11-16 16:51 ` Bill Meahan
2013-11-16 17:37 ` Aditya Mahajan
2013-11-16 18:15 ` Bill Meahan
2013-11-18 9:00 ` Keith J. Schultz
2013-11-18 12:21 ` Hans Hagen
2013-11-18 15:11 ` Keith J. Schultz
2013-11-18 15:33 ` Hans Hagen
2013-11-18 18:12 ` Keith J. Schultz
2013-11-19 21:39 ` Mica Semrick
2013-11-20 9:39 ` Keith J. Schultz
2013-11-20 13:59 ` Aditya Mahajan
2013-11-20 18:11 ` Bill Meahan
2013-11-20 19:43 ` Jan Tosovsky
2013-11-20 19:12 ` Keith J. Schultz
2013-11-18 8:05 ` Keith J. Schultz
2013-11-16 16:07 ` Wolfgang Schuster
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=6D4E68EB-1FD2-4093-9A89-A3B5E93D988F@web.de \
--to=keithjschultz@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).