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 p28DQPl8022316 for ; Tue, 8 Mar 2011 14:26:26 +0100 Received: (qmail 10242 invoked by alias); 8 Mar 2011 13:26:20 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 08 Mar 2011 13:26:19 -0000 Received: from relay2.uni-heidelberg.de (EHLO relay2.uni-heidelberg.de) [129.206.210.211] by mx0.gmx.net (mx061) with SMTP; 08 Mar 2011 14:26:19 +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 p28DONar026377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Mar 2011 14:24:23 +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 p28DBSAQ011347; Tue, 8 Mar 2011 14:24:22 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1251091 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 8 Mar 2011 14:24:22 +0100 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 p28DOMbP004648 for ; Tue, 8 Mar 2011 14:24:22 +0100 Received: from mail-gx0-f177.google.com (mail-gx0-f177.google.com [209.85.161.177]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id p28DOEPD006671 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for ; Tue, 8 Mar 2011 14:24:21 +0100 Received: by gxk21 with SMTP id 21so3479432gxk.22 for ; Tue, 08 Mar 2011 05:24:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.150.61.13 with SMTP id j13mr5959244yba.180.1299590654638; Tue, 08 Mar 2011 05:24:14 -0800 (PST) Received: by 10.147.169.4 with HTTP; Tue, 8 Mar 2011 05:24:13 -0800 (PST) References: <4D738DB1.3020807@gmx.de> <4D738FA8.8050509@morningstar2.co.uk> <4D739437.4040802@gmx.de> <4D73A4B8.5060108@morningstar2.co.uk> <4D73C1FC.4050907@gmx.de> <4D73CD52.4090800@yahoo.de> <4D73D6AA.9080806@gmx.de> <4D740146.3040500@morningstar2.co.uk> Content-Type: text/plain; charset=windows-1252 X-Spam-Whitelist: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id p28DOMbP004649 Message-ID: Date: Tue, 8 Mar 2011 08:24:13 -0500 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Bruno Le Floch Subject: Re: format? To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <4D740146.3040500@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=5D7Q89H36p77e5KAPs1l6v/Sb97LojnDtMgfETrECMLUO9erHzOJe+OynZRhvlGqb5A0X bbiCt2rAnnct/NAlbHMvoAL6GY+23tB3khNK7avqRsgMMVBwlWgrgcyEiCy6eQ7DbfhonniFyqTI PpJNA==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: 6648 > As we need things, they are added. Of course, others should feel free to > write things and send them along :-) (I have some more serious thoughts > on that, but need to work some other items through yet. Perhaps next > month if I work hard at it.) > >> I was thinking about this, but that would go too far. At least for a >> short-term test version, that would be too much packages. >> For long-term considerations, they would be nice to have in the format – >> but this would blow up the size strongly, wouldn't it? We could imagine >> a "plain LaTeX" format without them and a "bloated LaTeX" including … ;) A plea for slow computers: I don't know how much having a format will accelerate loading, but I guess that adding tikz would be too much. >>> Fixltx2e has already been mentioned and would probably the first >>> candidate for inclusion in the format. >> >> Yes. > > For the moment, I think LaTeX3 'release' packages + fontspec + fixltx2e > will do :-) (Long-term I would like to imagine most of the material > listed above being part of LaTeX3. However, that is a way off and we > should probably not overdo things just at the moment.) Perhaps the {trace} package (although it seems included in l3chk, but not loaded by expl3?)? -- Bruno Le Floch