Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Thu, 17 Jul 2003 22:48:29 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h6HKmIcH001375 for ; Thu, 17 Jul 2003 22:48:28 +0200 MIME-Version: 1.0 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 h6HKhXmp023107; Thu, 17 Jul 2003 22:43:34 +0200 (MET DST) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34CA4.C6CA4C80" 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 h6GM0AiD028243; Thu, 17 Jul 2003 22:43:04 +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 2527 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 17 Jul 2003 22:43:04 +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 h6HKh4M9007377 for ; Thu, 17 Jul 2003 22:43:04 +0200 Received: from ams.org (sun06.ams.org [130.44.1.6]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h6HKhTGl018889 for ; Thu, 17 Jul 2003 22:43:29 +0200 (MET DST) Received: from localhost (bnb@localhost) by ams.org (8.12.9/8.12.9) with ESMTP id h6HKhRpj006344 for ; Thu, 17 Jul 2003 16:43:28 -0400 (EDT) In-Reply-To: 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: 17 Jul 2003 20:48:35.0057 (UTC) FILETIME=[CA668610:01C34CA4] X-Scanned-By: MIMEDefang 1.0 (http://www.roaringpenguin.com/mimedefang/) X-Spam-Score: -15.7 () IN_REP_TO,REFERENCES,USER_AGENT_PINE Content-class: urn:content-classes:message Subject: Re: XML, UTF-8 and TeX engines Date: Thu, 17 Jul 2003 21:43:27 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: XML, UTF-8 and TeX engines Thread-Index: AcNMpMqjqfbTESyGTt+AJ0l84E0p2A== From: "Barbara Beeton" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4695 This is a multi-part message in MIME format. ------_=_NextPart_001_01C34CA4.C6CA4C80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 many characters you need different commands for text and math mode. I'd love to have a typesetting system to which I could pass a say 'small Greek letter alpha', and it would just work in every context. No font families, no encodings, no active/special characters, no babel settings, and no modes to worry about. Wonderful ... not quite. i'm with tim here. for math publication, it's traditional to have variables in italic. it's also traditional to have theorems in italic. unless it's marked as math, how can you tell that "a" in a theorem is a variable or the english indefinite article? knuth tried to avoid this by - using a slanted font instead of italic for theorems - making a math italic that is ever so slightly wider than text italic but it still definitely requires marking a math "a" as math. -- bb ------_=_NextPart_001_01C34CA4.C6CA4C80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: XML, UTF-8 and TeX engines

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
    many characters you need different = commands for text and math mode.
    I'd love to have a typesetting = system to which I could pass a say
    'small Greek letter alpha', and it = would just work in every context.
    No font families, no encodings, no = active/special characters, no
    babel settings, and no modes to = worry about.  Wonderful ...

not quite.  i'm with tim here.

for math publication, it's traditional to have = variables in
italic.  it's also traditional to have theorems = in italic.
unless it's marked as math, how can you tell that = "a" in a
theorem is a variable or the english indefinite = article?
knuth tried to avoid this by
 - using a slanted font instead of italic for = theorems
 - making a math italic that is ever so slightly = wider than
   text italic
but it still definitely requires marking a math = "a" as math.
          &nbs= p;            = ;            =             &= nbsp;        -- bb

------_=_NextPart_001_01C34CA4.C6CA4C80--