Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 6 Jan 2003 10:12:44 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h069Cf6C011777 for ; Mon, 6 Jan 2003 10:12:42 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2B563.C584CE00" 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 h0693SEV005698; Mon, 6 Jan 2003 10:03:28 +0100 (MET) 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 h064ACVY008642; Mon, 6 Jan 2003 09:56:52 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 5026 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 6 Jan 2003 09:56:52 +0100 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h068kqTk009451 for ; Mon, 6 Jan 2003 09:46:52 +0100 Received: from pcmail.mpae.gwdg.de (pcmail.mpae.gwdg.de [134.76.238.47]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h068rKwO024265 for ; Mon, 6 Jan 2003 09:53:20 +0100 (MET) Content-class: urn:content-classes:message Return-Path: X-MimeOLE: Produced By Microsoft Exchange V6.5 X-OriginalArrivalTime: 06 Jan 2003 09:12:44.0115 (UTC) FILETIME=[C5965A30:01C2B563] x-mime-autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id h068kqTk009452 X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: 0.9 () DEAR_SOMEBODY,SPAM_PHRASE_02_03 Subject: Update to parskip.sty and backward compatibility Date: Mon, 6 Jan 2003 09:53:13 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Update to parskip.sty and backward compatibility Thread-Index: AcK1YYMgvDFO3SFPEdeQHgAA+Aa3tg== From: "Daly Dr., Patrick" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4391 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2B563.C584CE00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable This is an informal bug report that I am sending to Robin Fairbairns. I cc it to the LaTeX-L list because although it is fairly minor, it does involves certain fundamental issues such as backward compatibility and = who maintains older packages. Dear Robin, In making preparations for the 4th edition of A Guide to LaTeX, I looked = into the parskip.sty package from the TeXLive 7 CD, really just to check its = date. There I noticed that you have updated it, adding an option parfill, and fixing up the double spaced table of contents. I always had my own way = of getting around that, when I wanted to get around it. Shortly after, I was working on a 500 page document (out Institute = Yearbook), made some minor corrections, and then noticed that the entire document = was 2 pages shorter than it was before. Horrified, I discovered it was the = table of contents that was now shorter, single instead of double spaced. It then clicked that parskip.sty had been altered, and I was processing the = document now on my laptop, the only computer around with the revised parskip. Had I not coincidentally seen the change in parskip shortly before this, = I would have been extremely puzzled. (I guess I would have discovered the = cause fairly quickly.) But this should not happen. Your change to parskip is welcomed, but it should not be so that older documents are processed differently than before. I would call the double-spaced table of = contents a feature, not a bug. It is not necessarily a bad thing, although one may = not want it all the time. And many people may have got used to it, and even expect it. I would prefer to see your fix-up as an option, say notoc, so that the default behaviour is the double-spaced listings, as it has been for the = last 13 years. Then one must actively select single-spacing with this option, avoiding unexpected surprises. I am not sure who is now maintaining parskip.sty officially, but since = you made the last change, I guess it is your court now. Regards, Patrick -------------------------------------------------------------------------= ---- Dr. Patrick W. Daly Tel. [+49] 5556-979-279 Max-Planck-Institut fuer Aeronomie Fax. [+49] 5556-979-240 Max-Planck-Str. 2 Mob. [+49] 175-162-1811 D-37191 Katlenburg-Lindau Email: daly@linmpi.mpg.de Germany -------------------------------------------------------------------------= ---- ------_=_NextPart_001_01C2B563.C584CE00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Update to parskip.sty and backward compatibility

This is an informal bug report that I am sending to = Robin Fairbairns.
I cc it to the LaTeX-L list because although it is = fairly minor, it does
involves certain fundamental issues such as backward = compatibility and who
maintains older packages.

Dear Robin,

In making preparations for the 4th edition of A Guide = to LaTeX, I looked into
the parskip.sty package from the TeXLive 7 CD, really = just to check its date.
There I noticed that you have updated it, adding an = option parfill, and
fixing up the double spaced table of contents. I = always had my own way of
getting around that, when I wanted to get around = it.

Shortly after, I was working on a 500 page document = (out Institute Yearbook),
made some minor corrections, and then noticed that = the entire document was 2
pages shorter than it was before. Horrified, I = discovered it was the table of
contents that was now shorter, single instead of = double spaced. It then
clicked that parskip.sty had been altered, and I was = processing the document
now on my laptop, the only computer around with the = revised parskip.

Had I not coincidentally seen the change in parskip = shortly before this, I
would have been extremely puzzled. (I guess I would = have discovered the cause
fairly quickly.) But this should not happen. Your = change to parskip is
welcomed, but it should not be so that older = documents are processed
differently than before. I would call the = double-spaced table of contents a
feature, not a bug. It is not necessarily a bad = thing, although one may not
want it all the time. And many people may have got = used to it, and even
expect it.

I would prefer to see your fix-up as an option, say = notoc, so that the
default behaviour is the double-spaced listings, as = it has been for the last
13 years. Then one must actively select = single-spacing with this option,
avoiding unexpected surprises.

I am not sure who is now maintaining parskip.sty = officially, but since you
made the last change, I guess it is your court = now.

Regards, Patrick


----------------------------------------------------------------= -------------
   Dr. Patrick W. = Daly           &nb= sp;        Tel. [+49] = 5556-979-279
   Max-Planck-Institut fuer = Aeronomie     Fax. [+49] 5556-979-240
   Max-Planck-Str. = 2            =           Mob. [+49] = 175-162-1811
   D-37191 = Katlenburg-Lindau         &n= bsp;    Email: daly@linmpi.mpg.de
   Germany
----------------------------------------------------------------= -------------

------_=_NextPart_001_01C2B563.C584CE00--