From: John Culleton <john@wexfordpress.com>
Subject: Context to XML
Date: Sun, 9 Jun 2002 19:23:00 -0400 [thread overview]
Message-ID: <200206091923.00924.john@wexfordpress.com> (raw)
I understand that Pragma is working on the job of making XML coded documents
work under Context. However XML does not have ways of showing refinements
such as hanging punctuation etc. AFAIK.
So I have two questions:
Is there a reverse path from Context to XML encoding?
Is the loss of detail in this reverse path so great so as to make the use
of fine typesetting useless?
There are databases of published documents that require conversion to
XML, hence my questions.
--
John Culleton
Able Indexers and Typesetters
http://wexfordpress.com
__________________________________________________
D O T E A S Y - "Join the web hosting revolution!"
http://www.doteasy.com
next reply other threads:[~2002-06-09 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 23:23 John Culleton [this message]
2002-06-09 23:33 ` Hans Hagen
2002-06-10 8:29 ` Taco Hoekwater
2008-04-21 10:02 Context to xml Olivier Guéry
2008-04-21 10:42 ` Mojca Miklavec
2008-04-21 11:18 ` Olivier Guéry
2008-04-21 11:23 ` Wolfgang Schuster
2008-04-21 11:37 ` Mojca Miklavec
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=200206091923.00924.john@wexfordpress.com \
--to=john@wexfordpress.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).