Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with SMTP id p7TJSpQq005528 for ; Mon, 29 Aug 2011 21:28:52 +0200 Received: (qmail 16457 invoked by alias); 29 Aug 2011 19:28:46 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 29 Aug 2011 19:28:46 -0000 Received: from relay2.uni-heidelberg.de (EHLO relay2.uni-heidelberg.de) [129.206.210.211] by mx0.gmx.net (mx052) with SMTP; 29 Aug 2011 21:28:46 +0200 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 p7TJPfUv019425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Aug 2011 21:25:41 +0200 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 p7TElnlA006217; Mon, 29 Aug 2011 21:25:41 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1612761 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 29 Aug 2011 21:25:41 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id p7TJPfK4011376 for ; Mon, 29 Aug 2011 21:25:41 +0200 Received: from anchor-post-2.mail.demon.net (anchor-post-2.mail.demon.net [195.173.77.133]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id p7TJPTHr019382 for ; Mon, 29 Aug 2011 21:25:33 +0200 Received: from cremornelane.demon.co.uk ([80.177.25.195] helo=palladium.local) by anchor-post-2.mail.demon.net with esmtp (Exim 4.69) id 1Qy7Sb-00051j-kd for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 29 Aug 2011 19:25:29 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 References: <4E5B6BF7.80208@morningstar2.co.uk> <4E5BA7FC.8060705@latex-project.org> <4E5BBD69.6040403@gmx.de> X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Message-ID: <4E5BE7A9.6040505@morningstar2.co.uk> Date: Mon, 29 Aug 2011 20:25:29 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: missing or unclear concept documentation To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <4E5BBD69.6040403@gmx.de> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Sender is in whitelist: joseph.wright@MORNINGSTAR2.CO.UK); Detail=5D7Q89H36p4L00VTXC6D4q0N+AH0PUCnBi0P5cROEGjO+pG7NAH/K+tf9SrVFtpLrKONl 2T9EL4W4U4jgzLbnCcGpk1z/zwmKT/K1fv3lD0=V1; X-Resent-By: Forwarder X-Resent-For: rainer.schoepf@gmx.net X-Resent-To: rainer@rainer-schoepf.de Status: R X-Status: X-Keywords: X-UID: 6847 On 29/08/2011 17:25, Arno Trautmann wrote: > And, maybe even more important, at least for > me personally, a kind-of-a-roadmap where the development is going. That > may be in three parts, short-term, middle-term and long-term. Maybe it > is my personal fault, but I have no idea of where L3 is supposed to go, > in which steps, etc. If it is the policy of the team to keep this > non-public, it is sad, but ok. If not, it should be made more public – > that doesn't have to be much text, nor must it be too concrete or > ultimate decisions. The L3 news are a good step in that direction, but > they mostly “only” report on what has happened. Roadmap-wise, things are rather diffuse. I guess that my (personal) view is something like Short-term ---------- 1) Potential re-implementation of l3fp in an expandable form. Bruno is looking at this (see l3trial on the SVN/GitHub for details). 2) Create some basic driver code such that l3coffins works in format mode (using a 'hacked up' output routine). 3) Look again at box affine operations, again to support coffins beyond LaTeX2e. 4) Take a look back over the 'niggles' list (the issues on GitHub), and try to deal with some of them. Medium-term ----------- 5) Get some form of decisions made on the galley: does it work, are we going the right way, etc. 6) Sort out issue of expandable versus protected definitions of document commands (in xparse). 7) Font selection (mainly a port of NFSS) and loading mechanism (fontspec-based plus something for pdfTeX). Long-term --------- 10) Output routine: get xor 'up to scratch'. ... Some of these are ongoing: for example, work on the galley has actually ongoing. To some extent, the divisions here depend on how significant the stuff is, as well as the likely time-frame. Once we get (5), (7) and (10) done, we'll be in a position to build a format which can typeset something. My view there is that this will start *really* basic, and probably also somewhat 'flexible', and that we'll then add 'stuff' as testing takes place. -- Joseph Wright