From: Michael Hallgren <m.hallgren@free.fr>
To: ntg-context@ntg.nl
Subject: Re: EPUB XHTML Format
Date: Thu, 05 Sep 2013 23:15:07 +0200 [thread overview]
Message-ID: <5228F45B.60209@free.fr> (raw)
In-Reply-To: <5228CC7A.9040307@wxs.nl>
Le 05/09/2013 20:24, Hans Hagen a écrit :
> On 9/5/2013 8:20 PM, Aditya Mahajan wrote:
>
>> The typical ConTeXt document has a lot of structure, and the XML export
>> generates a well structured XML output. That can be directly used in
>> most modern browsers that handle XML+CSS well. However, most (all?) EPUB
>> readers don't. So, the question is asking if instead ConTeXt could
>> generate a XHTML
>
> but how hard would it be to make an xslt tranformation from
> context.export to epub variants (ok, at some point i can look into it
> but only if there is a robust standard and i have devices to test it on)
>
> and indeed the quality of the source is important
Sounds by far to be the cleanest approach.
Cheers,
mh
>
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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-09-05 21:15 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 [this message]
2013-09-05 22:00 ` Thangalin
2013-09-06 16:09 ` Hans Hagen
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=5228F45B.60209@free.fr \
--to=m.hallgren@free.fr \
--cc=mh@xalto.net \
--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).