Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with SMTP id p06BX4n0027913 for ; Thu, 6 Jan 2011 12:33:06 +0100 Received: (qmail 12966 invoked by alias); 6 Jan 2011 11:32:59 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 06 Jan 2011 11:32:58 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx106) with SMTP; 06 Jan 2011 12:32:58 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id p06BQE7V026686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Jan 2011 12:31:15 +0100 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id p06BIQ4Y001194; Thu, 6 Jan 2011 12:19:57 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 791426 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 6 Jan 2011 12:17:23 +0100 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id p06BHNm2024852 for ; Thu, 6 Jan 2011 12:17:23 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id p06BHAl4028994 for ; Thu, 6 Jan 2011 12:17:15 +0100 Received: from morse.mittelbach-online.de (p3EE3E158.dip.t-dialin.net [62.227.225.88]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MeMRD-1PyGrl14gh-00QEtm; Thu, 06 Jan 2011 12:12:10 +0100 Received: by morse.mittelbach-online.de (Postfix, from userid 501) id 7367670F29; Thu, 6 Jan 2011 12:12:07 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19748.48031.990921.327320@morse.mittelbach-online.de> <4D24DEEC.2090803@morningstar2.co.uk> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Provags-ID: V02:K0:mtd7TXKNETj/JU5gJTIXMyUioc8FSnd4aB5T2Eq4pQI uZtpHF+NV5tPIJYP1+1Ht6Cg0I52gcEdAJZNB5EnLlnSlfYNRn 8V5tC2s3iwUj3WrYlsPBxWdCU35Y5pP+IG0n9xsRqDxouNNunA wwb+Gr9zHvSqlRIxt68i4bH9GEvKVxpF4LR3P+nArd30i8M8FH GAeQB0KRac1lph1iCNR0w== X-Spam-Whitelist-Provider: Message-ID: <19749.41863.250832.630171@morse.mittelbach-online.de> Date: Thu, 6 Jan 2011 12:12:07 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Frank Mittelbach Subject: Re: xcoffins: missing functions? To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <4D24DEEC.2090803@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=5D7Q89H36p77e5KAPs1l6v/Sb97LojnDtMgfETrECMLUO9erHzOJe+OynZRhvlGqb5A0X bbiCt2rAnnct/NAlbHMvoAL6GY+23tB3khNK7aqcuJkHrktl7heUBBMuxWDU8MR6sgnaA+ruWxex YrTyw==V1; X-Resent-By: Forwarder X-Resent-For: rainer.schoepf@gmx.net X-Resent-To: rainer@rainer-schoepf.de Status: R X-Status: X-Keywords: X-UID: 6536 Joseph Wright writes: > On 05/01/2011 18:42, Frank Mittelbach wrote: > > Joseph did a cleaner reimplementation of that recently. This new > > implementation is working very nicely and it is available from the svn for > > people who want to play with it. > > I have updated a snapshot to CTAN, as part of xpackages. You can > therefore download xpackages.tds.zip for testing [once Robin has > installed it, of course :-)]. ah, Joseph already announced this ... me too late as usual. > > Basically what xcoffins currently does is to provide a fairly natural way > > for specifying how boxes (called coffins for some reason) are to be > > aligned to each other including rotation and with Joseph's implementation > > also scaling. > > Scaling here means 'stretching the content of the box', i.e. > graphic(s/x)'s \scalebox and \resizebox. I might add that the stretching and scaling is a part that I'm least convinced off. Not that it is wrong or should be taken out, but that I doubt that this particular functionality is often needed. There are use cases for it, I guess. But in many cases a designer wouldn't want to loose control over font sizes which will be the result of such type of scaling. There is another type of scaling/sizing which stretches the inner glue of a box and which isn't implemented. Again I don't think that there are many applications for it, but I would expect equal number of use cases for this type too. So perhaps we should consider this as well. frank