From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: EPUB XHTML Format
Date: Thu, 5 Sep 2013 14:20:30 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1309051414280.29678@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <00b501ceaa63$61805e50$24811af0$@tosovsky@email.cz>
On Thu, 5 Sep 2013, honyk wrote:
> On 2013-09-04 Thangalin wrote:
>>
>> What needs to happen to take a minimal ConTeXt file (such as the
>> attached) to produce a minimum viable EPUB that:
>>
> It is always difficult to parse and further process not well structured
> plain text without advanced semantics. Garbage in, garbage out.
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
> If you need both EPUB and PDF, start with a semantically rich XML
> vocabulary, e.g. DocBook. In this case you can relatively easy transfrom
> (XSLT) input data into almost any format. These basic outputs like EPUB or
> PDF (via XSL-FO) you can get out-of-the-box. The Context output can be
> generated using dbcontext: http://dblatex.sourceforge.net/
>
> In sum, use XML as your primary source and from it derive everything else.
I haven't used XML-only toolchains. Is it possible to handle:
- Automatic section numbering taking care of different conversions.
- Automatic index generation and sorting
- Inserting hyphenation points at the approriate place in the generated
ouput (so that the browser can effectively rely on TeX's hyphenation
algorithm to do linebreaking).
- Convert TeX math to MathML.
The current ConTeXT XML source can translate a well formed ConTeXt
document into a XML document with the above features.
Aditya
___________________________________________________________________________________
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 18:20 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 [this message]
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
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=alpine.LNX.2.02.1309051414280.29678@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).