Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 3 Feb 2003 00:40:03 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h12Ne16C016195 for ; Mon, 3 Feb 2003 00:40:02 +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 h12NXqXM012412; Mon, 3 Feb 2003 00:33:52 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2CB14.68554B80" 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 h12N036H030154; Mon, 3 Feb 2003 00:25:23 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 6416 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 3 Feb 2003 00:25:23 +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 h12NPN5f030407 for ; Mon, 3 Feb 2003 00:25:23 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h12NX0tt028937 for ; Mon, 3 Feb 2003 00:33:00 +0100 (MET) Received: from [212.227.126.161] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 18fTbh-0003T5-00 for LATEX-L@listserv.uni-heidelberg.de; Mon, 03 Feb 2003 00:33:01 +0100 Received: from [80.129.3.15] (helo=istrati.mittelbach-online.de) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 18fTbh-0001uR-00 for LATEX-L@listserv.uni-heidelberg.de; Mon, 03 Feb 2003 00:33:01 +0100 Received: (from frank@localhost) by istrati.mittelbach-online.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id h12NUrF14791; Mon, 3 Feb 2003 00:30:53 +0100 In-Reply-To: <200301311603.QAA22049@penguin.nag.co.uk> References: <200301311603.QAA22049@penguin.nag.co.uk> Return-Path: X-Mailer: VM 6.96 under Emacs 20.7.1 X-OriginalArrivalTime: 02 Feb 2003 23:40:03.0961 (UTC) FILETIME=[68E7EE90:01C2CB14] X-Authentication-Warning: istrati.mittelbach-online.de: frank set sender to frank@mittelbach-online.de using -f X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -0.7 () IN_REP_TO,REFERENCES,SPAM_PHRASE_00_01,X_AUTH_WARNING Content-class: urn:content-classes:message Subject: Re: latex/3480: Support for UTF-8 missing in inputenc.sty Date: Mon, 3 Feb 2003 00:30:53 +0100 Message-ID: A<15933.43565.751843.247809@istrati.mittelbach-online.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: latex/3480: Support for UTF-8 missing in inputenc.sty Thread-Index: AcLLFGkmskJgNVYzTN+QmyfYq9VYow== From: "Frank Mittelbach" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4524 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2CB14.68554B80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable David Carlisle writes: > > > 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 > > Additions (or especially) corrections to the field in > http://www.w3.org/Math/characters/unicode.xml > are always welcome. as Roozbeh said, this would need some better idea what the semantics of = that field are, the contents looks rather ... (not saying :-) ... > The TeX support for various SGML/XML/Unicode tools is derived from > this file most notably Sebastian's jadetex and passivetex systems for > dsssl and xsl respectively, which is where the file originated, > although this version is distributed as part of the MathML = specification > sources. well, if we would like to see decent TeX support it might be good to get = some grip on that but first it would need a clear understanding of the = fields, eg what is the text/math notation supposed to mean? is this also TeX = related? i guess with a suitable utf8 support plus a suitable translation from fontencoding specific commands (LICR) to math commands, (ie something = like inpmath) we could come up with a list for unicode that would allow = better support than what is currently in that file, since that would then work consistently throughout text and math selecting the right glyphs inside = TeX as needed frank ------_=_NextPart_001_01C2CB14.68554B80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: latex/3480: Support for UTF-8 missing in = inputenc.sty

David Carlisle writes:
 > > > 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
 >
 > Additions (or especially) corrections to = the <latex> field in
 > http://www.w3.org/= Math/characters/unicode.xml
 > are always welcome.

as Roozbeh said, this would need some better idea what = the semantics of that
field are, the contents looks rather ... (not saying = :-) ...

 > The TeX support for various = SGML/XML/Unicode tools is derived from
 > this file most notably Sebastian's jadetex = and passivetex systems for
 > dsssl and xsl respectively, which is where = the file originated,
 > although this version is distributed as = part of the MathML specification
 > sources.

well, if we would like to see decent TeX support it = might be good to get some
grip on that but first it would need a clear = understanding of the fields, eg
what is the text/math notation supposed to mean? is = this also TeX related?

i guess with a suitable utf8 support plus a suitable = translation from
fontencoding specific commands (LICR) to math = commands, (ie something like
inpmath) we could come up with a list for unicode = that would allow better
support than what is currently in that file, since = that would then work
consistently throughout text and math selecting the = right glyphs inside TeX as
needed


frank

------_=_NextPart_001_01C2CB14.68554B80--