Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Sat, 1 Feb 2003 18:02:10 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h11H246C012788 for ; Sat, 1 Feb 2003 18:02:09 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h11Gnptt013747; Sat, 1 Feb 2003 17:49:51 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2CA13.A880D500" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h0VN06Cx019262; Sat, 1 Feb 2003 17:41:45 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 6947 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 1 Feb 2003 17:41:45 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h11Gfi5f023402 for ; Sat, 1 Feb 2003 17:41:44 +0100 Received: from sina.sharif.edu ([81.31.160.35]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h11GnGtt013672 for ; Sat, 1 Feb 2003 17:49:18 +0100 (MET) Received: from bamdad.org (IDENT:root@bamdad.org [81.31.160.190]) by sina.sharif.edu (8.11.6/8.11.6) with ESMTP id h11Gmub03578; Sat, 1 Feb 2003 20:18:58 +0330 Received: from localhost (roozbeh@localhost) by bamdad.org (8.11.6/8.11.6) with ESMTP id h11GvwY24190; Sat, 1 Feb 2003 20:27:58 +0330 In-Reply-To: <15931.3562.730605.294877@istrati.mittelbach-online.de> Return-Path: X-OriginalArrivalTime: 01 Feb 2003 17:02:11.0789 (UTC) FILETIME=[A991CFD0:01C2CA13] X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Authentication-Warning: gilas.bamdad.org: roozbeh owned process doing -bs X-X-Sender: roozbeh@gilas X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -3.2 () EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01,USER_AGENT_PINE,X_AUTH_WARNING Content-class: urn:content-classes:message Subject: Re: latex/3480: Support for UTF-8 missing in inputenc.sty Date: Sat, 1 Feb 2003 17:57:58 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: latex/3480: Support for UTF-8 missing in inputenc.sty Thread-Index: AcLKE6mwSlPk8ogCRYeGoHu3qZPQUg== From: "Roozbeh Pournader" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4521 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2CA13.A880D500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Sat, 1 Feb 2003, Frank Mittelbach wrote: > which "some" editor is that? Honestly, I don't know an editor supporting this intentionally, but a = sane text editor that is just using a font supplied by Adobe as the default font will just pass the code to the font and get the glyph back. It will support Adobe Private Use Area without knowing by just playing according to the Unicode rules (using Unicode codepoints internally, leaving = intact the things that it doesn't know about, ...). > that's not the way it works in TeX, is it? at the time input encoding = is > translated to LICR we are before the decision for "text" or "math". = the > naming conventions for the LICR objects are a bit dubious here as they = often > say "\text..." but that is the major goal for them, ie make the LICR = objects > work in text and with different font encodings. [...] Sorry Frank, I don't understand the LaTeX internals completely, so although I'm trying my best to understand your description, I can't suggest any good solution. > the only common usage in LaTeX (i think) is as a bullet for some = itemize level Then this *is* the Unicode character U+2217 used as a bullet... (AMS has also got something called LOW ASTERSIK encoded in Unicode 3.2, but I really don't know about the usage, as I could not find much information about it in the original proposal. But the glyph used for = that in the charts appears too lower than a math asterisk. Barbara?) roozbeh ------_=_NextPart_001_01C2CA13.A880D500 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: latex/3480: Support for UTF-8 missing in = inputenc.sty

On Sat, 1 Feb 2003, Frank Mittelbach wrote:

> which "some" editor is that?

Honestly, I don't know an editor supporting this = intentionally, but a sane
text editor that is just using a font supplied by = Adobe as the default
font will just pass the code to the font and get the = glyph back. It will
support Adobe Private Use Area without knowing by = just playing according
to the Unicode rules (using Unicode codepoints = internally, leaving intact
the things that it doesn't know about, ...).

> that's not the way it works in TeX, is it? at the = time input encoding is
> translated to LICR we are before the decision = for "text" or "math".  the
> naming conventions for the LICR objects are a = bit dubious here as they often
> say "\text..." but that is the major = goal for them, ie make the LICR objects
> work in text and with different font encodings. = [...]

Sorry Frank, I don't understand the LaTeX internals = completely, so
although I'm trying my best to understand your = description, I can't
suggest any good solution.

> the only common usage in LaTeX (i think) is as a = bullet for some itemize level

Then this *is* the Unicode character U+2217 used as a = bullet...

(AMS has also got something called LOW ASTERSIK = encoded in Unicode 3.2,
but I really don't know about the usage, as I could = not find much
information about it in the original proposal. But = the glyph used for that
in the charts appears too lower than a math asterisk. = Barbara?)

roozbeh

------_=_NextPart_001_01C2CA13.A880D500--