From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: EPUB woes
Date: Wed, 20 Nov 2013 08:59:14 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1311200854200.10508@nqv-guvaxcnq> (raw)
In-Reply-To: <6062EC24-1DF7-4727-84E2-1FFAE5FCE1E4@uni-trier.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1066 bytes --]
On Wed, 20 Nov 2013, Keith J. Schultz wrote:
> \usemodule[ebook]
>
> \setupcss[…]{…}% see comment #1
>
> \setupmapping[…]{…} % used for when author has his/her own ideas #2
>
> %normal ConTeXt sets see comment #3
>
> % possibly set a mode or set externally
>
> \starttext
> \startebook
> \chapter… %see comment #4
> \startparagraph{leftmargin=20%, …] % see comment #5
> % text
> \stopparagraph
> \starttable…
> \stoptable
> …
> \stopebook
> \stoptext
To me, the biggest advantage of a TeX based system is the ease of
extensibility. If you want to restrict to a specific subset, then might as
well use XML:
<document>
<book>
<chapter>
<paragraph leftmargin=20%>
text
</paragraph>
</book>
</document>
or using one of the existing XML schemas rather than inventing your own
(perhaps even HTML5).
As far as ConTeXt is concerned, you can process the above XML quite
easily. Come to think of it, it may be a useful to provide a module that
maps HTML5 to PDF.
Aditya
[-- 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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-11-20 13:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 15:16 Bill Meahan
2013-11-16 16:00 ` Keith J. Schultz
2013-11-16 16:51 ` Bill Meahan
2013-11-16 17:37 ` Aditya Mahajan
2013-11-16 18:15 ` Bill Meahan
2013-11-18 9:00 ` Keith J. Schultz
2013-11-18 12:21 ` Hans Hagen
2013-11-18 15:11 ` Keith J. Schultz
2013-11-18 15:33 ` Hans Hagen
2013-11-18 18:12 ` Keith J. Schultz
2013-11-19 21:39 ` Mica Semrick
2013-11-20 9:39 ` Keith J. Schultz
2013-11-20 13:59 ` Aditya Mahajan [this message]
2013-11-20 18:11 ` Bill Meahan
2013-11-20 19:43 ` Jan Tosovsky
2013-11-20 19:12 ` Keith J. Schultz
2013-11-18 8:05 ` Keith J. Schultz
2013-11-16 16:07 ` Wolfgang Schuster
-- strict thread matches above, loose matches on Subject: below --
2012-11-15 18:58 Epub woes Bill Meahan
2012-11-15 19:24 ` Wolfgang Schuster
2012-11-15 20:20 ` Bill Meahan
2012-11-15 23:55 ` Marcin Borkowski
2012-11-16 0:13 ` Aditya Mahajan
2012-11-16 0:48 ` Bill Meahan
2012-11-16 4:17 ` Aditya Mahajan
2012-11-16 15:41 ` Bill Meahan
2012-11-16 16:36 ` Aditya Mahajan
2012-11-16 6:49 ` Andy Thomas
2012-11-16 7:13 ` luigi scarso
2012-11-16 7:18 ` Andy Thomas
2012-11-16 23:18 ` Zenlima
2012-11-16 23:21 ` Zenlima
2012-11-16 23:41 ` Bill Meahan
2012-11-17 7:08 ` luigi scarso
2012-11-17 9:18 ` Alan BRASLAU
2012-11-17 16:48 ` Bill Meahan
2012-11-17 17:24 ` luigi scarso
2012-11-16 10:21 ` Keith J. Schultz
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.DEB.2.02.1311200854200.10508@nqv-guvaxcnq \
--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).