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 f4HK5pf09741 for ; Thu, 17 May 2001 22:05:51 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f4HK5o708623 . for ; Thu, 17 May 2001 22:05:50 +0200 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 f4HK5oU16896 for ; Thu, 17 May 2001 22:05:50 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0DF0C.C55A3980" 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 WAA13583 for ; Thu, 17 May 2001 22:05:49 +0200 (MEST) 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 f4HK5n016494 for ; Thu, 17 May 2001 22:05:49 +0200 (MET DST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <4.C16CB02B@mail.listserv.gmd.de>; Thu, 17 May 2001 22:04:06 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 496005 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 17 May 2001 22:05:46 +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 WAA04812 for ; Thu, 17 May 2001 22:05:45 +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 WAA51232 for ; Thu, 17 May 2001 22:05:45 +0200 Received: from knatte.tninet.se (knatte.tninet.se [195.100.94.10]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f4HK5eP09120 for ; Thu, 17 May 2001 22:05:44 +0200 (MET DST) Received: (qmail 17167 invoked from network); 17 May 2001 22:05:40 +0200 Received: from delenn.tninet.se (HELO algonet.se) (195.100.94.104) by knatte.tninet.se with SMTP; 17 May 2001 22:05:40 +0200 Received: from [195.100.226.144] (du132-226.ppp.su-anst.tninet.se [195.100.226.132]) by delenn.tninet.se (BLUETAIL Mail Robustifier 2.2.2) with ESMTP id 626362.129938.990delenn-s0 for ; Thu, 17 May 2001 22:05:38 +0200 In-Reply-To: References: Return-Path: X-Sender: haberg@pop.matematik.su.se Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary 2.2 Date: Thu, 17 May 2001 20:56:41 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Hans Aberg" 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: 4081 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0DF0C.C55A3980 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 21:21 +0300 2001/05/17, Apostolos Syropoulos wrote: >> Here are two examples: >> $\epsilon\varepsilon R$ >> $\varepsilon R$ ... >I believe your example is incorrect. The right way to write the first >formula should be: >$\varepsilon \epsilon R$. No, the second formula. :-) -- The correct version was zipped out by the spell-checker I used. The thing though is that both types of epsilon have in the past been = used to indicate set membership. In principle frequent epsilon users in say analysis could have used the other epsilon to denote a small quantity. = But whether they actually did depends on whether they made use of set = notation and whether the epsilon's were both available by the typesetter: If some sign wasn't available, one would have to substitute another. Another example: TeX has undotted \imath and \jmath with the idea that = they should be used when putting math diacritical marks on top of them. But = once those symbols are there, it is possible for mathematicians to use say \jmath and $j$ side by side. If I should conjure up an example, it is common to let a dot denote the derivative of a path. Then, in order to avoid confusion, one could define a path $\jmath(t)$ with derivative $j(t)$. So then one cannot require these different versions to be semantically equivalent anymore. So this evolution of characters and their use in math make it difficult = to put restrictions on their usage. Hans Aberg ------_=_NextPart_001_01C0DF0C.C55A3980 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary 2.2

At 21:21 +0300 2001/05/17, Apostolos Syropoulos = wrote:
>> Here are two examples:
>>   $\epsilon\varepsilon R$
>>   $\varepsilon R$
...
>I believe your example is incorrect. The right = way to write the first
>formula should be:
>$\varepsilon \epsilon R$.

No, the second formula. :-) -- The correct version was = zipped out by the
spell-checker I used.

The thing though is that both types of epsilon have in = the past been used
to indicate set membership. In principle frequent = epsilon users in say
analysis could have used the other epsilon to denote = a small quantity. But
whether they actually did depends on whether they = made use of set notation
and whether the epsilon's were both available by the = typesetter: If some
sign wasn't available, one would have to substitute = another.

Another example: TeX has undotted \imath and \jmath = with the idea that they
should be used when putting math diacritical marks on = top of them. But once
those symbols are there, it is possible for = mathematicians to use say
\jmath and $j$ side by side. If I should conjure up = an example, it is
common to let a dot denote the derivative of a path. = Then, in order to
avoid confusion, one could define a path $\jmath(t)$ = with derivative
$j(t)$. So then one cannot require these different = versions to be
semantically equivalent anymore.

So this evolution of characters and their use in math = make it difficult to
put restrictions on their usage.

  Hans Aberg

------_=_NextPart_001_01C0DF0C.C55A3980--