Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f0VADO716944 for ; Wed, 31 Jan 2001 11:13:24 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f0VAEC731001 . for ; Wed, 31 Jan 2001 11:14:12 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C08B6E.71E6FA00" Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f0VADNM06761 for ; Wed, 31 Jan 2001 11:13:23 +0100 (MET) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id LAA05239 for ; Wed, 31 Jan 2001 11:13:23 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f0VADMM06757 for ; Wed, 31 Jan 2001 11:13:22 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <15.47C5E212@mail.listserv.gmd.de>; Wed, 31 Jan 2001 11:13:19 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 485356 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 31 Jan 2001 11:13:19 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id LAA16245 for ; Wed, 31 Jan 2001 11:13:17 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id LAA45552 for ; Wed, 31 Jan 2001 11:13:18 +0100 Received: from alpha.ntp.springer.de (alpha.ntp.springer.de [192.129.24.9]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f0VADIp12413 for ; Wed, 31 Jan 2001 11:13:18 +0100 (MET) Received: from ALPHA.NTP.SPRINGER.DE by ALPHA.NTP.SPRINGER.DE (PMDF V5.2-32 #35169) id <01JZJZKE0WG200087L@ALPHA.NTP.SPRINGER.DE> for LATEX-L@URZ.UNI-HEIDELBERG.DE; Wed, 31 Jan 2001 11:14:32 MEZ Return-Path: x-vms-to: IN%"LATEX-L@URZ.UNI-HEIDELBERG.DE" Content-class: urn:content-classes:message Subject: Re: default font encoding Date: Wed, 31 Jan 2001 11:14:32 +0100 Message-ID: <01JZJZKE0WG400087L@ALPHA.NTP.SPRINGER.DE> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "J%ORG KNAPPEN" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 3683 This is a multi-part message in MIME format. ------_=_NextPart_001_01C08B6E.71E6FA00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Frank Mittelbach schrieb: > \DeclareInputText{189}{\textonehalf} % so that gives an error if = placed in > % math > > but > > \DeclareInputMath{185}{\mathonesuperior} > > would that also make an uproar on ctt? i.e., changing the inputencs to = be text > objects by default > comments anybody? (Mr. from the grave?) Long time ago, I wrote my own inputenc files making *all* high = characters text character. The definition files (latin1jk.def, latin2jk.def, and latin3jk.def) are available from CTAN = (latex/contrib/supported/jknappen). If the standard inputenc files are changed, I strongly plea for "dual = use" characters. The standard ASCII characters with a few exceptions can be = used in text and math as well. A user expects the high character not to be = different in this respect. However, the whole setup using active characters makes such kind of = change rather difficult. --J"org Knappen ------_=_NextPart_001_01C08B6E.71E6FA00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: default font encoding

Frank Mittelbach schrieb:

> \DeclareInputText{189}{\textonehalf} % so that = gives an error if placed in
>          =             &= nbsp;           &n= bsp;  % math
>
> but
>
> \DeclareInputMath{185}{\mathonesuperior}
>
> would that also make an uproar on ctt? i.e., = changing the inputencs to be text
> objects by default

> comments anybody? (Mr. from the grave?)

Long time ago, I wrote my own inputenc files making = *all* high characters
text character. The definition files (latin1jk.def, = latin2jk.def,
and latin3jk.def) are available from CTAN = (latex/contrib/supported/jknappen).


If the standard inputenc files are changed, I strongly = plea for "dual use"
characters. The standard ASCII characters with a few = exceptions can be used
in text and math as well. A user expects the high = character not to be different
in this respect.

However, the whole setup using active characters makes = such kind of change
rather difficult.

--J"org Knappen

------_=_NextPart_001_01C08B6E.71E6FA00--