Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.6713); Wed, 18 Aug 2004 16:52:48 +0200 Received: by mail.proteosys.com (8.12.10/8.12.2) with ESMTP id i7IEqiKE024656 for ; Wed, 18 Aug 2004 16:52:47 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.119.176]) by relay2.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id i7IEewBp013302; Wed, 18 Aug 2004 16:40:58 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C48533.06F8A000" Received: from listserv (listserv.uni-heidelberg.de [129.206.119.176]) by listserv.uni-heidelberg.de (8.12.7/8.12.7/SuSE Linux 0.6) with ESMTP id i7ICkxTt008608; Wed, 18 Aug 2004 16:38:01 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8e) with spool id 493506 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 18 Aug 2004 16:38:01 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.12.7/8.12.7/SuSE Linux 0.6) with ESMTP id i7IEc1RB008408 for ; Wed, 18 Aug 2004 16:38:01 +0200 Received: from asmtp04.eresmas.com (144-235-81-62.libre.auna.net [62.81.235.144] (may be forged)) by relay.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id i7IEeCIY022821 for ; Wed, 18 Aug 2004 16:40:13 +0200 (MET DST) Received: from [192.168.108.53] (helo=mx03.eresmas.com) by asmtp04.eresmas.com with esmtp (Exim 4.30) id 1BxRbn-0008QY-Gs for LATEX-L@listserv.uni-heidelberg.de; Wed, 18 Aug 2004 16:40:11 +0200 Received: from [80.103.248.149] (helo=PROPIETAFMI1K9) by mx03.eresmas.com with asmtp (Exim 4.30) id 1BxRbm-0000CV-BP for LATEX-L@listserv.uni-heidelberg.de; Wed, 18 Aug 2004 16:40:10 +0200 Return-Path: X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft Exchange V6.5 X-OriginalArrivalTime: 18 Aug 2004 14:52:49.0087 (UTC) FILETIME=[079E7CF0:01C48533] x-mime-autoconverted: from base64 to 8bit by listserv.uni-heidelberg.de id i7IEc1RB008409 X-Scanned-By: MIMEDefang at proteosys.com X-Spam-Score: 2.2 (++) X-ProteoSys-SPAM-Score: 0 () Content-class: urn:content-classes:message Subject: \parshape in lists Date: Wed, 18 Aug 2004 15:40:04 +0100 Message-ID: A<001f01c48531$4489f4c0$95f86750@PROPIETAFMI1K9> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: \parshape in lists Thread-Index: AcSFMwe4cnHrQ3hnRjSk/ERbHx4emQ== From: "Javier Bezos" Sender: "Mailing list for the LaTeX3 project" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4807 This is a multi-part message in MIME format. ------_=_NextPart_001_01C48533.06F8A000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, Just a little question. Apparently the only occurrence in LaTeX of \parshape is in \list and I wonder why it was preferred to other possibilities like \hangindent or \leftskip/rightskip. Any ideas? Thanks in advance for the answers. Javier ------_=_NextPart_001_01C48533.06F8A000 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable \parshape in lists

Hello,

Just a little question. Apparently the only = occurrence
in LaTeX of \parshape is in \list and I wonder = why
it was preferred to other possibilities like = \hangindent
or \leftskip/rightskip. Any ideas?

Thanks in advance for the answers.

Javier

------_=_NextPart_001_01C48533.06F8A000--