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 XHTML Format
Date: Fri, 06 Sep 2013 18:09:34 +0200	[thread overview]
Message-ID: <5229FE3E.3090807@wxs.nl> (raw)
In-Reply-To: <CAANrE7pjNTxXP95c=R+KWACkx_SY8DU0rrwC_L6deNW5m8WhOg@mail.gmail.com>

On 9/6/2013 12:00 AM, Thangalin wrote:

> That is a good point. The current XML structure produced by ConTeXt
> (Hans correct me here if I'm mistaken) is not accessible, as it doesn't
> adhere to strict XHTML. I suspect that <div> tags would not be
> accessible -- the only way to provide true accessibility in EPUB format
> would be by using the strict XHTML tags.

html is not rich enough .. one ends up with abusing tags which in turn 
is confusing for accesibility ... i once saw an epub where h1 was used 
for the chapter number and h2 for the chapter title

> When I talk about strict XHTML, I'm proposing that a _simple_ ConTeXt
> document (up to 6 header levels, numbered and unnumbered lists, images,
> text emphasis, etc.) should generate a simple, validating XHTML
> document. Trying to attain 100% coverage of ConTeXt transmogrification
> to XHTML is ridiculous when, I suspect, 80% coverage would meet most
> needs.. :-)

in that case a few page transformation could do, isn't it?

> *XML + XSLT -> ConTeXT TeX -> EPUB + CSS*

probably ok for novels but who there is no way to limit the user ... so 
in the end we still have a complex mix to deal with ... i'd rather have

ConTeXT TeX reading xml -> export -> optional transform -> EPUB + CSS*

you want 'direct epub html from context' (no xslt) but on the other hand 
use xslt to map onto context while context can do xml directly ... 
chicken egg

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:[~2013-09-06 16:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04  1:19 Thangalin
2013-09-04  9:20 ` Hans Hagen
2013-09-04 17:55   ` Thangalin
2013-09-05 13:55     ` Hans Hagen
2013-09-12 14:32       ` Alan BRASLAU
2013-09-05 16:38   ` Hans Hagen
2013-09-05 16:57     ` Thangalin
2013-09-05 17:57       ` Khaled Hosny
2013-09-05 18:22         ` Hans Hagen
2013-09-05 17:22     ` Aditya Mahajan
2013-09-05 18:21       ` Hans Hagen
2013-09-05 18:11 ` honyk
     [not found] ` <00b501ceaa63$61805e50$24811af0$@tosovsky@email.cz>
2013-09-05 18:20   ` Aditya Mahajan
2013-09-05 18:24     ` Hans Hagen
2013-09-05 19:54       ` Mica Semrick
2013-09-05 21:15       ` Michael Hallgren
2013-09-05 22:00     ` Thangalin
2013-09-06 16:09       ` Hans Hagen [this message]
2013-09-06 16:36       ` Mica Semrick
2013-09-06 20:20         ` Thangalin
2013-09-06 21:22           ` Thangalin
2013-09-06 21:27             ` Aditya Mahajan
2013-09-07 12:07           ` Hans Hagen
2013-09-07 18:31             ` Thangalin

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=5229FE3E.3090807@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).