Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Wed, 8 Jan 2003 19:20:07 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h08IK46C021856 for ; Wed, 8 Jan 2003 19:20:05 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h08DVeEV026306; Wed, 8 Jan 2003 14:31:41 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2B742.924C6580" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h081CYju025022; Wed, 8 Jan 2003 14:24:52 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 5825 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 8 Jan 2003 14:24:52 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h08DOpTk029962 for ; Wed, 8 Jan 2003 14:24:51 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h08DVLwO006575 for ; Wed, 8 Jan 2003 14:31:21 +0100 (MET) Received: from [212.227.126.162] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 18WGIi-0001X8-00 for LATEX-L@listserv.uni-heidelberg.de; Wed, 08 Jan 2003 14:31:20 +0100 Received: from [80.129.2.146] (helo=istrati.mittelbach-online.de) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 18WGIi-0003K7-00 for LATEX-L@listserv.uni-heidelberg.de; Wed, 08 Jan 2003 14:31:20 +0100 Received: (from frank@localhost) by istrati.mittelbach-online.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id h08DV4G01674; Wed, 8 Jan 2003 14:31:04 +0100 In-Reply-To: References: <200212031601.gB3G11cQ009558@sun.dante.de> <15899.14827.804209.458595@istrati.mittelbach-online.de> <20030108133159790734.GyazMail.jbezos@wanadoo.es> Return-Path: X-Mailer: VM 6.96 under Emacs 20.7.1 X-OriginalArrivalTime: 08 Jan 2003 18:20:07.0669 (UTC) FILETIME=[92B27A50:01C2B742] 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-Spam-Score: -0.7 () IN_REP_TO,REFERENCES,SPAM_PHRASE_00_01,X_AUTH_WARNING Content-class: urn:content-classes:message Subject: Re: latex/3480: Support for UTF-8 missing in inputenc.sty Date: Wed, 8 Jan 2003 14:31:04 +0100 Message-ID: A<15900.10264.614534.536619@istrati.mittelbach-online.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: latex/3480: Support for UTF-8 missing in inputenc.sty Thread-Index: AcK3QpLURZwyBEC7QQmf0BeYVGT65Q== From: "Frank Mittelbach" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4415 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2B742.924C6580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable David Kastrup writes: > Javier Bezos writes: > > > > % This mapping needs to be set up only once so here it is done = at > > > % |\begin{document}| > > > > I think a better place is inputenc itself or fontenc; > > otherwise saveboxes in the preamble won't work. > > Saveboxes in the preamble are probably not a good idea, anyway, since > the font setup has not completed there. well, yes. this is an open question to us for a long time. I tend to think that one has to view the preamble as a "non-typesetting = area" otherwise you end up with all kind of complications, e.g., the font = setup not being ready, etc. assuming the reading of the utf8 declaration files happens in inputenc = only, then any later encoding declaration will not be used. if it happens in = fontenc then this situation is better as it could always then loads the Xenc.def = file and the Xenc.dfu file at that point in time. One can then of course do = the following: when inputenc is processed, read the .dfu files for all encodings known = alread (ie those on the cdp list) and set a flag to signal to fontenc to take = over from then on. that might actually be the best solution. i didn't = implemented it that way to avoid having to distribute fontenc as well right now. however, i still think that there are problems with typesetting in the preamble and while i doubt it should be completely banned it is best to = assume that normally it doesn't work or can't be relied on. frank ------_=_NextPart_001_01C2B742.924C6580 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: latex/3480: Support for UTF-8 missing in = inputenc.sty

David Kastrup writes:
 >         = Javier Bezos <jbezos@WANADOO.ES> writes:
 >
 > > > %    This mapping = needs to be set up only once so here it is done at
 > > > %    = |\begin{document}|
 > >
 > > I think a better place is inputenc = itself or fontenc;
 > > otherwise saveboxes in the preamble = won't work.
 >
 > Saveboxes in the preamble are probably not = a good idea, anyway, since
 > the font setup has not completed = there.

well, yes. this is an open question to us for a long = time.

I tend to think that one has to view the preamble as a = "non-typesetting area"
otherwise you end up with all kind of complications, = e.g., the font setup not
being ready, etc.

assuming the reading of the utf8 declaration files = happens in inputenc only,
then any later encoding declaration will not be used. = if it happens in fontenc
then this situation is better as it could always then = loads the Xenc.def file
and the Xenc.dfu file at that point in time. One can = then of course do the
following:

when inputenc is processed, read the .dfu files for = all encodings known alread
(ie those on the cdp list) and set a flag to signal = to fontenc to take over
from then on. that might actually be the best = solution. i didn't implemented it
that way to avoid having to distribute fontenc as = well right now.

however, i still think that there are problems with = typesetting in the
preamble and while i doubt it should be completely = banned it is best to assume
that normally it doesn't work or can't be relied = on.

frank

------_=_NextPart_001_01C2B742.924C6580--