Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 6 Jan 2003 17:12:32 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h06GCU6C013186 for ; Mon, 6 Jan 2003 17:12:30 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h06G3PEV009631; Mon, 6 Jan 2003 17:03:25 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2B59E.6ABC9800" 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 h064ACaQ008642; Mon, 6 Jan 2003 16:56:51 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 5307 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 6 Jan 2003 16:56:51 +0100 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 h06FupTk011653 for ; Mon, 6 Jan 2003 16:56:51 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h06G3IEV009612 for ; Mon, 6 Jan 2003 17:03:18 +0100 (MET) Received: from [212.227.126.155] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 18VZig-0008AZ-00 for LATEX-L@listserv.uni-heidelberg.de; Mon, 06 Jan 2003 17:03:18 +0100 Received: from [80.129.1.68] (helo=istrati.mittelbach-online.de) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 18VZig-0003Am-00 for LATEX-L@listserv.uni-heidelberg.de; Mon, 06 Jan 2003 17:03:18 +0100 Received: (from frank@localhost) by istrati.mittelbach-online.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id h06G2mw01806; Mon, 6 Jan 2003 17:02:48 +0100 In-Reply-To: References: <15897.10031.19948.331055@cs.anu.edu.au> <20030106130656259998.GyazMail.jbezos@wanadoo.es> Return-Path: X-Mailer: VM 6.96 under Emacs 20.7.1 X-OriginalArrivalTime: 06 Jan 2003 16:12:32.0689 (UTC) FILETIME=[6B25BA10:01C2B59E] X-Authentication-Warning: istrati.mittelbach-online.de: frank set sender to frank@mittelbach-online.de using -f X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -0.7 () IN_REP_TO,REFERENCES,SPAM_PHRASE_00_01,X_AUTH_WARNING Content-class: urn:content-classes:message Subject: Re: Proposed change of policy Date: Mon, 6 Jan 2003 17:02:48 +0100 Message-ID: A<15897.43176.632097.41316@istrati.mittelbach-online.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Proposed change of policy Thread-Index: AcK1nmtB4TlmSOErQ06JOZgpAmKeRQ== From: "Frank Mittelbach" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4399 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2B59E.6ABC9800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable This is still not a `policy statement' but just to say that we are = listening hard and we do not entirely disagree with any of the arguments (even = when they are contradictory:-). The Team is of course aware of the useful facilities provided by e-TeX = and is also in close contact with the omega developers. Robin's summary of the current situation is very good and we are aware = that we need to provide a reasonably detailed and definite answer to (almost) = his question: how should we best proceed from here? and that the answer should be, if possible, one that takes account of = the needs of different devlopers whilst avoiding the dangers of trying to be all = things to all devlopers. Frank and Chris ------_=_NextPart_001_01C2B59E.6ABC9800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Proposed change of policy

This is still not a `policy statement' but just to say = that we are listening
hard and we do not entirely disagree with any of the = arguments (even when they
are contradictory:-).

The Team is of course aware of the useful facilities = provided by e-TeX and is
also in close contact with the omega = developers.

Robin's summary of the current situation is very good = and we are aware that we
need to provide a reasonably detailed and definite = answer to (almost) his
question:

  how should we best proceed from here?

and that the answer should be, if possible, one that = takes account of the needs
of different devlopers whilst avoiding the dangers of = trying to be all things
to all devlopers.


Frank and Chris

------_=_NextPart_001_01C2B59E.6ABC9800--