Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Jun 2006 00:15:45 +0200 Received: by mail.proteosys.com (8.12.11.20060308/8.12.2) with ESMTP id k51MFdSC028616 for ; Fri, 2 Jun 2006 00:15:40 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.13.4/8.13.1) with ESMTP id k51MAK8C011129 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Jun 2006 00:10:20 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id k51M1GUb017425; Fri, 2 Jun 2006 00:10:14 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 14.3) with spool id 1288318 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 2 Jun 2006 00:10:13 +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 k51MADKn017777 for ; Fri, 2 Jun 2006 00:10:13 +0200 Received: from atlas.informatik.uni-freiburg.de (atlas.informatik.uni-freiburg.de [132.230.150.3]) by relay.uni-heidelberg.de (8.13.4/8.13.1) with ESMTP id k51MA64g011100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 2 Jun 2006 00:10:09 +0200 Received: from remote218-12.home.uni-freiburg.de ([132.230.218.12] helo=m0A023293.vpn.uni-freiburg.de) by atlas.informatik.uni-freiburg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.60) (envelope-from ) id 1FlvMh-0007TY-VT for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 02 Jun 2006 00:10:04 +0200 Received: by m0A023293.vpn.uni-freiburg.de (Postfix, from userid 500) id F3B7536B2A; Fri, 2 Jun 2006 00:10:02 +0200 (CEST) Mail-Followup-To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE References: <20060427182251.GA23586@m0A023293.vpn.uni-freiburg.de> <20060530155648.GA16268@m0A023293.vpn.uni-freiburg.de> <20060531192925.GA7290@m0A023293.vpn.uni-freiburg.de> <17535.21403.129121.579232@morse.mittelbach-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Message-ID: <20060601221001.GA21524@m0A023293.vpn.uni-freiburg.de> Date: Fri, 2 Jun 2006 00:10:02 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Heiko Oberdiek Subject: Re: LaTeX Release 2005/12/01 To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <17535.21403.129121.579232@morse.mittelbach-online.de> Precedence: list X-ProteoSys-SPAM-Score: 0 () X-Scanned-By: MIMEDefang at proteosys.com Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 01 Jun 2006 22:15:45.0270 (UTC) FILETIME=[ED973160:01C685C8] Status: R X-Status: X-Keywords: X-UID: 4960 Hello Frank, On Thu, Jun 01, 2006 at 10:52:43PM +0200, Frank Mittelbach wrote: > Heiko, > > > > * I have written a wrapper file that merges all the ltnews??.tex > > > documents: ltnews.pdf contain all LaTeX News issues 1--17. > > I wonder if it is best to have the ltnews in there in cronological order or > better in reverse cronological order. See below. > not even sure it is best to have them all together. * For example, I don't want to open upto 17 (seventeen!) files to find something. Thus I just call "texdoc ltnews" and ask the PDF viewer search function. * Second advantage, the directory listing of TDS:doc/latex/base does look less cluttered. > most people will be only > interested in the latest information so reverse might be the best order It would be easy to implement. But there are some reasons against: * Natural order is chronological. The page and time axis show in the same direction. * Confusion: If I look at books that deal with history, then I have never seen one that starts at the 21th century and ends at the big bang. * Inconsistent: Look at the "Change History" of the LaTeX documentation (source2e, multicol, ...). Here you have already decided against reverse chronological order. Yours sincerely Heiko