X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1118" "Fri" "27" "November" "1998" "11:14:25" "+0000" "Sebastian Rahtz" "s.rahtz@ELSEVIER.CO.UK" nil "35" "Re: portable LaTeX" "^Date:" nil nil "11" nil nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id NAA14378; Fri, 27 Nov 1998 13:05:10 +0100 (MET) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <7.0653FCA8@listserv.gmd.de>; Fri, 27 Nov 1998 13:05:09 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 411445 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 27 Nov 1998 13:05:02 +0100 Received: from pillar.elsevier.co.uk (root@pillar.elsevier.co.uk [193.131.222.35]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id NAA09076 for ; Fri, 27 Nov 1998 13:04:54 +0100 (MET) Received: from snowdon.elsevier.co.uk [193.131.197.164]; by pillar.elsevier.co.uk (8.8.5/8.8.5) with ESMTP; for ""; sender "s.rahtz@elsevier.co.uk"; id LAA16925; hop 0; Fri, 27 Nov 1998 11:56:38 GMT Received: from srahtz (actually host srahtz.elsevier.co.uk) by snowdon.elsevier.co.uk with SMTP (PP); Fri, 27 Nov 1998 12:04:02 +0000 X-Mailer: emacs 20.3.2 (via feedmail 9-beta-3 Q); VM 6.61 under Emacs 20.3.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199811261814.NAA16984@hilbert.math.albany.edu> Message-ID: <13918.35217.61736.372419@srahtz> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <199811261814.NAA16984@hilbert.math.albany.edu> Date: Fri, 27 Nov 1998 11:14:25 +0000 From: Sebastian Rahtz Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: portable LaTeX Status: R X-Status: X-Keywords: X-UID: 2943 William F. Hammond writes: > This could as well be: > > \documenttype{article} which is not valid XML, so whats the point? > If I run this markup through my elisp, I get the following sgml: but i want the *source* be to useable, not a result munged by some script!!! >

> >

Introduction

> > a + 3 This is fun > >

not valid XML either :-} ... > The main idea is that this type of markup is amenable to robust > processing toward *any* target once an sgml processor for that target but it goes through you (inevitably flaky) elisp. thats the flaw. if you *started* with valid *ML markup, wouldnt it be even easier? > Note that this approach is different from that of James Clark's "jade" > which "centralizes" style for all "backends" using a DSSSL stylesheet please don't blame James Clark in person for the fundamental concepts of DSSSL, an ISO standard developed after a decade of work... Sebastian