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 f1NGI4r07738 for ; Fri, 23 Feb 2001 17:18:04 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1NGI3s12820 . for ; Fri, 23 Feb 2001 17:18:03 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09DB4.32E64600" 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 f1NGH3H02650 for ; Fri, 23 Feb 2001 17:17:03 +0100 (MET) 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 RAA27798 for ; Fri, 23 Feb 2001 17:17:02 +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 mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1NGH2Q16102 for ; Fri, 23 Feb 2001 17:17:02 +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 <4.DFF3F421@mail.listserv.gmd.de>; Fri, 23 Feb 2001 17:16:51 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 493472 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 23 Feb 2001 17:16:58 +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 RAA20347 for ; Fri, 23 Feb 2001 17:16:56 +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 RAA50916 for ; Fri, 23 Feb 2001 17:16:48 +0100 Received: from ams.org (sun06.ams.org [130.44.1.6]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1NGGkh09665 for ; Fri, 23 Feb 2001 17:16:46 +0100 (MET) Received: from localhost (bnb@localhost) by ams.org (8.11.2/8.11.2) with ESMTP id f1NGGga12716 for ; Fri, 23 Feb 2001 11:16:43 -0500 (EST) In-Reply-To: Return-Path: Content-class: urn:content-classes:message Subject: Re: LaTeX's internal char prepresentation (UTF8 or Unicode?) Date: Fri, 23 Feb 2001 17:16:42 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Barbara Beeton" 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: 4008 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09DB4.32E64600 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable from lars hellstr=F6m re greek in math: Allowing greek letters does however raise some interesting problems. = Many of the greek letters have var-forms in the current math fonts, so = which form should the input letter select? E.g. \epsilon and \varepsilon = are hardly distinct enough to count as different letters/symbols, they = are merely different glyphs, so which one should it be? I for one much = prefer \varepsilon, so I would like to have some interface which lets the = user select this. in fact all the variant greek letters (that i am familiar with) *do* have distinct unicodes. the problem of how they'll actually be used still remains. i'd also like to point out that there text strings can legitimately be embedded in math expressions, and math can be embedded in those text strings ... (i don't think i've seen any deeper nesting in the wild, but such could be invented), so the transitions do have to be taken into account. -- bb ------_=_NextPart_001_01C09DB4.32E64600 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LaTeX's internal char prepresentation (UTF8 or = Unicode?)

from lars hellstr=F6m re greek in math:

    Allowing greek letters does however = raise some interesting problems. Many
    of the greek letters have = var-forms in the current math fonts, so which
    form should the input letter = select? E.g. \epsilon and \varepsilon are
    hardly distinct enough to count as = different letters/symbols, they are
    merely different glyphs, so which = one should it be? I for one much prefer
    \varepsilon, so I would like to = have some interface which lets the user
    select this.

in fact all the variant greek letters (that i am = familiar with)
*do* have distinct unicodes.  the problem of how = they'll actually
be used still remains.

i'd also like to point out that there text strings can = legitimately
be embedded in math expressions, and math can be = embedded in those
text strings ... (i don't think i've seen any deeper = nesting in the
wild, but such could be invented), so the transitions = do have to
be taken into account.
          &nbs= p;            = ;            =             &= nbsp;        -- bb

------_=_NextPart_001_01C09DB4.32E64600--