Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 3 Mar 2003 16:07:49 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h23F7k6C012258 for ; Mon, 3 Mar 2003 16:07:47 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h23EpBtt011457; Mon, 3 Mar 2003 15:51:11 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2E196.A76BD080" 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 h22N02FK028997; Mon, 3 Mar 2003 15:42:15 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 8842 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 3 Mar 2003 15:42:15 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 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 h23EgF2k007516 for ; Mon, 3 Mar 2003 15:42:15 +0100 Received: from nic.lth.se (nic.lth.se [130.235.20.3]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h23Ep8tt011437 for ; Mon, 3 Mar 2003 15:51:09 +0100 (MET) Received: from [130.235.3.161] (mathcent81.maths.lth.se [130.235.3.161]) by nic.lth.se (8.12.3/8.12.3) with ESMTP id h23Ep6Hq029675 for ; Mon, 3 Mar 2003 15:51:07 +0100 (MET) In-Reply-To: <000e01c2e18d$6a5f6430$657ba8c0@DOMINUS> References: <630BE70C8320D6118D240002A589ABB204A95102@DERUM201> Return-Path: X-OriginalArrivalTime: 03 Mar 2003 15:07:49.0418 (UTC) FILETIME=[A7AB98A0:01C2E196] X-Sender: lars@abel.math.umu.se x-mime-autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id h23EgF2k007517 X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -0.5 () IN_REP_TO,REFERENCES,SPAM_PHRASE_00_01 Content-class: urn:content-classes:message Subject: Re: Problem with baseline grid and multicol Date: Mon, 3 Mar 2003 15:51:38 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Problem with baseline grid and multicol Thread-Index: AcLhlqfKdoGoKJyNRXmumWg3rWzXDA== From: =?iso-8859-1?Q?Lars_Hellstr=F6m?= To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4562 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2E196.A76BD080 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 15.01 +0100 2003-03-03, Ulrich Dirr wrote: >And curiously in the resulting output the next line of text is offset = by >~0.4mm. When putting some \vspace command before the next line of text >to compensate for this -- which is not what I want because I then have >to do this very often and by hand -- I got the irritating behavior that >this text line "oscillates" above and below the baseline when I'm >changing the amount of vspace only a bit ... This needs not be related, but it sometimes leads to similar problems, = and I haven't seen an explanation anywhere: why is \addvspace discontinuous? = If SKIP < \lastskip < 0 then the net effect of \addvspace{SKIP} is to do nothing, but if SKIP < 0 <=3D \lastskip then the net effect of \addvspace{SKIP} is that SKIP is added to the current vertical list (thus moving everything up). Lars Hellstr=F6m ------_=_NextPart_001_01C2E196.A76BD080 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Problem with baseline grid and multicol

At 15.01 +0100 2003-03-03, Ulrich Dirr wrote:
>And curiously in the resulting output the next = line of text is offset by
>~0.4mm. When putting some \vspace command before = the next line of text
>to compensate for this -- which is not what I = want because I then have
>to do this very often and by hand -- I got the = irritating behavior that
>this text line "oscillates" above and = below the baseline when I'm
>changing the amount of vspace only a bit = ...

This needs not be related, but it sometimes leads to = similar problems, and
I haven't seen an explanation anywhere: why is = \addvspace discontinuous? If
  SKIP < \lastskip < 0
then the net effect of \addvspace{SKIP} is to do = nothing, but if
  SKIP < 0 <=3D \lastskip
then the net effect of \addvspace{SKIP} is that SKIP = is added to the
current vertical list (thus moving everything = up).

Lars Hellstr=F6m

------_=_NextPart_001_01C2E196.A76BD080--