Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Thu, 10 Jul 2003 23:20:50 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h6ALKmcH003190 for ; Thu, 10 Jul 2003 23:20:48 +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 h6AL9ump005486; Thu, 10 Jul 2003 23:09:56 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34729.22D32500" 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 h69M03hJ021895; Thu, 10 Jul 2003 23:09:34 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 1566 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 10 Jul 2003 23:09:33 +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 h6AL9XM9032181 for ; Thu, 10 Jul 2003 23:09:33 +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 h6AL9amp005429 for ; Thu, 10 Jul 2003 23:09:37 +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 h6AL9ZU4028209 for ; Thu, 10 Jul 2003 17:09:35 -0400 (EDT) Received: (from hammond@localhost) by hilbert.math.albany.edu (8.12.5/8.12.5/Submit) id h6AL9YKq027292; Thu, 10 Jul 2003 17:09:34 -0400 (EDT) In-Reply-To: <3F0DC260.183ED82C@MartinHensel.de> Lines: 42 References: <3BFEACE361F5BF429DD1DA593E3A7C0922406A@xch-nw-28.nw.nos.boeing.com> <3F0BE0E6.E87B2479@MartinHensel.de> <3F0DC260.183ED82C@MartinHensel.de> Return-Path: X-OriginalArrivalTime: 10 Jul 2003 21:20:50.0796 (UTC) FILETIME=[234C9AC0:01C34729] 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: -33.4 () EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA Content-class: urn:content-classes:message Subject: Re: Invitation for discussion: My suggestion for a LaTeX3 syntax Date: Thu, 10 Jul 2003 22:09:34 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Invitation for discussion: My suggestion for a LaTeX3 syntax Thread-Index: AcNHKSNukSbmb05iRIeolKTDYMqGbg== From: "William F Hammond" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4676 This is a multi-part message in MIME format. ------_=_NextPart_001_01C34729.22D32500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Martin Hensel writes: > Sorry, I don't see your point. My conviction is that the current LaTeX > syntax can be improved with regard to legibility. Legibility is in the eye of the beholder. To say that your issues were addressed is not to say they were addressed in your way. > As far as I > understand GELLMU, this project tries to use the LaTeX syntax to > produce HTML documents, Really, _any_ XML document type. It's usually a waste of time to write HTML directly though it can be done and using gellmu to do so provides the advantage of macros with arguments. The point of an XML document type for authors is to be able to translate well to many other formats under a standard translation umbrella. An author should seek to occupy high ground in the land of markup languages. HTML is low ground for an author. > with improving the LaTeX syntax. Maybe you can point me to the correct > page? For example, look at the source (suffix ".glm") of the manual in http://www.albany.edu/~hammond/gellmu/glman/ > > That said, I would not propose to change the syntax of LaTeX itself > > unless it might be in conjunction with the introduction in LaTeX of > > \documenttype parallel to \documentclass. > > I'm not sure if you mean document type in the same sense as GELLMU > (\documenttype{html}). Presently gellmu article source goes through a two-stage pipeline to produce an XML document that is slightly pre-formatted (see appendix B.2.2 in the manual). Then a translation to LaTeX is obtained from that. It might be possible to have a future LaTeX engine handle gellmu article source for a more direct route to dvi or pdf. -- Bill ------_=_NextPart_001_01C34729.22D32500 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Invitation for discussion: My suggestion for a LaTeX3 = syntax

Martin Hensel <mail@MARTINHENSEL.DE> = writes:

> Sorry, I don't see your point. My conviction is = that the current LaTeX
> syntax can be improved with regard to = legibility.

Legibility is in the eye of the beholder.  To say = that your issues
were addressed is not to say they were addressed in = your way.

>          =             &= nbsp;           &n= bsp;           &nb= sp;     As far as I
> understand GELLMU, this project tries to use the = LaTeX syntax to
> produce HTML documents,

Really, _any_ XML document type.  It's usually a = waste of time to
write HTML directly though it can be done and using = gellmu to do so
provides the advantage of macros with = arguments.

The point of an XML document type for authors is to be = able to
translate well to many other formats under a standard = translation
umbrella.  An author should seek to occupy high = ground in the land of
markup languages.  HTML is low ground for an = author.

> with improving the LaTeX syntax. Maybe you can = point me to the correct
> page?

For example, look at the source (suffix = ".glm") of the manual in
http://www.albany.e= du/~hammond/gellmu/glman/

> > That said, I would not propose to change the = syntax of LaTeX itself
> > unless it might be in conjunction with the = introduction in LaTeX of
> > \documenttype parallel to = \documentclass.
>
> I'm not sure if you mean document type in the = same sense as GELLMU
> (\documenttype{html}).

Presently gellmu article source goes through a = two-stage pipeline to
produce an XML document that is slightly = pre-formatted (see appendix
B.2.2 in the manual).  Then a translation to = LaTeX is obtained from
that.  It might be possible to have a future = LaTeX engine handle
gellmu article source for a more direct route to dvi = or pdf.

          &nbs= p;            = ;            = -- Bill

------_=_NextPart_001_01C34729.22D32500--