Received: by nummer-3.proteosys id <01C19443.42DFA1AC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:41:54 +0100 In-Reply-To: Don Hosek's message of Sat, 1 Jun 91 15:00:00 PDT MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.42DFA1AC" Organization: Konrad-Zuse-Zentrum fuer Informationstechnik Berlin X-MimeOLE: Produced By Microsoft Exchange V6.5 Return-Path: x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) Content-class: urn:content-classes:message Subject: LaTeX bug/feature/gotcha Date: Mon, 3 Jun 1991 11:22:50 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Rainer Schoepf" To: Cc: Status: R X-Status: X-Keywords: X-UID: 342 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.42DFA1AC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dominik, regarding your posting to comp.text.tex about an enumerate in a float in an enumerate environment: The behaviour you quote is certainly not proper and must be changed for LaTeX 3. There are many more of this kind: think of a list environment in a footnote or endnote. During discussions we came already across this problem, but it's not something that can be solved on the fly. You can certainly make a quick fix to the problem at hand, but this will most certainly give unexpected results at another point. Rainer PS: Is the address I should use in future? ------_=_NextPart_001_01C19443.42DFA1AC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable LaTeX bug/feature/gotcha

Dominik,

regarding your posting to comp.text.tex about an = enumerate in a float
in an enumerate environment:

The behaviour you quote is certainly not proper and = must be changed
for LaTeX 3. There are many more of this kind: think = of a list
environment in a footnote or endnote.

During discussions we came already across this = problem, but it's not
something that can be solved on the fly. You can = certainly make a
quick fix to the problem at hand, but this will most = certainly give
unexpected results at another point.

Rainer

PS: Is <teexdwu@ioe.lon.ac.uk> the address I = should use in future?

------_=_NextPart_001_01C19443.42DFA1AC--