Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Fri, 11 Jul 2003 08:23:55 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h6B6NqcH004560 for ; Fri, 11 Jul 2003 08:23:53 +0200 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 h6B6I5Gl021509; Fri, 11 Jul 2003 08:18:05 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34775.00FF8F80" 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 h6B400NZ001562; Fri, 11 Jul 2003 08:16:56 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 0254 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 11 Jul 2003 08:16:56 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 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 h6B6GuM9002120 for ; Fri, 11 Jul 2003 08:16:56 +0200 Received: from control.informatik.rwth-aachen.de (control.Informatik.RWTH-Aachen.DE [137.226.53.6]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with SMTP id h6B6H4Gl021365 for ; Fri, 11 Jul 2003 08:17:04 +0200 (MET DST) Received: (qmail 4733 invoked from network); 11 Jul 2003 06:17:04 -0000 Received: from unknown (HELO i7.informatik.rwth-aachen.de) (137.226.53.122) by control.informatik.rwth-aachen.de with SMTP; 11 Jul 2003 06:17:04 -0000 Received: (qmail 14159 invoked by uid 607); 11 Jul 2003 06:17:04 -0000 In-Reply-To: <78ADDA01-B2DC-11D7-8AE7-0050E4455404@atlis.com>; from wadams@ATLIS.COM on Thu, Jul 10, 2003 at 09:43:21AM -0400 References: <20030710081528.A12401@diabolo.informatik.rwth-aachen.de> <78ADDA01-B2DC-11D7-8AE7-0050E4455404@atlis.com> Return-Path: X-OriginalArrivalTime: 11 Jul 2003 06:23:57.0366 (UTC) FILETIME=[02689560:01C34775] User-Agent: Mutt/1.2.5i X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -33.4 () EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_MUTT Content-class: urn:content-classes:message Subject: Re: OT: ANT Date: Fri, 11 Jul 2003 07:17:04 +0100 Message-ID: A<20030711081704.A14039@diabolo.informatik.rwth-aachen.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: OT: ANT Thread-Index: AcNHdQKnRjRvawhLSJiSvJbgEQzmwQ== From: "Achim Blumensath" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4677 This is a multi-part message in MIME format. ------_=_NextPart_001_01C34775.00FF8F80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, 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. I'm currently finishing the next version of ant which mainly fixes a lot of small things like: o font encodings o hyphenation o colour and images o PDF output (only bitmap fonts though) When it is done I plan to start working on insertions. How long it will take I haven't the slightest idea. BTW, at the moment one has to modify the source code of ant if one wants to experiment with those features not present in TeX. Most of them cannot be accessed from the markup language -- mainly because I haven't had time to come up with suitable commands. > > 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. ant is not completely TeX compatible. Hence, the existing tools have to be adapted to produce ant code. But I agree that this would be the easiest way to feed XML to ant (although a bit pointless, since the output quality of TeX and ant are the same). I made the above remark since I got the impression that the original poster thought I planned to make XML the default input format for ant. Achim -- ________________________________________________________________________ | \_____/ = | Achim Blumensath \O/ \___/\ = | Mathematische Grundlagen der Informatik =3Do=3D \ = /\ \| www-mgi.informatik.rwth-aachen.de/~blume /"\ = o----| ____________________________________________________________________\___|= ------_=_NextPart_001_01C34775.00FF8F80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: OT: ANT

Hello,

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.

I'm currently finishing the next version of ant which = mainly fixes a lot
of small things like:

 o font encodings
 o hyphenation
 o colour and images
 o PDF output (only bitmap fonts though)

When it is done I plan to start working on insertions. = How long it will
take I haven't the slightest idea.

BTW, at the moment one has to modify the source code = of ant if one wants
to experiment with those features not present in TeX. = Most of them
cannot be accessed from the markup language -- mainly = because I haven't
had time to come up with suitable commands.

> > 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.

ant is not completely TeX compatible. Hence, the = existing tools have to
be adapted to produce ant code. But I agree that this = would be the
easiest way to feed XML to ant (although a bit = pointless, since the
output quality of TeX and ant are the same).

I made the above remark since I got the impression = that the original
poster thought I planned to make XML the default = input format for ant.

Achim
--
________________________________________________________________= ________
          &nbs= p;            = ;            =             &= nbsp;           &n= bsp;  | \_____/ |
   Achim = Blumensath          &nb= sp;           &nbs= p;            = ;       \O/ \___/\ |
   Mathematische Grundlagen der = Informatik          &nb= sp;        =3Do=3D  \ /\ = \|
   = www-mgi.informatik.rwth-aachen.de/~blume     &nb= sp;            = /"\   o----|
________________________________________________________________= ____\___|

------_=_NextPart_001_01C34775.00FF8F80--