From: "Keith J. Schultz" <schultzk@uni-trier.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: EPUB woes
Date: Mon, 18 Nov 2013 16:11:23 +0100 [thread overview]
Message-ID: <63EC0C6C-1DBA-4CE4-84E5-66347AF42417@uni-trier.de> (raw)
In-Reply-To: <528A063A.10203@wxs.nl>
Hi Hans,
Am 18.11.2013 um 13:21 schrieb Hans Hagen <pragma@wxs.nl>:
> On 11/18/2013 10:00 AM, Keith J. Schultz wrote:
>
>> 2) Now, what a EPub-READER must implement to handle is very
>> little. There are HARDLY ANY provisions that a certified EPuB-READER has
>> to implement any particular engine or features therein to display/render
>> the information contain in the EPub-file/wrapper.
>
> right, and I'm not going to waste time on it till i have a decent ebook reader that behaves well
The point you are missing is that the ereaders are behaving well. They are following the epub
standard, and that to the letter of the standard. The problem is that the standard does not
enforce any particular implementation. If you look at the slow progress of the standard that
actually requires a full implementation of the HTML5 standard. That wait will very long.
Furthermore, ereaders are made by companies more interested in profits than spending a few Euros
more to put decent HTML engines into their readers. Why they do not do that is beyond me!
>
>>> 3. Modify the way in which ConTeXt generates the XML files. Ideally, I should be able to write something like
>> Would be nice if there where commands in ConTeXt or a module for defining what should go into the CSS and a
>> mode "epub" where the ConTeXt commands are converted to suitible HTML5 structures that are suitiable for
>> most ereaders.
>> Features:
>> 1) margins in percentages
>> 2) font sizes based on em
>> 3) a new file for every chapter optional for sections user defined
>> Just a few. Lots more can be found in any decent documentation on writing ebooks.
>
> context outputs xml and as a bonus provides a css too ... one can always convert that xml to his/her ebooks liking .. maybe at some point the mtx-epub script will do that
I always to like to look at programming as modular and would think that a epub/ebook module would be nice that maps
there are commands for layingout ebooks. these commands can then be mapped back to standard context commands.
For some interested in producing a epub then can use the conventions for producing ebooks and ConTeXt can provide the
math conversions to regular page dimensions used in PDFs for proofing or creating a printed version. It would also make the
creation of EPubs from ConTeXt a simple parsing exercise.
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:[~2013-11-18 15:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 15:16 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2012-11-15 18:58 Epub woes 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
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=63EC0C6C-1DBA-4CE4-84E5-66347AF42417@uni-trier.de \
--to=schultzk@uni-trier.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).