Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Fri, 31 Jan 2003 18:35:45 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h0VHZg6C010185 for ; Fri, 31 Jan 2003 18:35:43 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h0VH7sXM007685; Fri, 31 Jan 2003 18:07:54 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2C94F.2F1FAE80" 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 h0V3OfWP009148; Fri, 31 Jan 2003 18:00:16 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 8182 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 31 Jan 2003 18:00:16 +0100 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 h0VH0G5f017207 for ; Fri, 31 Jan 2003 18:00:16 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail22.messagelabs.com (mail22.messagelabs.com [193.109.255.115]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with SMTP id h0VH7mXM007666 for ; Fri, 31 Jan 2003 18:07:48 +0100 (MET) Received: (qmail 6631 invoked from network); 31 Jan 2003 17:07:34 -0000 Received: from smtp-6.star.net.uk (212.125.75.75) by server-23.tower-22.messagelabs.com with SMTP; 31 Jan 2003 17:07:34 -0000 Received: (qmail 1064 invoked from network); 31 Jan 2003 17:07:38 -0000 Received: from nagmx1.nag.co.uk (HELO nag.co.uk) (62.231.145.242) by smtp-6.star.net.uk with SMTP; 31 Jan 2003 17:07:38 -0000 Received: from penguin.nag.co.uk (IDENT:root@penguin.nag.co.uk [192.156.217.14]) by nag.co.uk (8.9.3/8.9.3) with ESMTP id RAA10966 for ; Fri, 31 Jan 2003 17:07:24 GMT Received: by penguin.nag.co.uk (8.9.3) id RAA22372; Fri, 31 Jan 2003 17:07:18 GMT In-Reply-To: (message from Roozbeh Pournader on Fri, 31 Jan 2003 20:16:15 +0330) References: Return-Path: X-OriginalArrivalTime: 31 Jan 2003 17:35:45.0116 (UTC) FILETIME=[2F3161C0:01C2C94F] X-VirusChecked: Checked X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -1 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_03_05 X-Env-Sender: davidc@nag.co.uk X-Msg-Ref: server-23.tower-22.messagelabs.com!1044032854!1920 Content-class: urn:content-classes:message Subject: Re: latex/3480: Support for UTF-8 missing in inputenc.sty Date: Fri, 31 Jan 2003 18:07:18 +0100 Message-ID: A<200301311707.RAA22372@penguin.nag.co.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: latex/3480: Support for UTF-8 missing in inputenc.sty Thread-Index: AcLJTy9OBzdYHTkpRcS0ZDD4KMP5oQ== From: "David Carlisle" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4514 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2C94F.2F1FAE80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > Which is the policy? the file has a long history, and I'm not sure that policy has always been consistent.. Some things, especially the classification of characters as math or non math, have not been that systematic I fear. As you commented earlier, Unicode doesn't really make the distinction in the same way as TeX. > "Show a black box if you > can't do it exactly" or "Show something and display a warning"? Ideally I think that I'd like the latex field to consistently have a command that could be used as latex's internal encoding independent command, together with some latex packages to define any additional commands needed, so you could switch at the latex level between displaying the glyph, or faking it with TeX constructs or making a missing-glyph marker, depending on the fonts available. Suggestions welcome... If needs be, the latex-unicode support could be a new additional field if you needed some different markup or attributes to that contained in the existing field. Similar problems occur in the ISO entity support without the TeX part, It's hard to know what to map the ISO jmath entity to given there's no dotless j in Unicode (to return to a previous example) (I'd be lynched by the W3C I18N group if I mapped it to a private use character, currently I map it to j) David ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ ------_=_NextPart_001_01C2C94F.2F1FAE80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: latex/3480: Support for UTF-8 missing in = inputenc.sty

>  Which is the policy?

the file has a long history, and I'm not sure that = policy has always
been consistent.. Some things, especially the = classification of
characters as math or non math, have not been that = systematic I fear.
As you commented earlier, Unicode doesn't really make = the distinction in
the same way as TeX.

> "Show a black box if you
> can't do it exactly" or "Show = something and display a warning"?

Ideally I think that I'd like the latex field to = consistently have
a command that could be used as latex's internal = encoding independent
command, together with some latex packages to define = any additional
commands needed, so you could switch at the latex = level between
displaying the glyph, or faking it with TeX = constructs or making a
missing-glyph marker, depending on the fonts = available.

Suggestions welcome...
If needs be, the latex-unicode support could be a new = additional field
if you needed some different markup or attributes to = that contained in
the existing field.

Similar problems occur in the ISO entity support = without the TeX part,
It's hard to know what to map the ISO jmath entity to = given there's no
dotless j in Unicode (to return to a previous = example)
(I'd be lynched by the W3C I18N group if I mapped it = to a private use
character, currently I map it to j)

David

________________________________________________________________= ________
This e-mail has been scanned for all viruses by Star = Internet. The
service is powered by MessageLabs. For more = information on a proactive
anti-virus service working around the clock, around = the globe, visit:
http://www.star.net.uk
________________________________________________________________= ________

------_=_NextPart_001_01C2C94F.2F1FAE80--