From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: E-books and XML.
Date: Tue, 26 Aug 2014 20:04:47 +0200 [thread overview]
Message-ID: <53FCCC3F.9080806@wxs.nl> (raw)
In-Reply-To: <20140826110712.2b02eff7@localb.wexfordpress.net>
On 8/26/2014 5:07 PM, john Culleton wrote:
> Context is moving toward accepting XML input,
> although the filtering process is necessarily
> complex. But what is also needed is a version
> of Context that produces well formed XML as an
> output. That would be a step toward producing a
> dual purpose document with Context, for print
> and for e-book use.
What do you mean with 'accepting' xml input? It accepts xml input
already for many years. And in mkiv filtering is part of the game too.
> Context users have invested time, often years, in
> learning how to write Context code. Writing XML is
> a whole other skillset, comparable to writing xhtml.
It's not so different if you're accustomed to structure.
> So is writing a Context to XML converter a
> possibility? A probability? The commercial
> program InDesign already has such a capability.
There are export possibilities (and there will be a bit more). This is a
topic at the upcoming ctx meeting (where we set priorities).
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:[~2014-08-26 18:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 15:07 john Culleton
2014-08-26 15:10 ` Wolfgang Schuster
2014-08-26 17:08 ` Henning Hraban Ramm
2014-08-26 17:29 ` Hans Hagen
2014-08-27 7:02 ` Henning Hraban Ramm
2014-08-27 9:05 ` Hans Hagen
2014-08-27 9:25 ` Henning Hraban Ramm
2014-08-27 9:37 ` Hans Hagen
2014-08-27 9:46 ` Henning Hraban Ramm
2014-08-27 10:06 ` Hans Hagen
2014-08-28 8:10 ` Henning Hraban Ramm
2014-08-28 8:22 ` Hans Hagen
2014-08-28 10:54 ` Henning Hraban Ramm
2014-08-28 13:34 ` Hans Hagen
2014-08-28 13:35 ` Hans Hagen
2014-08-28 17:39 ` Hans Hagen
2014-08-29 6:33 ` Henning Hraban Ramm
2014-08-29 10:17 ` Hans Hagen
2014-08-29 11:46 ` Henning Hraban Ramm
2014-08-29 12:46 ` Hans Hagen
2014-08-30 7:56 ` Henning Hraban Ramm
[not found] ` <540AEA44.2080106@wxs.nl>
[not found] ` <540C26D3.1020101@wxs.nl>
2014-09-13 7:29 ` Henning Hraban Ramm
2014-08-27 9:03 ` Henning Hraban Ramm
2014-08-26 18:04 ` Hans Hagen [this message]
2014-08-26 18:12 ` Thomas A. Schmitz
2014-08-27 14:03 ` XML as source (was: E-books and XML) Procházka Lukáš Ing. - Pontex s. r. o.
2014-08-27 18:40 ` Jan Tosovsky
2014-08-28 17:02 ` Mica Semrick
2014-08-27 14:38 ` E-books and XML john Culleton
2014-08-27 16:15 ` Schmitz Thomas A.
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=53FCCC3F.9080806@wxs.nl \
--to=pragma@wxs.nl \
--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).