Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Sun, 16 Feb 2003 19:48:14 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h1GImB6C029127 for ; Sun, 16 Feb 2003 19:48:12 +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 h1GIaBtt000445; Sun, 16 Feb 2003 19:36:11 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2D5EB.F5F06B00" 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 h1GCAmR3014645; Sun, 16 Feb 2003 19:26:51 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 6758 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 16 Feb 2003 19:26:51 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h1GIGpPR015871 for ; Sun, 16 Feb 2003 19:16:51 +0100 Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h1GIP6XM023387 for ; Sun, 16 Feb 2003 19:25:06 +0100 (MET) Received: from fwd00.sul.t-online.de by mailout10.sul.t-online.com with smtp id 18kTTK-0000Gb-02; Sun, 16 Feb 2003 19:25:02 +0100 Received: from localhost.localdomain (520018396234-0001@[62.226.12.189]) by fmrl00.sul.t-online.com with esmtp id 18kTSk-1ZPA6SC; Sun, 16 Feb 2003 19:24:26 +0100 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.7/8.12.5) with ESMTP id h1GIOPKr023774 for ; Sun, 16 Feb 2003 19:24:26 +0100 Received: (from dak@localhost) by localhost.localdomain (8.12.7/8.12.5/Submit) id h1GIOOPg023770; Sun, 16 Feb 2003 19:24:25 +0100 In-Reply-To: Lines: 32 References: Return-Path: X-OriginalArrivalTime: 16 Feb 2003 18:48:14.0174 (UTC) FILETIME=[F60AF7E0:01C2D5EB] X-Sender: 520018396234-0001@t-dialin.net User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -3.1 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,USER_AGENT,USER_AGENT_GNUS_UA Content-class: urn:content-classes:message Subject: Re: [LATEX3] xor: patches for use with current classes Date: Sun, 16 Feb 2003 19:24:24 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: [LATEX3] xor: patches for use with current classes Thread-Index: AcLV6/YpDpLOZONCSCylfp6RHLLHEQ== From: "David Kastrup" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4544 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2D5EB.F5F06B00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Bjoern Pedersen writes: > On Sat, 8 Feb 2003, Chris Rowley wrote: > > > > > Here's a fix for xo-new.dtx, but I am still not sure wether the = fixing > > > is done in the right place at all. > > > > Well one good test is: does it look tight now? > > Yes, it looks right. But what is making me think is, that the original > calculations seem right. It appears, that the floatbox-origin is = shifted > somewhere. So maybe it is really something in the float-setup or > float-boxing that is wrong, and my fix is just a work-around. > Especially, as the offset seems to depend on the spancnt of the float, > something that is not used in this part of xo-new. > > I still have some trouble tracing the float-placement, so I have not = found > anything there, that looks wrong. So that's what I meant with "the = right > place". It's not easy to find out just what packages are supposed to be provided for what, and which are superseded (like stuff in xo-new supposedly replacing xo-final). Hard to say what to fix where if one does not even know what is supposed to be loaded! Any chance for improving pointers on that? Just so that others might be able to know just what is worth working on and what is really dead beef? -- David Kastrup, Kriemhildstr. 15, 44793 Bochum ------_=_NextPart_001_01C2D5EB.F5F06B00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: [LATEX3] xor: patches for use with current = classes

        Bjoern = Pedersen <Bjoern.Pedersen@FRM2.TUM.DE> writes:

> On Sat, 8 Feb 2003, Chris Rowley wrote:
>
>
> > > Here's  a fix for xo-new.dtx, but = I am still not sure wether the fixing
> > > is done in the right place at = all.
> >
> > Well one good test is: does it look tight = now?
>
> Yes, it looks right. But what is making me think = is, that the original
> calculations seem right. It appears, that the = floatbox-origin is shifted
> somewhere. So maybe it is really something in = the float-setup or
> float-boxing that is wrong, and my fix is just a = work-around.
> Especially, as the offset seems to depend on the = spancnt of the float,
> something that is not used in this part of = xo-new.
>
> I still have some trouble tracing the = float-placement, so I have not found
> anything there, that looks wrong. So that's what = I meant with "the right
> place".

It's not easy to find out just what packages are = supposed to be
provided for what, and which are superseded (like = stuff in xo-new
supposedly replacing xo-final).  Hard to say = what to fix where if one
does not even know what is supposed to be = loaded!

Any chance for improving pointers on that?  Just = so that others might
be able to know just what is worth working on and = what is really dead
beef?

--
David Kastrup, Kriemhildstr. 15, 44793 Bochum

------_=_NextPart_001_01C2D5EB.F5F06B00--