Received: by nummer-3.proteosys id <01C19443.4561798C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:41:59 +0100 In-Reply-To: /G=N/S=POPPELIER/@ELSEVIER.SURF.400net.nl's message of 20 Aug 91 15:33:49+0200 <"DFNGATE:Nd8iBADc"*@x400-gate> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.4561798C" 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: blind spot, or: why @listI and not @listi? Date: Tue, 20 Aug 1991 15:43:07 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Rainer Schoepf" To: Cc: Status: R X-Status: X-Keywords: X-UID: 366 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.4561798C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Nico, two things come to my mind: First of all, \@normalsize contains \let\@listi\@listI. Probably that's why your second example fails. Second, the reason for the introduction of \@listI was the following: Before that change was made, After=20 \small text \normalsize the first-level list parameters had still the values for type size \small.=20 Rainer ------_=_NextPart_001_01C19443.4561798C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable blind spot, or: why @listI and not @listi?

Nico,

two things come to my mind:

First of all, \@normalsize contains = \let\@listi\@listI. Probably
that's why your second example fails.

Second, the reason for the introduction of \@listI was = the following:
Before that change was made, After

\small

text

\normalsize

the first-level list parameters had still the values = for type size
\small.

Rainer

------_=_NextPart_001_01C19443.4561798C--