Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Fri, 18 Jul 2003 15:54:05 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h6IDrvcH004251 for ; Fri, 18 Jul 2003 15:54:03 +0200 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 h6IDlomp024541; Fri, 18 Jul 2003 15:47:50 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34D34.0D1ABC80" 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 h6HM0DfB008378; Fri, 18 Jul 2003 15:47:12 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 1047 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 18 Jul 2003 15:47:12 +0200 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.3/8.12.3/SuSE Linux 0.6) with ESMTP id h6IDlBM9018038 for ; Fri, 18 Jul 2003 15:47:11 +0200 Received: from smtp.albany.edu (mail1.csc.albany.edu [169.226.1.133]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h6IDlcGl000200 for ; Fri, 18 Jul 2003 15:47:38 +0200 (MET DST) Received: from hilbert.math.albany.edu (hilbert.math.albany.edu [169.226.23.52]) by smtp.albany.edu (8.12.5/8.12.5) with ESMTP id h6IDla3v028806 for ; Fri, 18 Jul 2003 09:47:36 -0400 (EDT) Received: (from hammond@localhost) by hilbert.math.albany.edu (8.12.5/8.12.5/Submit) id h6IDlZIL022996; Fri, 18 Jul 2003 09:47:35 -0400 (EDT) In-Reply-To: Lines: 34 References: <20030710081528.A12401@diabolo.informatik.rwth-aachen.de> <16150.26432.179873.408825@pussy.npc.de> <200307171952.38152.tim@birdsnest.maths.tcd.ie> Return-Path: X-OriginalArrivalTime: 18 Jul 2003 13:54:07.0998 (UTC) FILETIME=[0EE431E0:01C34D34] User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -32.8 () EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA Content-class: urn:content-classes:message Subject: Re: XML, UTF-8 and TeX engines Date: Fri, 18 Jul 2003 14:47:35 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: XML, UTF-8 and TeX engines Thread-Index: AcNNNA7+YVF2BYbeTOC7+akj3A5P4A== From: "William F Hammond" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4711 This is a multi-part message in MIME format. ------_=_NextPart_001_01C34D34.0D1ABC80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Barbara Beeton writes: > timothy murphy asked, > > > And isn't it quite sensible to distinguish between text and = maths? > > and torsten bronger responded, > > XML doesn't do it and I find this very convenient. In (La)TeX, = for This statement about XML is not helpful without reference to a particular document type. For example, gellmu article does provide elements called "math" and "displaymath", which when formatted to LaTeX switch on the corresponding math mode. As LaTeX is evolving it will be possible for gellmu's "alpha" (an empty element marked up in Gellmu source as \alpha) to be formatted in LaTeX as (math) \alpha when recursively inside a math element and not inside either of gellmu's "mbox" or "text", while outside of math "alpha" could easily be morphed to a suitable unicode point. And Timothy Murphy wrote: > Wouldn't "true unicode support" require fonts with 64000 glyphs? That's roughly the number of points in a single plane of unicode. The current design provides 16 planes, but I believe that less than half are defined. Not all of these points correspond to simple glyphs. For example, some points are combining characters. -- Bill ------_=_NextPart_001_01C34D34.0D1ABC80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: XML, UTF-8 and TeX engines

Barbara Beeton <bnb@AMS.ORG> writes:

> timothy murphy asked,
>
>     > And isn't it quite = sensible to distinguish between text and maths?
>
> and torsten bronger responded,
>
>     XML doesn't do it and I = find this very convenient.  In (La)TeX, for

This statement about XML is not helpful without = reference to a
particular document type.

For example, gellmu article does provide elements = called "math" and
"displaymath", which when formatted to = LaTeX switch on the
corresponding math mode.

As LaTeX is evolving it will be possible for gellmu's = "alpha" (an
empty element marked up in Gellmu source as \alpha) = to be formatted in
LaTeX as (math) \alpha when recursively inside a math = element and not
inside either of gellmu's "mbox" or = "text", while outside of math
"alpha" could easily be morphed to a = suitable unicode point.

And Timothy Murphy wrote:

> Wouldn't "true unicode support" require = fonts with 64000 glyphs?

That's roughly the number of points in a single plane = of unicode.  The
current design provides 16 planes, but I believe that = less than half
are defined.  Not all of these points correspond = to simple glyphs.
For example, some points are combining = characters.

          &nbs= p;            = ;            = -- Bill

------_=_NextPart_001_01C34D34.0D1ABC80--