ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Epub format Was: Re:  Context to epub: itemize
Date: Wed, 18 Feb 2015 17:54:53 +0100	[thread overview]
Message-ID: <54E4C3DD.1050904@wxs.nl> (raw)
In-Reply-To: <D32828BE-1E54-41AC-9131-59F7E5CFAF45@icloud.com>

On 2/17/2015 10:01 PM, Keith Schultz wrote:
>
>> Am 17.02.2015 um 21:16 schrieb Hans Hagen <pragma@wxs.nl
>> <mailto:pragma@wxs.nl>>:
>>
>> On 2/17/2015 8:24 AM, Keith J. Schultz wrote:
>>> Hi Axel, All,
>>>
>>>
> [snip, snip]
>>> IMHO : ConTeXt should not output XHMTL for epub, but HMTL5.
>>> Yes, yes, I know XHMTL is part of HMTL5.
>>
>> And html 5 is just html with some extras (and assuming javascript i
>> guess) ... marketing.
> The html 5 standard is far more. For one is makes flash, java and more
> obsolete. Far more than a marketing gag!

well, if javascript is used instead it's still fluent ... every time i 
played with e.g. jquery or libraries i had to make sure i used the 
latest and had to adapt code .. there will be something new (and maybe 
even different) every decade (if only because that generates money)

>>> Another question for me is if ConTeXt should also output code for
>>> the iBooks epub format, (Basicaly epub, but some extras).
>>
>> Isn't a book supposed to be independent and kind of portable + long
>> term visible? So no way that a context epub will be specific for a
>> device. (I probably can't even get it on / test it on my outdated ipad
>> 1 anyway.)
> I was thinking more along the line of the spine.

ah, direct neural injection ...

>>> There are thing you can do in/with ConTeXt that would work with iBooks
>>> that do not in „ordinary“ epub books.
>>>
>>> Then, there is the Kindle format one might want to consider!
>>
>> Another lock-in device.
>>
>>> Another, question which needs investigation is if the ConTeXt output for
>>> epub,
>>> also, implementing the fallbacks for missing features which is required?
>>
>> Context outputs three varants: regular xml, xhtml, and stupified xhtml
>> with div/class tagging. The last one is supposed to work on all
>> devices as it doesn't demands anything beyond css.
> If that is the case it is not very useful for a decent workflow. There
> would be to much to
> tweak to make good looking output.

i'm not sure what you have in mind but context is a typesetting system 
and as such cannot produce an epub simply because epub is a blob of xml 
(html) with a css packages in a zip

> I have not investigated how it handles dimensions, widths, font sizes,
> spacing, etc.

structure normally doesn't carry that information

> These are important in order to create output that adjust proper to the
>          devices capabilities.
> One should avoid absolute values.

there are hardly any values output ... but one can of course extend the 
css with font and color directives, probably different from the ones 
used in the pdf

> Of course if we want to emulate the printed output then we could simply
> create a pdf or very page as pdf and put in an epub wrapper.

i've seen impressive examples of pdf turned html (huge html files btw)

(fyi: i see pdf and html as independent things)

(and i don't believe in reflow of pdf: it's either a design for made up 
pages or a flexible adaptive one as in html; and till now i never wished 
a paper book to reflow itself anyway but maybe if i really would use an 
epub device ... who knows ... i don't own ebooks currently as i cannot 
share docs freely then like i share books and i consider ebooks to be 
way too expensive for fun)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2015-02-18 16:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 16:17 Axel Kielhorn
2015-02-16 18:55 ` Hans Hagen
2015-02-17  6:11   ` Axel Kielhorn
2015-02-17  7:24     ` Epub format Was: " Keith J. Schultz
2015-02-17 20:16       ` Hans Hagen
2015-02-17 21:01         ` Keith Schultz
2015-02-18 16:54           ` Hans Hagen [this message]
2015-02-19  9:27             ` Keith Schultz
2015-02-17 22:37         ` Aditya Mahajan
2015-02-18  8:14           ` Henning Hraban Ramm
2015-02-18 14:10             ` Keith J. Schultz
2015-02-18 14:21               ` Henning Hraban Ramm
2015-02-18 16:44               ` Hans Hagen
2015-02-18 16:55           ` Hans Hagen

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=54E4C3DD.1050904@wxs.nl \
    --to=pragma@wxs.nl \
    --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).