Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 20 Jan 2003 13:48:17 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h0KCmE6C032050 for ; Mon, 20 Jan 2003 13:48:15 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2C082.33F87E80" Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h0KCWeAL026821; Mon, 20 Jan 2003 13:32:40 +0100 (MET) 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 h0K3JsuR000694; Mon, 20 Jan 2003 13:25:17 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 6974 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 20 Jan 2003 13:25:16 +0100 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 h0KCPG5f005976 for ; Mon, 20 Jan 2003 13:25:16 +0100 Received: from lumiere.idris.fr (lumiere.idris.fr [130.84.8.14]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h0KCWHZr024598 for ; Mon, 20 Jan 2003 13:32:17 +0100 (MET) Received: from lin2.idris.fr (root@lin2.idris.fr [130.84.4.161]) by lumiere.idris.fr (8.12.6/8.12.6) with ESMTP id h0KCWHCf339443 for ; Mon, 20 Jan 2003 13:32:17 +0100 (CET) Received: (from gaulle@localhost) by lin2.idris.fr (8.11.2/8.11.2) id h0KCWGe10685; Mon, 20 Jan 2003 13:32:16 +0100 Return-Path: X-OriginalArrivalTime: 20 Jan 2003 12:48:17.0399 (UTC) FILETIME=[34356070:01C2C082] X-Scanned-By: MIMEDefang 2.26 (www . roaringpenguin . com / mimedefang) X-Spam-Score: 0.8 () SPAM_PHRASE_00_01 Content-class: urn:content-classes:message Subject: LICR objects in math Date: Mon, 20 Jan 2003 13:32:16 +0100 Message-ID: A<15915.60496.798501.907773@lin2.idris.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: LICR objects in math Thread-Index: AcLAgjRX4xeteghyQUqJURFusSR+4Q== From: "Bernard Gaulle" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4442 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2C082.33F87E80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Frank Mittelbach introducing "inpmath": > \usepackage{inpmath} > \DeclareMathMeaning{\"}{\ddot} pleased to see that project which was already implemented... at least in French Pro along with the "keyboard" package. Since i did that for the "mltex" option, i really appreciate to have it available without it too. But.. i consider there is a little typographic pb because, in the current example, the diacritic should not be at the same place in math (italic) and in text since fonts are very different. This is in fact a basic TeX pb. Doing that, what about \c and \C? or \L and \o and such? and \oe, \OE ? The pb is a little more complicated and should often require a new definition of that macros. > i would be very much interested in comments concerning the approach = the > feasibility or anything else you find useful to discuss in this = respect, eg > > should such an implementation be incorporated (somehow not this = one), > - as a package, > - as a standard, yes, as a standard-goal. --bg ------_=_NextPart_001_01C2C082.33F87E80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable LICR objects in math

Frank Mittelbach introducing = "inpmath":
 > \usepackage{inpmath}
 > \DeclareMathMeaning{\"}{\ddot}

pleased to see that project which was already = implemented...
at least in French Pro along with the = "keyboard" package.
Since i did that for the "mltex" option, i = really appreciate
to have it available without it too.

But.. i consider there is a little typographic pb = because, in
the current example, the diacritic should not be at = the same
place in math (italic) and in text since fonts are = very different.
This is in fact a basic TeX pb.

Doing that, what about \c and \C? or \L and \o and = such?
and \oe, \OE ? The pb is a little more complicated = and
should often require a new definition of that = macros.

 > i would be very much interested in comments = concerning the approach the
 > feasibility or anything else you find = useful to discuss in this respect, eg
 >
 >  should such an implementation be = incorporated (somehow not this one),
 >     - as a = package,
 >     - as a = standard,

yes, as a standard-goal.

  --bg

------_=_NextPart_001_01C2C082.33F87E80--