Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Thu, 10 Jul 2003 22:03:51 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h6AK3ncH002983 for ; Thu, 10 Jul 2003 22:03:50 +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 h6AJjump025291; Thu, 10 Jul 2003 21:45:56 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3471E.61AFAD80" 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 h69M03et021895; Thu, 10 Jul 2003 21:45:39 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 1337 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 10 Jul 2003 21:45:39 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h6AJjdM9031466 for ; Thu, 10 Jul 2003 21:45:39 +0200 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.185]) by relay.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h6AJjjmp025269 for ; Thu, 10 Jul 2003 21:45:46 +0200 (MET DST) Received: from [212.227.126.162] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19ahMQ-0003Dm-00 for LATEX-L@listserv.uni-heidelberg.de; Thu, 10 Jul 2003 21:45:46 +0200 Received: from [212.159.41.28] (helo=MartinHensel.de) by mrelayng.kundenserver.de with asmtp (SSLv3:RC4-MD5:128) (Exim 3.35 #1) id 19ahMP-0006dC-00 for LATEX-L@listserv.uni-heidelberg.de; Thu, 10 Jul 2003 21:45:46 +0200 References: <3BFEACE361F5BF429DD1DA593E3A7C0922406A@xch-nw-28.nw.nos.boeing.com> <3F0BE0E6.E87B2479@MartinHensel.de> Return-Path: X-Mailer: Mozilla 4.75 [de] (Win98; U) X-OriginalArrivalTime: 10 Jul 2003 20:03:51.0956 (UTC) FILETIME=[62418D40:01C3471E] X-Accept-Language: de,en X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -10.1 () QUOTED_EMAIL_TEXT,REFERENCES,USER_AGENT_MOZILLA_XM Content-class: urn:content-classes:message Subject: Re: Invitation for discussion: My suggestion for a LaTeX3 syntax Date: Thu, 10 Jul 2003 20:45:36 +0100 Message-ID: A<3F0DC260.183ED82C@MartinHensel.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Invitation for discussion: My suggestion for a LaTeX3 syntax Thread-Index: AcNHHmJb5jCh4FWPSeGulmHCnzrmbg== From: "Martin Hensel" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4675 This is a multi-part message in MIME format. ------_=_NextPart_001_01C3471E.61AFAD80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable William F Hammond schrieb: > > My decision was made mainly in three steps. > The issues underlying these points have been addressed in the GELLMU > Project: http://www.albany.edu/~hammond/gellmu/ . Sorry, I don't see your point. My conviction is that the current LaTeX syntax can be improved with regard to legibility. As far as I understand GELLMU, this project tries to use the LaTeX syntax to produce HTML documents, for instance. I don't see how it is concerned with improving the LaTeX syntax. Maybe you can point me to the correct page? > 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'm not sure if you mean document type in the same sense as GELLMU (\documenttype{html}). Then there may be a misunderstanding. Nevertheless, I was told that LaTeX3 will be able to support several syntaxes. The statement, which syntax is used in a document may be what you ment by \documenttype. > 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. Sorry, I'm not very understanding today. What issues do you mean in particular? As far as I can see, Texinfo uses only commands that take no or one parameter. examples: @settitle title @url{uniform-resource-locator} The main issues I thought about in LaTeX are caused by commands that can take several more. Sorry that I'm answering with a lot more questions. Martin ------_=_NextPart_001_01C3471E.61AFAD80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Invitation for discussion: My suggestion for a LaTeX3 = syntax

William F Hammond schrieb:
> > My decision was made mainly in three = steps.

> The issues underlying these points have been = addressed in the GELLMU
> Project: http://www.albany.edu/~ha= mmond/gellmu/ .

Sorry, I don't see your point. My conviction is that = the current LaTeX
syntax can be improved with regard to legibility. As = far as I
understand GELLMU, this project tries to use the = LaTeX syntax to
produce HTML documents, for instance. I don't see how = it is concerned
with improving the LaTeX syntax. Maybe you can point = me to the correct
page?

> 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'm not sure if you mean document type in the same = sense as GELLMU
(\documenttype{html}). Then there may be a = misunderstanding.
Nevertheless, I was told that LaTeX3 will be able to = support several
syntaxes. The statement, which syntax is used in a = document may be
what you ment by \documenttype.

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

Sorry, I'm not very understanding today. What issues = do you mean in
particular?

As far as I can see, Texinfo uses only commands that = take no or one
parameter.
  examples: @settitle title
          &nbs= p; @url{uniform-resource-locator}
The main issues I thought about in LaTeX are caused = by commands that
can take several more.

Sorry that I'm answering with a lot more = questions.

Martin

------_=_NextPart_001_01C3471E.61AFAD80--