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 f1C0L2H13149 for ; Mon, 12 Feb 2001 01:21:02 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1C0L2d27109 . for ; Mon, 12 Feb 2001 01:21:02 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09489.AE2D2B00" 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 f1C0L1M23045 for ; Mon, 12 Feb 2001 01:21:01 +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 BAA21073 for ; Mon, 12 Feb 2001 01:21:00 +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 f1C0KxM23037 for ; Mon, 12 Feb 2001 01:20:59 +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 <1.80E88305@mail.listserv.gmd.de>; Mon, 12 Feb 2001 1:20:52 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 487449 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 12 Feb 2001 01:20:56 +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 BAA29161 for ; Mon, 12 Feb 2001 01:20:55 +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 BAA21232 for ; Mon, 12 Feb 2001 01:20:55 +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 f1C0Ksu02667 for ; Mon, 12 Feb 2001 01:20:54 +0100 (MET) Received: from localhost (bnb@localhost) by ams.org (8.11.1/8.11.1) with ESMTP id f1C0KnZ18953 for ; Sun, 11 Feb 2001 19:20:50 -0500 (EST) In-Reply-To: Return-Path: Content-class: urn:content-classes:message Subject: Re: LaTeX's internal char prepresentation (UTF8 or Unicode?) Date: Mon, 12 Feb 2001 01:20:49 +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: 3835 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09489.AE2D2B00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable a small update on unicode and math symbols; roozbeh says There are also ones that will most probably never get into Unicode, = like the dotless j. [...] Unicode recommends modifiers for the unified math symbols, which = will become something like \mathmakelonger{\rightarrow} internally. this is still an active area. there has been a strong counterproposal to explicitly encode the long arrows, based on the fact that they are given distinct entity names in the sgml public entity set isoamsa, and the concept of "disunification" has some strong support. the defining proposal will be distributed in a week or two to the utc for a letter ballot; i can't predict whether it will or won't be accepted, but i can say with assurance that the matter isn't yet settled, and if the decision ends up to use a modifier, it won't be a *unicode* modifier, but one defined in mathml. -- bb ------_=_NextPart_001_01C09489.AE2D2B00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LaTeX's internal char prepresentation (UTF8 or = Unicode?)

a small update on unicode and math symbols;

roozbeh says

    There are also ones that will most = probably never get into Unicode, like
    the dotless j.

    [...]

    Unicode recommends modifiers for = the unified math symbols, which will
    become something like = \mathmakelonger{\rightarrow} internally.

this is still an active area.  there has been a = strong counterproposal
to explicitly encode the long arrows, based on the = fact that they are
given distinct entity names in the sgml public entity = set isoamsa,
and the concept of "disunification" has = some strong support.  the
defining proposal will be distributed in a week or = two to the utc
for a letter ballot; i can't predict whether it will = or won't be
accepted, but i can say with assurance that the = matter isn't yet
settled, and if the decision ends up to use a = modifier, it won't
be a *unicode* modifier, but one defined in = mathml.
          &nbs= p;            = ;            =             &= nbsp;        -- bb

------_=_NextPart_001_01C09489.AE2D2B00--