Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Fri, 31 Jan 2003 15:51:48 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h0VEpj6C009736 for ; Fri, 31 Jan 2003 15:51:46 +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 h0VEMstt001228; Fri, 31 Jan 2003 15:22:55 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2C938.47D09A00" 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 h0V3OfSl009148; Fri, 31 Jan 2003 15:14:58 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 7936 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 31 Jan 2003 15:14:58 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h0VEEw5f015704 for ; Fri, 31 Jan 2003 15:14:58 +0100 Received: from sina.sharif.edu (Sina.Sharif.EDU [81.31.160.35]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h0VEMQXM021825 for ; Fri, 31 Jan 2003 15:22:28 +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 h0VEMKb16009 for ; Fri, 31 Jan 2003 17:52:20 +0330 Received: from localhost (roozbeh@localhost) by bamdad.org (8.11.6/8.11.6) with ESMTP id h0VEUvL04955 for ; Fri, 31 Jan 2003 18:00:57 +0330 In-Reply-To: <15903.14792.193451.96963@istrati.mittelbach-online.de> Return-Path: X-OriginalArrivalTime: 31 Jan 2003 14:51:48.0878 (UTC) FILETIME=[485692E0:01C2C938] 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_02_03,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: Fri, 31 Jan 2003 15:30:57 +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: AcLJOEh+EX6niOoFQ2iGNvneRTPueQ== From: "Roozbeh Pournader" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4510 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2C938.47D09A00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Fri, 10 Jan 2003, Frank Mittelbach wrote: > > Adobe has assigned dotlessj to U+F6BE (LATIN SMALL LETTER DOTLESS = J), but > > that is inofficial (and thus not universal) as it resides in the = private > > use area. > > what we try is to provide a utf8 input encoding, how likely is it that = some > editor or application generates that Adobe thing? not very i would = guess (at > least not now) therefore i would not assign anything. Something that may happen: 1. A TeX document is typeset with a PS Type 1 font will have the = dotlessj somewhere. After being converted to PDF, you will have the glyph in a = PDF document. Adobe tools see a 'dotlessj' there. 2. Someone copies and pastes it from Acrobat Reader into a document = using an editor that supports Adobe private use characters. He sees a dotlessj there. 3. The output is fed back into LaTeX. > that would be wrong in my opinion. the internal LaTeX form > \textasteriskcentered is clearly a text character and U+2217 is a math > symbol. so if some application is requesting U+2217 it should get a * = in > math mode that is (probably, haven't checked the unicode page) a > relation or a binary operator. Unicode doesn't distinguish that much between text and math characters. = It says somewhere that you may use a math character as a bullet or = something. I guess the best way to implement this is if you saw the character in = text mode it is \textasteriskcentered and if you saw it in math mode it is = '*'. Anyway, what is the usage of \textasteriskcentered? I may be able to follow it up with Unicode guys and see if we need a character for that. > whether that is worth doing, I don't know. I guess as part of the = exercise we > should perhaps build an extended list of all mapping from unicode to = known > (abd used) encoding-specific commands. I'm in. roozbeh ------_=_NextPart_001_01C2C938.47D09A00 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 Fri, 10 Jan 2003, Frank Mittelbach wrote:

>  > Adobe has assigned dotlessj to U+F6BE = (LATIN SMALL LETTER DOTLESS J), but
>  > that is inofficial (and thus not = universal) as it resides in the private
>  > use area.
>
> what we try is to provide a utf8 input encoding, = how likely is it that some
> editor or application generates that Adobe = thing? not very i would guess (at
> least not now) therefore i would not assign = anything.

Something that may happen:

1. A TeX document is typeset with a PS Type 1 font = will have the dotlessj
somewhere. After being converted to PDF, you will = have the glyph in a PDF
document. Adobe tools see a 'dotlessj' there.

2. Someone copies and pastes it from Acrobat Reader = into a document using
an editor that supports Adobe private use characters. = He sees a dotlessj
there.

3. The output is fed back into LaTeX.

> that would be wrong in my opinion. the internal = LaTeX form
> \textasteriskcentered is clearly a text = character and U+2217 is a math
> symbol. so if some application is requesting = U+2217 it should get a * in
> math mode that is (probably, haven't checked the = unicode page) a
> relation or a binary operator.

Unicode doesn't distinguish that much between text and = math characters. It
says somewhere that you may use a math character as a = bullet or something.
I guess the best way to implement this is if you saw = the character in text
mode it is \textasteriskcentered and if you saw it in = math mode it is '*'.

Anyway, what is the usage of \textasteriskcentered? I = may be able to
follow it up with Unicode guys and see if we need a = character for that.

> whether that is worth doing, I don't know. I = guess as part of the exercise we
> should perhaps build an extended list of all = mapping from unicode to known
> (abd used) encoding-specific commands.

I'm in.

roozbeh

------_=_NextPart_001_01C2C938.47D09A00--