Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Wed, 9 Jul 2003 23:56:26 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h69LuNPP022249 for ; Wed, 9 Jul 2003 23:56:24 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h69Laumx010002; Wed, 9 Jul 2003 23:37:03 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34664.F1912100" 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 h68M02tj007911; Wed, 9 Jul 2003 23:32:06 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 2223 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 9 Jul 2003 23:32:06 +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 h69LW6M9021711 for ; Wed, 9 Jul 2003 23:32:06 +0200 Received: from smtp.albany.edu (mail1.csc.albany.edu [169.226.1.133]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h69LVcGl028723 for ; Wed, 9 Jul 2003 23:31:39 +0200 (MET DST) Received: from hilbert.math.albany.edu (hilbert.math.albany.edu [169.226.23.52]) by smtp.albany.edu (8.12.5/8.12.5) with ESMTP id h69LVZU4000087 for ; Wed, 9 Jul 2003 17:31:35 -0400 (EDT) Received: (from hammond@localhost) by hilbert.math.albany.edu (8.12.5/8.12.5/Submit) id h69LVYBx021428; Wed, 9 Jul 2003 17:31:34 -0400 (EDT) In-Reply-To: <3F0BE0E6.E87B2479@MartinHensel.de> Lines: 32 References: <3BFEACE361F5BF429DD1DA593E3A7C0922406A@xch-nw-28.nw.nos.boeing.com> <3F0BE0E6.E87B2479@MartinHensel.de> Return-Path: X-OriginalArrivalTime: 09 Jul 2003 21:56:26.0238 (UTC) FILETIME=[F1B571E0:01C34664] User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -32.8 () EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,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: Wed, 9 Jul 2003 22:31:34 +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: AcNGZPHQfEFfzKAURYCMzUpkhUjgXg== From: "William F Hammond" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4671 This is a multi-part message in MIME format. ------_=_NextPart_001_01C34664.F1912100 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Martin Hensel writes: > My decision was made mainly in three steps. The first two are mainly > concerned with better visual perception, the last one with the > writer's and reader's memory. > > 1. Commands should enclosed in brackets. . . . > 2. Command parameters are included in the command enclosure. . . . > 3. The combined position and named parameters . . . The issues underlying these points have been addressed in the GELLMU Project: http://www.albany.edu/~hammond/gellmu/ . More to the point, the syntactic translator enforces syntax, and SGML/XML validation enforces the correctness of both markup vocabulary and document structure. That said, I would not propose to change the syntax of LaTeX itself unless it might be in conjunction with the introduction in LaTeX of \documenttype parallel to \documentclass. I would also like to point out that Texinfo, the elderly language of the GNU Documentation System, has a rigid syntax that may be considered, apart from notation, responsive to the issues in "syntax.pdf". Note that "sgmltexi" is an SGML model for Texinfo. And please note that LaTeX, not Texinfo, is a backend for GELLMU though Texinfo could be a backend, too. -- Bill ------_=_NextPart_001_01C34664.F1912100 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:

> My decision was made mainly in three steps. The = first two are mainly
> concerned with better visual perception, the = last one with the
> writer's and reader's memory.
>
> 1. Commands should enclosed in brackets.
. . .
> 2. Command parameters are included in the = command enclosure.
. . .
> 3. The combined position and named = parameters
. . .

The issues underlying these points have been addressed = in the GELLMU
Project: http://www.albany.edu/~ha= mmond/gellmu/ .  More to the point,
the syntactic translator enforces syntax, and = SGML/XML validation
enforces the correctness of both markup vocabulary = and document
structure.

That said, I would not propose to change the syntax of = LaTeX itself
unless it might be in conjunction with the = introduction in LaTeX of
\documenttype parallel to \documentclass.

I would also like to point out that Texinfo, the = elderly language of
the GNU Documentation System, has a rigid syntax that = may be
considered, apart from notation, responsive to the = issues in
"syntax.pdf".  Note that = "sgmltexi" is an SGML model for Texinfo.
And please note that LaTeX, not Texinfo, is a backend = for GELLMU
though Texinfo could be a backend, too.

          &nbs= p;            = ;            = -- Bill

------_=_NextPart_001_01C34664.F1912100--