Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 3 Feb 2003 19:23:54 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h13INp6C019219 for ; Mon, 3 Feb 2003 19:23:52 +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 h13I3Ftt023831; Mon, 3 Feb 2003 19:03:15 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2CBB1.68575900" 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 h133iQQj031075; Mon, 3 Feb 2003 18:55:33 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 7644 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 3 Feb 2003 18:55:33 +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 h13HtXPw005037 for ; Mon, 3 Feb 2003 18:55:33 +0100 Received: from spmler3.mail.eds.com (spmler3.mail.eds.com [194.128.225.186]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h13I3CXM003538 for ; Mon, 3 Feb 2003 19:03:12 +0100 (MET) Received: from spmlir3.mail.eds.com (spmlir3-2.mail.eds.com [205.191.69.205]) by spmler3.mail.eds.com (8.11.6/8.11.6) with ESMTP id h13I38c09248 for ; Mon, 3 Feb 2003 18:03:08 GMT Received: from spmlir3.mail.eds.com (localhost [127.0.0.1]) by spmlir3.mail.eds.com (8.11.6/8.11.6) with ESMTP id h13I37g19879 for ; Mon, 3 Feb 2003 18:03:07 GMT Received: from gbspm001.exemhub.exch.eds.com ([207.37.51.199]) by spmlir3.mail.eds.com (8.11.6/8.11.6) with ESMTP id h13I37f19873 for ; Mon, 3 Feb 2003 18:03:07 GMT Received: by GBSPM001 with Internet Mail Service (5.5.2655.51) id <1HBYM8TX>; Mon, 3 Feb 2003 18:03:02 -0000 Return-Path: X-Mailer: Internet Mail Service (5.5.2655.51) X-OriginalArrivalTime: 03 Feb 2003 18:23:54.0099 (UTC) FILETIME=[68667430:01C2CBB1] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -1.7 () EMAIL_ATTRIBUTION,EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01 Content-class: urn:content-classes:message Subject: AW: latex/3480: Support for UTF-8 missing in inputenc.sty Date: Mon, 3 Feb 2003 19:02:59 +0100 Message-ID: A<630BE70C8320D6118D240002A589ABB204A9504F@DERUM201> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AW: latex/3480: Support for UTF-8 missing in inputenc.sty Thread-Index: AcLLsWiGNYz6YLlESEG05b8eDs80AQ== From: "Mittelbach, Frank" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4528 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2CBB1.68575900 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable David wrote: > That's just another way of saying the latex field should have LICR > commands. For Latex use only it would be just as easy to define the > mappings directly in the latex package files but having them in that = XML > would I think help translators from XML (especially MathML) to TeX to > come up with consistent mappings, as all the MathML entities and > character documentation is derived from there. right, but the question is the ownership of data. I think it would be a = good idea for us (LaTeX/TeX world) to maintain a source file that gives the mapping from unicode to LICR (having decided what the LICR's are. The move from that file to the unicode file could then be done by some automated process have to rush off, more from home frank ------_=_NextPart_001_01C2CBB1.68575900 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable AW: latex/3480: Support for UTF-8 missing in = inputenc.sty

David wrote:

> That's just another way of saying the latex field = should have LICR
> commands. For Latex use only it would be just as = easy to define the
> mappings directly in the latex package files but = having them in that XML
> would I think help translators from XML = (especially MathML) to TeX to
> come up with consistent mappings, as all the = MathML entities and
> character documentation is derived from = there.

right, but the question is the ownership of data. I = think it would be a good
idea for us (LaTeX/TeX world) to maintain a source = file that gives the
mapping from unicode to LICR (having decided what the = LICR's are.

The move from that file to the unicode file could then = be done by some
automated process

have to  rush off, more from home

frank

------_=_NextPart_001_01C2CBB1.68575900--