Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Thu, 10 Jul 2003 16:05:13 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h6AE5AcH001788 for ; Thu, 10 Jul 2003 16:05:11 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C346EC.47F57280" Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h6ADuaGl003301; Thu, 10 Jul 2003 15:56:37 +0200 (MET DST) Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h69M03aL021895; Thu, 10 Jul 2003 15:56:25 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 0991 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 10 Jul 2003 15:56:25 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h6ADuOM9028832 for ; Thu, 10 Jul 2003 15:56:24 +0200 Received: from wisbech.cl.cam.ac.uk (mta1.cl.cam.ac.uk [128.232.0.15]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h6ADuWGl003288 for ; Thu, 10 Jul 2003 15:56:32 +0200 (MET DST) Received: from pallas.cl.cam.ac.uk ([128.232.8.88] helo=cl.cam.ac.uk ident=[x3tUr6dfhKACM0xpIv1u65OWHGrYk2fD]) by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1) id 19abuQ-0008Fp-00 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 10 Jul 2003 14:56:30 +0100 In-Reply-To: Your message of Thu, 10 Jul 2003 09:43:21 -0400. <78ADDA01-B2DC-11D7-8AE7-0050E4455404@atlis.com> Return-Path: X-OriginalArrivalTime: 10 Jul 2003 14:05:13.0828 (UTC) FILETIME=[4873CA40:01C346EC] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -20.4 () EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,REPLY_WITH_QUOTES Content-class: urn:content-classes:message Subject: Re: OT: ANT, insertions and XML (was Re: Invitation for discussion: My suggestion for a LaTeX3 syntax) Date: Thu, 10 Jul 2003 14:56:30 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: OT: ANT, insertions and XML (was Re: Invitation for discussion: My suggestion for a LaTeX3 syntax) Thread-Index: AcNG7EiNMVpluKnrTPizxd7l2Oj68Q== From: "Robin Fairbairns" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4674 This is a multi-part message in MIME format. ------_=_NextPart_001_01C346EC.47F57280 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable william adams wrote: > Achim said: > > The problem is not the syntax, but the page layout algorithm that > > doesn't know what to do with insertions (yet). > > Any idea on a time frame for this? It's the one thing which has kept > me from experimenting w/ it. anything but the most trivial experiments seem to me to be pretty tricky -- see below. > > BTW, I will not write an XML parser for ant. If someone wants such a > > thing they have to write it themselves. > > Am I missing something here? The ways for getting XML into TeX are > legion, so I don't see why one of the extant solutions for TeX > wouldn't work for Ant. you're forgetting the what the acronym means: ant is not tex there's no tex macro engine in ant, and things like xml decoding need to be written in the style implementation language (aka "ocaml", the language ant itself is written in). robin ------_=_NextPart_001_01C346EC.47F57280 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: OT: ANT, insertions and XML (was Re: = Invitation for discussion: My suggestion for a LaTeX3 = syntax)

william adams wrote:

> Achim said:
> > The problem is not the syntax, but the page = layout algorithm that
> > doesn't know what to do with insertions = (yet).
>
> Any idea on a time frame for this? It's the one = thing which has kept
> me from experimenting w/ it.

anything but the most trivial experiments seem to me = to be pretty
tricky -- see below.

> > BTW, I will not write an XML parser for ant. = If someone wants such a
> > thing they have to write it = themselves.
>
> Am I missing something here? The ways for = getting XML into TeX are
> legion, so I don't see why one of the extant = solutions for TeX
> wouldn't work for Ant.

you're forgetting the what the acronym means: ant is = not tex

there's no tex macro engine in ant, and things like = xml decoding need
to be written in the style implementation language = (aka "ocaml", the
language ant itself is written in).

robin

------_=_NextPart_001_01C346EC.47F57280--