Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Fri, 18 Jul 2003 00:26:13 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h6HMQAcH001729 for ; Fri, 18 Jul 2003 00:26:11 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34CB2.6E01B080" Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h6HMKpmp004748; Fri, 18 Jul 2003 00:20:51 +0200 (MET DST) Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h6HM0DMr008378; Fri, 18 Jul 2003 00:20:18 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 0038 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 18 Jul 2003 00:20:18 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h6HMKIM9008671 for ; Fri, 18 Jul 2003 00:20:18 +0200 Received: from wisbech.cl.cam.ac.uk (mta1.cl.cam.ac.uk [128.232.0.15]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h6HMKhGl000692 for ; Fri, 18 Jul 2003 00:20:44 +0200 (MET DST) Received: from pallas.cl.cam.ac.uk ([128.232.8.88] helo=cl.cam.ac.uk ident=[oiLNxDs1CvkfO8v2mRxhTp+p0mxPz/oP]) by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1) id 19dH7E-0004hl-00 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 17 Jul 2003 23:20:44 +0100 In-Reply-To: Your message of Thu, 17 Jul 2003 19:52:38 +0100. <200307171952.38152.tim@birdsnest.maths.tcd.ie> Return-Path: X-OriginalArrivalTime: 17 Jul 2003 22:26:13.0471 (UTC) FILETIME=[6E498EF0:01C34CB2] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -6.6 () IN_REP_TO,QUOTED_EMAIL_TEXT Content-class: urn:content-classes:message Subject: Re: XML, UTF-8 and TeX engines Date: Thu, 17 Jul 2003 23:20:44 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: XML, UTF-8 and TeX engines Thread-Index: AcNMsm58DMkuFlSFRyCMmlPIkGythg== From: "Robin Fairbairns" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4698 This is a multi-part message in MIME format. ------_=_NextPart_001_01C34CB2.6E01B080 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > On Thursday 17 July 2003 11:10, Torsten Bronger wrote: > > > Surprisingly enough, TeX is the most serious limitation at the > > moment (of course also because it's so vital). It's still the best > > back-end for typesetting something, however its treatment of > > so-called special characters, lack of true unicode support, and the > > distinction text/math mode is really unfortunate. > > Wouldn't "true unicode support" require fonts with 64000 glyphs? it needs fonts with as many glyphs as your documents need. unicode has more than one plane, now, anyway. but you're right: the potential for type designers is awesome. > And isn't it quite sensible to distinguish between text and maths? i was wondering about that, too. do you actually _do_ maths, torsten? robin ------_=_NextPart_001_01C34CB2.6E01B080 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: XML, UTF-8 and TeX engines

> On Thursday 17 July 2003 11:10, Torsten Bronger = wrote:
>
> > Surprisingly enough, TeX is the most = serious limitation at the
> > moment (of course also because it's so = vital).  It's still the best
> > back-end for typesetting something, however = its treatment of
> > so-called special characters, lack of true = unicode support, and the
> > distinction text/math mode is really = unfortunate.
>
> Wouldn't "true unicode support" = require fonts with 64000 glyphs?

it needs fonts with as many glyphs as your documents = need.  unicode
has more than one plane, now, anyway.

but you're right: the potential for type designers is = awesome.

> And isn't it quite sensible to distinguish = between text and maths?

i was wondering about that, too.  do you actually = _do_ maths, torsten?

robin

------_=_NextPart_001_01C34CB2.6E01B080--