Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 20 Jan 2003 17:41:56 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h0KGfs6C000563 for ; Mon, 20 Jan 2003 17:41:55 +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 h0KGNNZr029843; Mon, 20 Jan 2003 17:23:23 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2C0A2.D7F22200" 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 h0K3Js2P000694; Mon, 20 Jan 2003 17:16:01 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 7315 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 20 Jan 2003 17:16:01 +0100 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.2/8.12.2/SuSE Linux 0.6) with ESMTP id h0KGG15f007984 for ; Mon, 20 Jan 2003 17:16:01 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h0KGN2Zr029752 for ; Mon, 20 Jan 2003 17:23:03 +0100 (MET) Received: from [212.227.126.160] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 18aehT-0001gL-00 for LATEX-L@listserv.uni-heidelberg.de; Mon, 20 Jan 2003 17:23:03 +0100 Received: from [80.129.5.232] (helo=istrati.mittelbach-online.de) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 18aehM-0001Vz-00 for LATEX-L@listserv.uni-heidelberg.de; Mon, 20 Jan 2003 17:23:03 +0100 Received: (from frank@localhost) by istrati.mittelbach-online.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id h0KGKCk24412; Mon, 20 Jan 2003 17:20:12 +0100 In-Reply-To: References: <15915.60496.798501.907773@lin2.idris.fr> <15915.64379.146524.772099@istrati.mittelbach-online.de> Return-Path: X-Mailer: VM 6.96 under Emacs 20.7.1 X-OriginalArrivalTime: 20 Jan 2003 16:41:56.0686 (UTC) FILETIME=[D85ACEE0:01C2C0A2] x-mime-autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id h0KGG15f007985 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: LICR objects in math Date: Mon, 20 Jan 2003 17:20:11 +0100 Message-ID: A<15916.8635.946195.989212@istrati.mittelbach-online.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: LICR objects in math Thread-Index: AcLAoth2nE6Q+mZQSGuTIbXIax3VXw== From: "Frank Mittelbach" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4450 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2C0A2.D7F22200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > > glad to learn that; can you perhaps tell us how you resolved the > > problem of either killing ligatures and kerns or alternatively > > making the wrong choice at the begining of an \halign cell that > > afterwards (!) jumps into math mode? > > One limited possibility would be > \mathcode`\=E4=3D"8000 yes, that is the sort of only out one would have, but as far as we could = see it isn't going to allow a resolution. point is a) this doesn't help for LICR objects like \" as they potentially = execute \accent and that bombs in math b) and even if \"a expands to a \chardef then the chardef number = depends on the outer fontencoding so might vary from case to case c) and of course that would mean that inputenc mapping would be called = upon so to make that sfe you would need to swap inputenc encoding in and out = ... > If the letter then ended up being typeset in math mode instead of = text > mode, it would get reevaluated. Unfortunately, this particular trick > would require that input encoding and font encoding match... exactly, which bring us back to square one: Don's big mistake of not separating the two in the first place so i doubt that this is helping frank ------_=_NextPart_001_01C2C0A2.D7F22200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LICR objects in math

 > > glad to learn that; can you perhaps = tell us how you resolved the
 > > problem of either killing ligatures = and kerns or alternatively
 > > making the wrong choice at the = begining of an \halign cell that
 > > afterwards (!) jumps into math = mode?
 >
 > One limited possibility would be
 > \mathcode`\=E4=3D"8000

yes, that is the sort of only out one would have, but = as far as we could see
it isn't going to allow a resolution.

point is

 a) this doesn't help for LICR objects like = \" as they potentially execute
 \accent and that bombs in math

 b) and even if \"a expands to a \chardef = then the chardef number depends on
 the outer fontencoding so might vary from case = to case

 c) and of course that would mean that inputenc = mapping would be called upon
 so to make that sfe you would need to swap = inputenc encoding in and out ...

 > If the letter then ended up being typeset = in math mode instead of text
 > mode, it would get reevaluated.  = Unfortunately, this particular trick
 > would require that input encoding and font = encoding match...

exactly, which bring us back to square one: Don's big = mistake of not
separating the two in the first place

so i doubt that this is helping
frank

------_=_NextPart_001_01C2C0A2.D7F22200--