ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mica Semrick <paperdigits@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: EPUB woes
Date: Tue, 19 Nov 2013 13:39:11 -0800	[thread overview]
Message-ID: <CABkompJvbqHdA8UsFPvh-7_cpuzWsxvF0NwW7RjUutHL_sNYkg@mail.gmail.com> (raw)
In-Reply-To: <971C0359-183E-490F-B693-EA2801FE9126@uni-trier.de>


[-- Attachment #1.1: Type: text/plain, Size: 4796 bytes --]

Keith,

Maybe you should explore an XML format that can be transformed directly to
epub. You'd also be able to write a style sheet with ConTeXt that would out
put a PDF as well. I think TEI-Lite is a good starting point.

Since you can make your own commands in ConTeXt, it will never be able to
intelligently map all commands on to simple HTML.


On Mon, Nov 18, 2013 at 10:12 AM, Keith J. Schultz <schultzk@uni-trier.de>wrote:

>
> Am 18.11.2013 um 16:33 schrieb Hans Hagen <pragma@wxs.nl>:
>
> On 11/18/2013 4:11 PM, Keith J. Schultz wrote:
>
> 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.
>
>
> sure, and every time i see an epub novel i realize that for something like
> that one really can stick to rather dumb html ... the point is that one
> cannot expect context to output simple everywhere accepted html from
> complex rendered input ...
>
> I agree fully. But, Since there are those that wish to produce epubs aka
> ebooks, they should not be doing complex
> layout. One can always go from simple to complicated in needed, if there
> were commands dedicated to epub/ebooks/html.
> As I had pointed out in my last post below.
>
>
> 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.
>
>
> in that case code in xml and either processit by context or transform it
> into something ebooks can render
>
> 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.
>
>
> so far i had no projects where epub was needes so it has a low priority
> and i still read paper books (or when i would have ebooks i wouldn't need
> to render them) ... pdfs views quite well on e.g. nexus 7 devices and i
> assume the upcoming sony high res ebook will also do pdf well
>
> Well I did start the discussion. Just offer my 2 Euro cents worth.
> Especially, since it comes up every now and then.
> Furthermore, I there was a simple way to create epubs/books with ConTeXt
> more would use this feature.
>  I have used up enough of or time.
>
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 7952 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

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

  reply	other threads:[~2013-11-19 21:39 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
2013-11-18 15:33             ` Hans Hagen
2013-11-18 18:12               ` Keith J. Schultz
2013-11-19 21:39                 ` Mica Semrick [this message]
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=CABkompJvbqHdA8UsFPvh-7_cpuzWsxvF0NwW7RjUutHL_sNYkg@mail.gmail.com \
    --to=paperdigits@gmail.com \
    --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).