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 f4LAuWf25815 for ; Mon, 21 May 2001 12:56:32 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f4LAuV727421 . for ; Mon, 21 May 2001 12:56:31 +0200 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f4LAuV022410 for ; Mon, 21 May 2001 12:56:31 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0E1E4.B1E8F000" Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id MAA05925 for ; Mon, 21 May 2001 12:56:30 +0200 (MEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f4LAuU022404 for ; Mon, 21 May 2001 12:56:30 +0200 (MET DST) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <12.AA2D4B8F@mail.listserv.gmd.de>; Mon, 21 May 2001 12:54:41 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 496420 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 21 May 2001 12:56:27 +0200 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 MAA09276 for ; Mon, 21 May 2001 12:56:25 +0200 (MET DST) 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 MAA19778 for ; Mon, 21 May 2001 12:56:25 +0200 Received: from abel.math.umu.se (abel.math.umu.se [130.239.20.139]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f4LAuOj07723 for ; Mon, 21 May 2001 12:56:24 +0200 (MET DST) Received: from [130.239.20.144] (mac144.math.umu.se [130.239.20.144]) by abel.math.umu.se (8.9.2/8.9.2) with ESMTP id MAA00750 for ; Mon, 21 May 2001 12:53:00 +0200 (CEST) In-Reply-To: References: <15111.36254.279748.954703@hoelderlin.localdomain> <200105161742.MAA02503@riemann.math.twsu.edu> Return-Path: X-Sender: lars@abel.math.umu.se x-mime-autoconverted: from quoted-printable to 8bit by relay.urz.uni-heidelberg.de id MAA09277 Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary 2.2 Date: Mon, 21 May 2001 11:56:25 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: =?iso-8859-1?Q?Lars_Hellstr=F6m?= 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: 4096 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0E1E4.B1E8F000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 11.54 +0200 2001-05-21, Hans Aberg wrote: >So the best one could hope for, I think, is to build a layer above = those >glyphs, say an empty set command that can expand to \emptyset or >\varnothing, a set membership command that can expand to either of \in = or >the two epsilon variations, but there can be no restrictions on the = glyphs >themselves in the sense that the use of one of them prohibits the = other. My suggestion is rather that the current set of math symbol commands = should be made into this layer (hence some commands which now produce different results would then by default produce identical results). It should = still be possible to access to any glyph available in the fonts, but the = author who wishes to do so must be prepared to first define a new command for accessing the glyph via some mixed-case command (cf. how one uses \DeclareTextSymbol for text today). There could also be a compability package which makes all commands that produce distinct results today continue to do this. Finally, for the more common task of selecting = which glyphic variant of a character to use, there should be a simpler = interface than giving an explicit code point, perhaps something like \chooseglyph{\leq}{slanted} to make \leq produce what \leqslant does today. (If that glyph is not available, a warning like Warning: Glyph variant `slanted' of command \leq not defined. Using `std' variant instead. should be issued. \leqq and \eqslantless could also be considered glyph variants of \leq, unless they actually have distinct meanings = somewhere.) Lars Hellstr=F6m ------_=_NextPart_001_01C0E1E4.B1E8F000 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary 2.2

At 11.54 +0200 2001-05-21, Hans Aberg wrote:
>So the best one could hope for, I think, is to = build a layer above those
>glyphs, say an empty set command that can expand = to \emptyset or
>\varnothing, a set membership command that can = expand to either of \in or
>the two epsilon variations, but there can be no = restrictions on the glyphs
>themselves in the sense that the use of one of = them prohibits the other.

My suggestion is rather that the current set of math = symbol commands should
be made into this layer (hence some commands which = now produce different
results would then by default produce identical = results). It should still
be possible to access to any glyph available in the = fonts, but the author
who wishes to do so must be prepared to first define = a new command for
accessing the glyph via some mixed-case command (cf. = how one uses
\DeclareTextSymbol for text today). There could also = be a compability
package which makes all commands that produce = distinct results today
continue to do this. Finally, for the more common = task of selecting which
glyphic variant of a character to use, there should = be a simpler interface
than giving an explicit code point, perhaps something = like

  \chooseglyph{\leq}{slanted}

to make \leq produce what \leqslant does today. (If = that glyph is not
available, a warning like

  Warning: Glyph variant `slanted' of command = \leq not defined.
           = Using `std' variant instead.

should be issued. \leqq and \eqslantless could also be = considered glyph
variants of \leq, unless they actually have distinct = meanings somewhere.)

Lars Hellstr=F6m

------_=_NextPart_001_01C0E1E4.B1E8F000--