Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 11 Aug 2009 11:17:50 +0200 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n7B9HmgZ007042 for ; Tue, 11 Aug 2009 11:17:48 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id n7B9E2fV028055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Aug 2009 11:14:02 +0200 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n7B7w6Ri010332; Tue, 11 Aug 2009 11:14:00 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 287783 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 11 Aug 2009 11:14:00 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n7B9E0Cc001183 for ; Tue, 11 Aug 2009 11:14:00 +0200 Received: from pluto.open.ac.uk (pluto.open.ac.uk [137.108.145.32]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id n7B9Dfco011783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 11 Aug 2009 11:13:46 +0200 Received: from laurel.open.ac.uk ([137.108.170.71]) by pluto.open.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1ManQL-00075v-JT for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 11 Aug 2009 10:13:41 +0100 Received: from KIELDERCMS1.open.ac.uk ([137.108.140.186]) by LAUREL.open.ac.uk ([137.108.170.71]) with mapi; Tue, 11 Aug 2009 10:13:41 +0100 Thread-Topic: xparse Thread-Index: AcoaYOvOc8oYK02ZSeCUoicU4vT1vgAAn5gw References: <4A7921CF.5020803@morningstar2.co.uk> <4A7A1505.4040604@residenset.net> <4A7AD930.2090106@residenset.net> <8516B615-51AA-4D90-BB7D-A9E122AA0335@gmail.com> <4A804317.6050909@morningstar2.co.uk> <4A80469B.5040305@morningstar2.co.uk> <4A804ED7.4040305@morningstar2.co.uk> <4A812A23.2000808@morningstar2.co.uk> <30090124-F668-4FB3-8F03-5CB615F80D6F@gmail.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id n7B9E0Cc001184 Message-ID: Date: Tue, 11 Aug 2009 10:13:40 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: "J.Fine" Subject: Re: xparse To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <30090124-F668-4FB3-8F03-5CB615F80D6F@gmail.com> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -6.599 () BAYES_00,RCVD_IN_DNSWL_MED X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 11 Aug 2009 09:17:50.0613 (UTC) FILETIME=[9965FC50:01CA1A64] Status: R X-Status: X-Keywords: X-UID: 5878 Will Robertson wrote: > On 11/08/2009, at 6:01 PM, J.Fine wrote: > > > There are some interesting ideas here, but why implement them in TeX > > macros? How will you translate LaTeX documents into XML? > > > > Surely to do this you will need a LaTeX->XML translator written in / > > some other language/. And once you have that, why do you need an > > implementation written in TeX macros? > > Simple: I prefer to write in LaTeX than in XML. I have yet to see an > XML dialect I wish to write by hand; I originally thought Gellmu was > similar to such a thing, but I've yet to fully understand -- through > lack of time -- the relationship between SGML/XML and the Gellmu syntax. My suggestion allows you to write in LaTeX, or a similar syntax. I'm not suggesting you author directly in XML. As you point out, Gellmu takes this sort of approach. I suggest you explore it before spending further time on the TeX macro route, in case it provides something better. > Also, xparse will be used for LaTeX2e documents and packages as well, > which are very much rooted to the TeX world. This is a good point, but must be balanced against the awfulness of programming in TeX macros. > It's not clear to me what is the best way to approach the problem of > HypotheticalLaTeX3 to XML. Half of me wants the XML to be generated > from LaTeX macros as they expand, \write-ing the necessary structural > information and transforming the input text as the document is typeset > to PDF. But that's mostly just a silly idea. I want documents that can be readily converted to XML. This is a future requirement for me. TeX macros is not. -- Jonathan The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302).