Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Thu, 17 Jul 2003 18:31:32 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h6HGVMcH000442 for ; Thu, 17 Jul 2003 18:31:31 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h6HGOFGl015836; Thu, 17 Jul 2003 18:24:16 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34C80.E18ACA00" 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 h6GM0Ad5028243; Thu, 17 Jul 2003 18:23:39 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 2021 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 17 Jul 2003 18:23:39 +0200 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.3/8.12.3/SuSE Linux 0.6) with ESMTP id h6HGNdM9004730 for ; Thu, 17 Jul 2003 18:23:39 +0200 Received: from smtp.albany.edu (mail1.csc.albany.edu [169.226.1.133]) by relay.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h6HGO5mp021468 for ; Thu, 17 Jul 2003 18:24:05 +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 h6HGO13v014709 for ; Thu, 17 Jul 2003 12:24:02 -0400 (EDT) Received: (from hammond@localhost) by hilbert.math.albany.edu (8.12.5/8.12.5/Submit) id h6HGO0TD018638; Thu, 17 Jul 2003 12:24:00 -0400 (EDT) In-Reply-To: <16150.26432.179873.408825@pussy.npc.de> Lines: 31 References: <20030710081528.A12401@diabolo.informatik.rwth-aachen.de> <78ADDA01-B2DC-11D7-8AE7-0050E4455404@atlis.com> <20030711081704.A14039@diabolo.informatik.rwth-aachen.de> <16146.60345.852158.31606@pussy.npc.de> <16150.26432.179873.408825@pussy.npc.de> Return-Path: X-OriginalArrivalTime: 17 Jul 2003 16:31:33.0692 (UTC) FILETIME=[E28CF7C0:01C34C80] 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 Was (Re: OT: ANT) Date: Thu, 17 Jul 2003 17:24:00 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: XML, UTF-8 and TeX engines Was (Re: OT: ANT) Thread-Index: AcNMgOKrCo2GWVK2T32DccZKzcWA0Q== From: "William F Hammond" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4688 This is a multi-part message in MIME format. ------_=_NextPart_001_01C34C80.E18ACA00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Joachim Schrod writes: > As much as I respect James, I can only agree with him here on a very > very abstract level. With "style sheets" above I didn't mean > transforming XML to other markup languages, I meant *directly* > typesetting XML documents, with a *very* high quality, and including I view my xml -> latex step as translation of a markup language to a typesetting language and, correspondingly, view the sgmlspl script for it as the functional equivalent of a "style sheet". I don't see why it matters that the step from xml document to dvi or pdf is a pipeline that uses (pdf)latex. > ... sheet front has not stopped here and will continue after the XML > hype is gone. I'm not sure what you mean by xml hype. Not all xml document types are document markup languages; for example, ctan-catalogue-entry is not a markup but is structured data. Authors who want re-useable source should use an xml document type that is a document markup language. The difference between that and present LaTeX is that the author's content is then stored under a template for generalized processing and is, therefore, (if the document type is good) maximally re-useable. Moreover, it is possible to determine in a format independent way if such a document instance is technically correct. Good LaTeX markup can come very close to meeting that criterion, but it's very hard to define just what good LaTeX markup is. -- Bill ------_=_NextPart_001_01C34C80.E18ACA00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: XML, UTF-8 and TeX engines Was (Re: OT: ANT)

Joachim Schrod <jschrod@ACM.ORG> writes:

> As much as I respect James, I can only agree with = him here on a very
> very abstract level. With "style = sheets" above I didn't mean
> transforming XML to other markup languages, I = meant *directly*
> typesetting XML documents, with a *very* high = quality, and including

I view my xml -> latex step as translation of a = markup language to a
typesetting language and, correspondingly, view the = sgmlspl script for
it as the functional equivalent of a "style = sheet".  I don't see why
it matters that the step from xml document to dvi or = pdf is a pipeline
that uses (pdf)latex.

> ... sheet front has not stopped here and will = continue after the XML
> hype is gone.

I'm not sure what you mean by xml hype.  Not all = xml document types
are document markup languages; for example, = ctan-catalogue-entry is
not a markup but is structured data.  Authors = who want re-useable
source should use an xml document type that is a = document markup
language.  The difference between that and = present LaTeX is that the
author's content is then stored under a template for = generalized
processing and is, therefore, (if the document type = is good) maximally
re-useable.  Moreover, it is possible to = determine in a format
independent way if such a document instance is = technically correct.

Good LaTeX markup can come very close to meeting that = criterion, but
it's very hard to define just what good LaTeX markup = is.

          &nbs= p;            = ;            = -- Bill

------_=_NextPart_001_01C34C80.E18ACA00--