Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Sat, 5 Jul 2003 06:52:58 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h654qtPP002984 for ; Sat, 5 Jul 2003 06:52:56 +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 h654llGl016117; Sat, 5 Jul 2003 06:47:47 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C342B1.4DE4F100" 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 h64M04tU031569; Sat, 5 Jul 2003 06:44:16 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 0447 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 5 Jul 2003 06:44:16 +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.2/8.12.2/SuSE Linux 0.6) with ESMTP id h654YGpU001334 for ; Sat, 5 Jul 2003 06:34:16 +0200 Received: from smtp.web.de (smtp03.web.de [217.72.192.158]) by relay.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h654Zpmp021089 for ; Sat, 5 Jul 2003 06:35:51 +0200 (MET DST) Received: from [217.227.91.110] (helo=zarniwoop.ms25.local) by smtp.web.de with esmtp (TLSv1:DES-CBC3-SHA:168) (WEB.DE 4.98 #232) id 19Yem5-00051f-00 for LATEX-L@listserv.uni-heidelberg.de; Sat, 05 Jul 2003 06:35:49 +0200 Received: from zarniwoop.ms25.local (reinhard@localhost [127.0.0.1]) by zarniwoop.ms25.local (8.12.9/8.12.9) with ESMTP id h654ZkQC012351 for ; Sat, 5 Jul 2003 06:35:46 +0200 In-Reply-To: <3F058C1B.32BF3DF5@MartinHensel.de> References: <3F058C1B.32BF3DF5@MartinHensel.de> Return-Path: X-Mailer: VM 7.00 under Emacs 20.7.2 X-OriginalArrivalTime: 05 Jul 2003 04:52:58.0278 (UTC) FILETIME=[4E0F5C60:01C342B1] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -15.7 () IN_REP_TO,REFERENCES,USER_AGENT_VM Content-class: urn:content-classes:message Subject: Invitation for discussion: My suggestion for a LaTeX3 syntax Date: Sat, 5 Jul 2003 05:35:46 +0100 Message-ID: A<16134.21922.541305.541547@zarniwoop.ms25.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Invitation for discussion: My suggestion for a LaTeX3 syntax Thread-Index: AcNCsU448ZilqkfXSfWJVrRs4h2g/Q== From: "Reinhard Kotucha" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4635 This is a multi-part message in MIME format. ------_=_NextPart_001_01C342B1.4DE4F100 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >>>>> "Martin" =3D=3D Martin Hensel writes: > I decided to optimize the LaTeX user syntax with > ergonomics/usability in mind. The way spaces after commands are treated follows a simple rule. This rule is so simple that it makes no sense to give it up. A linebreak should always behave like a space token. This is quite natural and I really doubt that beginners have problems here. In LaTeX2e there are some commands that take a lot of parameters. LaTeX3 will hopefully make more use of keyval, which solves this problem in an elegant way. Regards, Reinhard ------_=_NextPart_001_01C342B1.4DE4F100 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Invitation for discussion: My suggestion for a LaTeX3 = syntax

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

    > I decided to optimize the = LaTeX user syntax with
    > ergonomics/usability in = mind.

The way spaces after commands are treated follows a = simple rule.  This
rule is so simple that it makes no sense to give it = up.

A linebreak should always behave like a space = token.  This is quite
natural and I really doubt that beginners have = problems here.

In LaTeX2e there are some commands that take a lot of = parameters.
LaTeX3 will hopefully make more use of keyval, which = solves this
problem in an elegant way.

Regards,
  Reinhard

------_=_NextPart_001_01C342B1.4DE4F100--