Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.6713); Tue, 6 Jul 2004 10:28:41 +0200 Received: by mail.proteosys.com (8.12.10/8.12.2) with ESMTP id i668SZUO006275 for ; Tue, 6 Jul 2004 10:28:36 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.119.176]) by relay.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id i668JIIY018711; Tue, 6 Jul 2004 10:19:19 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C46333.3E204280" 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 i65E1xCs004682; Tue, 6 Jul 2004 10:17:28 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8e) with spool id 367194 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 6 Jul 2004 10:17:23 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 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 i668HMh6024174 for ; Tue, 6 Jul 2004 10:17:23 +0200 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by relay.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id i668J7IY018660 for ; Tue, 6 Jul 2004 10:19:07 +0200 (MET DST) Received: from [212.227.126.162] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BhlAQ-00056E-00 for LATEX-L@listserv.uni-heidelberg.de; Tue, 06 Jul 2004 10:19:06 +0200 Received: from [80.129.1.205] (helo=istrati.mittelbach-online.de) by mrelayng.kundenserver.de with asmtp (TLSv1:EDH-RSA-DES-CBC3-SHA:168) (Exim 3.35 #1) id 1BhlAQ-0001gJ-00 for LATEX-L@listserv.uni-heidelberg.de; Tue, 06 Jul 2004 10:19:06 +0200 Received: (from frank@localhost) by istrati.mittelbach-online.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id i668I8g13814; Tue, 6 Jul 2004 10:18:08 +0200 In-Reply-To: <20040706.001646.155827066.wl@gnu.org> References: <20040705.073134.197330345.wl@gnu.org> <20040705133005.GA3295@m0A02325D.vpn.uni-freiburg.de> <20040706.001646.155827066.wl@gnu.org> Return-Path: X-Mailer: VM 6.96 under Emacs 20.7.1 X-OriginalArrivalTime: 06 Jul 2004 08:28:41.0538 (UTC) FILETIME=[3E725A20:01C46333] X-Authentication-Warning: istrati.mittelbach-online.de: frank set sender to frank@mittelbach-online.de using -f X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:923c546e49b26a7485eda6910e23f403 X-ProteoSys-SPAM-Score: 0.2 () RCVD_IN_NJABL,RCVD_IN_SORBS Content-class: urn:content-classes:message Subject: Re: accents and inputenc Date: Tue, 6 Jul 2004 09:18:08 +0100 Message-ID: A<16618.24640.441027.21210@istrati.mittelbach-online.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: accents and inputenc Thread-Index: AcRjMz6JCwFmdQ4uRO2G+bQkq3Yheg== From: "Frank Mittelbach" Sender: "Mailing list for the LaTeX3 project" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4800 This is a multi-part message in MIME format. ------_=_NextPart_001_01C46333.3E204280 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Werner LEMBERG writes: > > Package inputenc translates the input characters that it controls > > into TeX code: ^^b9 becomes: > > \show^^b9 > > ->\IeC {\i } > > Actually 4 tokens instead of one ^^b9 token. > > It is fairly easy to catch this case while the accent macro is = looking > for its argument -- I just wonder why it is missing... yes and no. it is "fairly" easy and it is also "fairly" dangerous in the = sense that it is likely to upset other parts of the process. don't = underestimate the kind of dependencies if you have to support all kind of extension = packages and not just those from a single user. more importantly it wasn't ever needed in real life except for something = like \i (which wasn't at the for-front of inputenc chars as it was not = generated with the first keyboard layouts). an even more important consideration is (or rather was) that it makes = the accent commands more complicated and slower. these days speed is less an issue so it should perhaps be looked at = again. as far as documentation is concerned i thought that it is mentioned = somewhere that the accents need braces if input enc characters are placed into = accent commands but i may be wrong. frank ------_=_NextPart_001_01C46333.3E204280 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: accents and inputenc

Werner LEMBERG writes:
 > > Package inputenc translates the input = characters that it controls
 > > into TeX code: ^^b9 becomes:
 > >   \show^^b9
 > >   ->\IeC {\i }
 > > Actually 4 tokens instead of one ^^b9 = token.
 >
 > It is fairly easy to catch this case while = the accent macro is looking
 > for its argument -- I just wonder why it = is missing...

yes and no. it is "fairly" easy and it is = also "fairly" dangerous in the sense
that it is likely to upset other parts of the = process. don't underestimate the
kind of dependencies if you have to support all kind = of extension packages and
not just those from a single user.

more importantly it wasn't ever needed in real life = except for something like
\i (which wasn't at the for-front of inputenc chars = as it was not generated
with the first keyboard layouts).

an even more important consideration is (or rather = was) that it makes the
accent commands more complicated and slower.

these days speed is less an issue so it should perhaps = be looked at again.

as far as documentation is concerned i thought that it = is mentioned somewhere
that the accents need braces if input enc characters = are placed into accent
commands but i may be wrong.

frank

------_=_NextPart_001_01C46333.3E204280--