From: Hans Hagen <pragma@wxs.nl>
To: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: epub
Date: Sat, 18 Feb 2012 09:25:33 +0100 [thread overview]
Message-ID: <4F3F607D.9040301@wxs.nl> (raw)
In-Reply-To: <4061D4AB-0CA9-49A0-B6E8-B53B7F3A8C10@googlemail.com>
On 18-2-2012 08:17, Wolfgang Schuster wrote:
> I would really prefer to use only html tags when a epub file is produced, now the files can be only viewed without problems in firefox (with the epubreader extension) which is nonsense. With the epub 3 standard also mathml is supported and when a reader is used which doesn’t understand it that’s no problem because the standard is AFAIK backward compatible and unknown functions are just ignored.
In that case some postprocessing has to be applied to as it makes no
sense to add tons of code to context to produce a less rich output (also
a pain to do and it will never be ok). We would end up with ugly kludges
like misusing <h1> for whatever we like combined with classes that make
it titles, section numbers, inline highlighting, etc ...
The export is not so much html but xhtml and afaik css can deal with
that. I woudn't be surprised if future ebook devices could do the same
as what firefox/chrome do. Also keep in mind that the (now xml) export
can be converted while some html/class/span/div hybrid would be painful
to postprocess. Going from rich encoding to poor encoding (rendering) is
easier than the reverse. I can imagine that we provide a couple of
mappings from export xml to whatever html.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-02-18 8:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 10:51 epub Jörg Hagmann
2012-02-16 11:13 ` epub luigi scarso
2012-02-16 13:07 ` epub Jörg Hagmann
2012-02-16 13:17 ` epub luigi scarso
2012-02-16 13:30 ` epub Jörg Hagmann
2012-02-16 15:19 ` epub Jörg Hagmann
2012-02-16 19:04 ` epub Wolfgang Schuster
2012-02-16 19:38 ` epub Aditya Mahajan
2012-02-16 20:08 ` epub Wolfgang Schuster
2012-02-16 21:53 ` epub Hans Hagen
2012-02-17 9:42 ` epub Wolfgang Schuster
2012-02-17 11:44 ` epub Hans Hagen
2012-02-17 13:57 ` epub Jörg Hagmann
2012-02-20 17:45 ` epub George N. White III
2012-02-20 18:25 ` epub Khaled Hosny
2012-02-18 7:17 ` epub Wolfgang Schuster
2012-02-18 8:25 ` Hans Hagen [this message]
2012-02-18 8:31 ` epub luigi scarso
2012-02-18 8:35 ` epub luigi scarso
2012-02-18 9:50 ` epub Hans Hagen
2012-02-17 10:04 ` epub luigi scarso
2012-02-17 10:17 ` epub Jörg Hagmann
2012-02-17 10:23 ` epub luigi scarso
2012-02-17 11:40 ` epub Hans Hagen
2012-02-16 14:07 ` epub Henning Hraban Ramm
2012-06-07 16:04 epub Hans Hagen
2012-06-08 4:19 ` epub Khaled Hosny
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=4F3F607D.9040301@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=schuster.wolfgang@googlemail.com \
/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).