From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: EPUB XHTML Format
Date: Sat, 7 Sep 2013 11:31:11 -0700 [thread overview]
Message-ID: <CAANrE7oyESyG98qyhZBV0gLqapu9rO=nUAPgw774ShCD5OuEYg@mail.gmail.com> (raw)
In-Reply-To: <522B16EE.8080005@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1052 bytes --]
Hi,
so, i'd never claim that context produces epub but it can be used in a
> workflow that involves epub as it outputs xml which can be transformed
>
That's a distinction that either might not matter or sometimes is lost:
http://tex.stackexchange.com/a/17642/2148
http://wiki.contextgarden.net/epub
"ConTeXt has preliminary epub <http://en.wikipedia.org/wiki/EPUB>support..."
Does ConTeXt refer to a suite of tools, or only the "context" command?
Either way, it appears that the line between the command and the tool set
is blurred a bit. This is completely understandable, too, as you wouldn't
want to write, "the ConTeXt suite of tools includes a command, mtxrun, that
can produce EPUB files" all the time when talking about EPUBs.
> supporting all variants of epub in the backend would be the same as
> hardcoding all kind of xml dts in the frontend (docbook, tei, whatever);
> instead we provide a general xml handler and a general xml export
That paragraph would be an excellent addition to the wiki; not sure where
though.
Kind regards.
[-- Attachment #1.2: Type: text/html, Size: 1763 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2013-09-07 18:31 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
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 [this message]
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='CAANrE7oyESyG98qyhZBV0gLqapu9rO=nUAPgw774ShCD5OuEYg@mail.gmail.com' \
--to=thangalin@gmail.com \
--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).