Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Sat, 8 Feb 2003 19:40:29 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h18IeR6C004809 for ; Sat, 8 Feb 2003 19:40:28 +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 h18ITOtt027191; Sat, 8 Feb 2003 19:29:24 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2CFA1.8D790C80" 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 h18A9aT6014126; Sat, 8 Feb 2003 19:21:18 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 6772 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 8 Feb 2003 19:21:18 +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 h18ILIPw017637 for ; Sat, 8 Feb 2003 19:21:18 +0100 Received: from mercury.open.ac.uk (mercury.open.ac.uk [137.108.128.150]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h18ITDtt027167 for ; Sat, 8 Feb 2003 19:29:13 +0100 (MET) Received: from fell.open.ac.uk by mercury.open.ac.uk via SMTP Local (Mailer 3.1) with ESMTP; Sat, 8 Feb 2003 18:29:10 +0000 Received: (from car2@localhost) by fell.open.ac.uk (8.9.3+Sun/8.9.1) id SAA27034; Sat, 8 Feb 2003 18:28:55 GMT In-Reply-To: References: <15941.7468.594851.92413@fell.open.ac.uk> Return-Path: X-Mailer: VM 6.76 under Emacs 20.7.1 X-OriginalArrivalTime: 08 Feb 2003 18:40:29.0960 (UTC) FILETIME=[8E0B8880:01C2CFA1] X-Authentication-Warning: fell.open.ac.uk: car2 set sender to car2@fell.open.ac.uk using -f X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -1.5 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,X_AUTH_WARNING Content-class: urn:content-classes:message Subject: Re: [LATEX3] xor: patches for use with current classes Date: Sat, 8 Feb 2003 19:28:55 +0100 Message-ID: A<15941.19559.19644.141087@fell.open.ac.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: [LATEX3] xor: patches for use with current classes Thread-Index: AcLPoY40LRKzfEYqSdmNn5mdBGu4ug== From: "Chris Rowley" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4543 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2CFA1.8D790C80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Bjoern > 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. > Yes, I agree that that seems odd. > 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". > Hmm, yes! Tricky stuff geometry. That kind of placment stuff needs a cleaner interface, probably in a seperate `module'. chris ------_=_NextPart_001_01C2CFA1.8D790C80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: [LATEX3] xor: patches for use with current = classes

Bjoern

> 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.
>

Yes, I agree that that seems odd.

> 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".
>

Hmm, yes!  Tricky stuff geometry.

That kind of placment stuff needs a cleaner interface, = probably in a
seperate `module'.


chris

------_=_NextPart_001_01C2CFA1.8D790C80--