From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Cc: ntg-context@ntg.nl
Subject: Re[3]: Pool string shortage?
Date: Thu, 15 Nov 2001 20:19:11 +0100 [thread overview]
Message-ID: <64458531.20011115201911@bigfoot.com> (raw)
In-Reply-To: <5.1.0.14.1.20011115165653.03240f00@server-1>
Thursday, November 15, 2001 Hans Hagen wrote:
HH> At 01:17 PM 11/15/2001 +0100, you wrote:
>>NO - WAY ! (Oh, actually, yes, that's the way I do the xdesc stuff
>>...)
HH> I'm playing with loading XML data into mem and manipulating it -)
HH> Is there an xml sorting program [maybe a nice challenge for berend -)]
I'm not sure that TeX should to anything more than typeset
--everything else should be left on the pre/post processor side.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2001-11-15 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 16:28 Giuseppe Bilotta
2001-11-14 17:17 ` Hans Hagen
2001-11-15 12:17 ` Re[2]: " Giuseppe Bilotta
2001-11-15 15:58 ` Hans Hagen
2001-11-15 19:19 ` Giuseppe Bilotta [this message]
2001-11-16 8:33 ` Re[3]: " Hans Hagen
2001-11-15 21:37 ` Re[2]: " Berend de Boer
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=64458531.20011115201911@bigfoot.com \
--to=bourbaki@bigfoot.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).