Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Fri, 4 Jul 2003 19:14:20 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h64HEIPP001372 for ; Fri, 4 Jul 2003 19:14:19 +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 h64H8RGl020059; Fri, 4 Jul 2003 19:08:27 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3424F.B4D1BE00" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h63M039K020122; Fri, 4 Jul 2003 19:06:49 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 1075 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 4 Jul 2003 19:06:49 +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.2/8.12.2/SuSE Linux 0.6) with ESMTP id h64GunpU029935 for ; Fri, 4 Jul 2003 18:56:49 +0200 Received: from localhost.localdomain (p3EE20BC5.dip.t-dialin.net [62.226.11.197]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h64GwMGl019086 for ; Fri, 4 Jul 2003 18:58:23 +0200 (MET DST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id h64GwT6M032761 for ; Fri, 4 Jul 2003 18:58:30 +0200 Received: (from dak@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id h64GwTW5032757; Fri, 4 Jul 2003 18:58:29 +0200 In-Reply-To: <3F05A7AB.DAE49A64@MartinHensel.de> Lines: 19 References: <3F058C1B.32BF3DF5@MartinHensel.de> <3F05A7AB.DAE49A64@MartinHensel.de> Return-Path: X-OriginalArrivalTime: 04 Jul 2003 17:14:20.0927 (UTC) FILETIME=[B55F30F0:01C3424F] User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -29.5 () EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA Content-class: urn:content-classes:message Subject: Re: Invitation for discussion: My suggestion for a LaTeX3 syntax Date: Fri, 4 Jul 2003 17:58:28 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Invitation for discussion: My suggestion for a LaTeX3 syntax Thread-Index: AcNCT7V8dXYPUR+eT6OyT96RnSwASA== From: "David Kastrup" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4634 This is a multi-part message in MIME format. ------_=_NextPart_001_01C3424F.B4D1BE00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Martin Hensel writes: > Finally, here it is: > > http://www.MartinHensel.de/LaTeX3/syntax.pdf Do you actually know the internals of TeX? Anyhow, there is little sense in calling anything "LaTeX" which looks entirely different. There are some XML DTDs that do something similar to what you seem to want to do, maybe they will suit whatever application you had in mind. There is a large variety of tools and material available about LaTeX that it makes little sense to cast away for mostly cosmetical reasons. In particular, I fail to see a good reason to cook up an arbitrary syntax that is neither LaTeX nor XML, when XML would probably fit your goals perfectly. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum ------_=_NextPart_001_01C3424F.B4D1BE00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Invitation for discussion: My suggestion for a LaTeX3 = syntax

Martin Hensel <mail@MARTINHENSEL.DE> = writes:

> Finally, here it is:
>
> http://www.MartinHe= nsel.de/LaTeX3/syntax.pdf

Do you actually know the internals of TeX?  = Anyhow, there is little
sense in calling anything "LaTeX" which = looks entirely different.
There are some XML DTDs that do something similar to = what you seem to
want to do, maybe they will suit whatever application = you had in mind.

There is a large variety of tools and material = available about LaTeX
that it makes little sense to cast away for mostly = cosmetical
reasons.  In particular, I fail to see a good = reason to cook up an
arbitrary syntax that is neither LaTeX nor XML, when = XML would
probably fit your goals perfectly.

--
David Kastrup, Kriemhildstr. 15, 44793 Bochum

------_=_NextPart_001_01C3424F.B4D1BE00--