Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id s527om1u025405 for ; Mon, 2 Jun 2014 09:50:50 +0200 Received: from relay.uni-heidelberg.de ([129.206.100.212]) by mx-ha.gmx.net (mxgmx106) with ESMTPS (Nemesis) id 0LzI21-1WnR1X2c1h-014TRZ for ; Mon, 02 Jun 2014 09:50:43 +0200 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 s527lsxT027218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Jun 2014 09:47:54 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s51M13sT032090; Mon, 2 Jun 2014 09:47:54 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 11052910 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 2 Jun 2014 09:47:54 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s527lrb1019584 for ; Mon, 2 Jun 2014 09:47:53 +0200 Received: from ix.urz.uni-heidelberg.de (cyrus-portal.urz.uni-heidelberg.de [129.206.100.176]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s527lrVw009100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 2 Jun 2014 09:47:53 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s527lqVk008085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 2 Jun 2014 09:47:52 +0200 Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id s527lj34027074 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Mon, 2 Jun 2014 09:47:50 +0200 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WrMy8-0000f3-SM for LATEX-L@URZ.UNI-HEIDELBERG.DE; Mon, 02 Jun 2014 09:47:44 +0200 Received: from p50893c35.dip0.t-ipconnect.de ([80.137.60.53]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 02 Jun 2014 09:47:44 +0200 Received: from news3 by p50893c35.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 02 Jun 2014 09:47:44 +0200 X-Injected-Via-Gmane: http://gmane.org/ Lines: 50 References: <1ubs1y1le1qz6$.dlg@nililand.de> <53720D19.6020700@morningstar2.co.uk> <538B7174.7020706@gmx.de> <538B7DBB.9050304@latex-project.org> <19yi0u0y3aa8q$.dlg@nililand.de> <538B8538.7090500@latex-project.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p50893c35.dip0.t-ipconnect.de User-Agent: 40tude_Dialog/2.0.15.41de X-Spam-Check-Skipped: Loadavg 12.99 Message-ID: <1jopdbg1bnkda.dlg@nililand.de> Date: Mon, 2 Jun 2014 09:47:32 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Ulrike Fischer Subject: Re: fixltx2e fixes some float stuff To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: Envelope-To: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=V3; X-GMX-Antivirus: 0 (no virus found) X-UI-Filterresults: notjunk:1;V01:K0:tz6dA2kfwXM=:iv/tIE59BF0b8OGwvBBr9ZDuJr HJAqedyQms8D7zp7uyKU+b7TcqAaLat8Eovu7XiQpsyIvf7BYGaGrInzfU4EBKRR2pPjTUQBN T+q1tco2g6tLnkbWYpwY31UpVjtVZEaq2NmmvtUx7WMlnRjRl00FeIbSUL5Ug3zyHIHMnRikM IkNFDQp0JjcJp4eDjAbYa85sBpI0iRZy1TPoKOxFf+AVZUJEQSJZlSlIh7tFKSO/J04un9p3B E9sfqDxoIdPGefzBdCwuV3Y/eHPk9aOsKX1UIBrddADNkl2n6nZhJSYln7Bmen8EtPGkdHhhV oVcJ7Wt+1hTM58ZX4VWioKBUqW8jz2BvplnJcQvHGXRziyXdEtUz4JBT5aSvWQGjsbiAwmcbk UNZ+OOPFKF4t6B4Hml4ydrLcAtgVf+Owkobl3SC/YUOeMWV8GEriIDUtRJ8oinQaghjfXcjZG +VWBDgwBe51rP+gWAiVrBy90f/HW96kjH7mO58lpwwOl5nkkbxKEknsLQOmYIuqg+eWxabpX8 kb059nJQZ275NxL0aurLCFL/7+oESPd9v2WiUT3KZ086KOGQ1xz9DGC4Crp02yHrDQD2XIaYQ vZWSNJ4gsQaBI8BNFpzM8G/jmEsDXKTn6W0qryhVuW6Ifr5hu7I+YWSegGaBfDTH+6ivofaUO FJYgYaIKvevtc9GLtvmRupV5s2Q7o38wWNg3eMVAU2eRVa/W/wLG6LILkR7vOzm1xKorAFoxP GsnBWfiZWxf3aB5QZ0VSHfaNLLpDE1fiuQwAtBeVw/nKEB3HZ0V7XBji0ogSA31/VP9Hue4hf 7JejSENkpT0OvvAqd7gQfkkN+j99ZDKfLbxVayKwSf25l2i18X2l8VcF78NClasmMWxzPCGOm MuAozGPsbz0dvIxQKXmVExYTaFwrbclkLCosTOtd+ow2sGKd/xTz+O7xWAyQG5t1OQNr8fYvL dYZFNFMGTZR21UutSxIuRpPmaNpU8WviXzJORZMb+0rLCKSUTUQwzxaSusQVlk3rBWQHnYDT9 fd9J0raPBWxKLm/7SFuHuQI05cUSEUqKH3DvD4zzaXLmD9XAjptYWGJFd1LCueqkh7w3HvKZr 1FGBEC62WN77YnZL6hydirPS1o0ditGfQI+ZSHx64Kn57AYF25vEEFH6COcPn+Is2EFYIPr0G vwrgNgsspBpnMKoL1kaVSJXqCpRV4ey/Yxv2EzhinO4Yb2ar+jR2RNl9OYQY7vaExGsP45pCd m4Wqa6OpF+oUleEZVn42xHc87CVw6fmHoO067yU3moQDjqE7tleybn/MlIcLKRJ7BkjmHLPr2 4pq1yr21FYspyu0uq+d7i3g1MqhPkmzQpkbBRYV2fLGEIk92lYMMxSW51h5N/t8JRlJUdC2ed WcHPyLgN9sz0XfAOGQOSMcVRZwx7IPIyq5wmthDVv3nb1kNdTvi88oxrPxL4pm4/VZ2Jzm/sw 1cY093vnRXKZ6U/930+eDcnRNmpxWSDDQ924PgD2MbTa6BJyhp/bzDLV5ErEh1ZoyU1AUN2r7 92vRLe4No8YEVKrmFslG4NLJ5aSIoZkuSG0ptaWWW X-UI-Loop:V01:8ljpb4l9qZk=:SA8dcCTqxJ3hIgpGPmkEMd9OlDXO3Qb8160E8bmeX1s= Status: R X-Status: X-Keywords: X-UID: 7479 Am Sun, 1 Jun 2014 21:55:36 +0200 schrieb Frank Mittelbach: >> Arno wrote about fixltx2e and not fix-cm. > but unfortunately her recycled the old subject line and didn't give a complete example > - ok we should have read more carefully but ... :-) I had the advantage that I already knew that fixltx2e affects packages that patch floats so I could ignore all confusing parts of the question ;-). >> Imho fixltx2e should be loaded like fix-cm before documentclass to >> avoid such problems. > that is absolutely true, fixltx2e fixes the kernel so it should come > directly after the kernel as soon as possible either via \RequirePackage > (best) or directly after the document class (second best). But the documentation doesn't say so. Actually it even warns people to load another package then fix-cm before \documentclass. > Nevertheless there is no way to do any fixing without side effects if > some package hooks into the fixed code (I discussed that one around the > float placement code in ltnews) > basically packages that hook into those areas would need to check if > they run with a kernel or with a "kernel + patches" Which can be difficult if the patches are loaded after the kernel - even more if the kernel patches are delayed to \AtBeginDocument and the package wants to patch the kernel patches ... > if a package internally loads fixltx2e (which is a doubtful practice in > my opinion) Yes I too find it a bit difficult that fontspec loads fixltx2e but perhaps fontspec needs it. -- Ulrike Fischer http://www.troubleshooting-tex.de/