Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 20 Jan 2009 11:41:57 +0100 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id n0KAft7O022357 for ; Tue, 20 Jan 2009 11:41:56 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id n0KAc9fN030324 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jan 2009 11:38:09 +0100 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n0JN6O83030737; Tue, 20 Jan 2009 11:38:01 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 172806 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 20 Jan 2009 11:38:00 +0100 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n0KAc0HN031041 for ; Tue, 20 Jan 2009 11:38:00 +0100 Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.246]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id n0KAbvjT030193 for ; Tue, 20 Jan 2009 11:38:01 +0100 Received: by rv-out-0708.google.com with SMTP id c5so3229014rvf.10 for ; Tue, 20 Jan 2009 02:37:55 -0800 (PST) Received: by 10.141.153.16 with SMTP id f16mr1052348rvo.283.1232447874854; Tue, 20 Jan 2009 02:37:54 -0800 (PST) Received: from ?129.127.15.244? ([129.127.15.244]) by mx.google.com with ESMTPS id g31sm12413424rvb.4.2009.01.20.02.37.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 20 Jan 2009 02:37:53 -0800 (PST) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v930.3) References: <49758499.5080004@morningstar2.co.uk> <68c491a60901200152y55297cc3wa784e4082ceb5e3f@mail.gmail.com> X-Mailer: Apple Mail (2.930.3) X-Spam-Whitelist: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id n0KAc0HN031042 Message-ID: <52113C28-0F76-4B7B-B306-DC00E20A2F03@gmail.com> Date: Tue, 20 Jan 2009 21:07:49 +1030 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Will Robertson Subject: Re: Key points of LaTex3 To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <68c491a60901200152y55297cc3wa784e4082ceb5e3f@mail.gmail.com> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -2.599 () BAYES_00 X-Scanned-By: MIMEDefang 2.64 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 20 Jan 2009 10:41:57.0972 (UTC) FILETIME=[B8009940:01C97AEB] Status: R X-Status: X-Keywords: X-UID: 5599 On 20/01/2009, at 8:22 PM, Martin Schröder wrote: > 2009/1/20 Joseph Wright : >> I've had a go at summarising the key aims of LaTeX3, as I understand >> them, on my blog (http://www.texdev.net). I'd be interested to know > > Very interesting, thanks. > > However, most of these aims bring no direct benefit for the user, > while other areas where LaTeX is sorely showing it's age, e.g. > hyperref, are missing. I think any LaTeX3 release without a direct > integration of hyperref's features will not attract many users. The > same goes for document classes (e.g. KOMA) and a much better > integration of utf8 and fonts. Definitely, of course. It's just that most of the work done so far and available at the moment is in the area of the underlying groundwork (i.e., the expl3 modules and the xpackages) before this sort of thing can be attempted. Designing the user-level interfaces will be one of the last pieces of the puzzle, when we know what features we have to play with. There will probably be several iterations between specifying what we want the user interface to be and writing the code to implement it. The vast scope of material on CTAN gives us a pretty good starting point for working out what should be included by default. As Frank has mentioned before, the functionality described in the entirety of The LaTeX Companion could be considered a first approximation of what a LaTeX3 user interface might be. Writing a specification for a LaTeX3 interface is a huge task for a small team to tackle, perhaps greater in scope than writing from scratch the entire HTML and CSS specifications. Somewhat of a daunting task. It's probably a foregone conclusion that we'll need further help from members of the community when the time comes for doing this. But it's never to early to start... Cheers, Will P.S. (While I am working on some LaTeX3 code right now, these are obviously entirely my own opinions and might even be in opposition to the ideas of other members of the LaTeX3 team!)