Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 7 Jul 2003 17:57:20 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h67FvIPP011166 for ; Mon, 7 Jul 2003 17:57:18 +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 h67Fo8Gl023171; Mon, 7 Jul 2003 17:50:08 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C344A0.7252F000" 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 h677rPZB016396; Mon, 7 Jul 2003 17:49:56 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 1465 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 7 Jul 2003 17:49:56 +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 h67FnuM9023760 for ; Mon, 7 Jul 2003 17:49:56 +0200 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.189]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h67FntGl023136 for ; Mon, 7 Jul 2003 17:49:55 +0200 (MET DST) Received: from [212.227.126.160] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19ZYFV-0006Nk-00 for LATEX-L@listserv.uni-heidelberg.de; Mon, 07 Jul 2003 17:49:53 +0200 Received: from [212.159.41.120] (helo=MartinHensel.de) by mrelayng.kundenserver.de with asmtp (SSLv3:RC4-MD5:128) (Exim 3.35 #1) id 19ZYFU-0007B7-00 for LATEX-L@listserv.uni-heidelberg.de; Mon, 07 Jul 2003 17:49:53 +0200 References: <3F075002.72955C93@MartinHensel.de> <16137.32354.704318.984160@pussy.npc.de> Return-Path: X-Mailer: Mozilla 4.75 [de] (Win98; U) X-OriginalArrivalTime: 07 Jul 2003 15:57:20.0885 (UTC) FILETIME=[72D9FA50:01C344A0] X-Accept-Language: de,en X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -10.1 () QUOTED_EMAIL_TEXT,REFERENCES,USER_AGENT_MOZILLA_XM Content-class: urn:content-classes:message Subject: Re: Invitation for discussion: My suggestion for a LaTeX3 syntax Date: Mon, 7 Jul 2003 16:31:16 +0100 Message-ID: A<3F099244.1434BFF3@MartinHensel.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Invitation for discussion: My suggestion for a LaTeX3 syntax Thread-Index: AcNEoHL4ZplPP0WKQeemZKA6dxyA/w== From: "Martin Hensel" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4648 This is a multi-part message in MIME format. ------_=_NextPart_001_01C344A0.7252F000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > These paragraphs made quite clear that the author didn't know a > thing about TeX constraints (and is erroneous about space handling > in HTML and XML as well). Obviously somebody who is new to > technical details of existing markup languages. > > So the probability to find something worthwile in the rest of the > text was not high enough to spend the time reading further. Could you please explain to me, where I'm wrong with HTML and XML? I wrote: ,-----[ syntax.pdf ]----- | In languages like HTML, XML, and most programming languages spaces | are treated as following: Line breaks are considered as spaces, | two or more spaces are considered as a single space. `----- The HTML specification ,-----[ http://www.w3.org/TR/html401/struct/text.html ]----- | only the following characters are defined as white space | characters: | - ASCII space ( ) | - ASCII tab ( ) | - ASCII form feed ( ) | - Zero-width space (​) | Line breaks are also white space characters. : ... | For all HTML elements except PRE, sequences of white space | separate "words" (we use the term "word" here to mean "sequences | of non-white space characters"). When formatting text, user agents | should identify these words and lay them out according to the | conventions of the particular written language (script) and target | medium. : ... | For example, in Latin scripts, inter-word space is typically | rendered as an ASCII space ( ), `----- The XML specification ,-----[ http://www.w3.org/TR/REC-xml ]----- | S (white space) consists of one or more space (#x20) characters, | carriage returns, line feeds, or tabs. | | White Space | [3] S ::=3D (#x20 | #x9 | #xD | #xA)+ `----- Martin ------_=_NextPart_001_01C344A0.7252F000 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Invitation for discussion: My suggestion for a LaTeX3 = syntax

> These paragraphs made quite clear that the author = didn't know a
> thing about TeX constraints (and is erroneous = about space handling
> in HTML and XML as well). Obviously somebody who = is new to
> technical details of existing markup = languages.
>
> So the probability to find something worthwile = in the rest of the
> text was not high enough to spend the time = reading further.

Could you please explain to me, where I'm wrong with = HTML and XML?

I wrote:
,-----[ syntax.pdf ]-----
| In languages like HTML, XML, and most programming = languages spaces
| are treated as following: Line breaks are = considered as spaces,
| two or more spaces are considered as a single = space.
`-----

The HTML specification
,-----[ http://www.w3.org/= TR/html401/struct/text.html ]-----
| only the following characters are defined as white = space
| characters:
| - ASCII space (&#x0020;)
| - ASCII tab (&#x0009;)
| - ASCII form feed (&#x000C;)
| - Zero-width space (&#x200B;)
| Line breaks are also white space characters.
: ...
| For all HTML elements except PRE, sequences of = white space
| separate "words" (we use the term = "word" here to mean "sequences
| of non-white space characters"). When = formatting text, user agents
| should identify these words and lay them out = according to the
| conventions of the particular written language = (script) and target
| medium.
: ...
| For example, in Latin scripts, inter-word space is = typically
| rendered as an ASCII space (&#x0020;),
`-----

The XML specification
,-----[ http://www.w3.org/TR/REC-xml = ]-----
| S (white space) consists of one or more space = (#x20) characters, |
carriage returns, line feeds, or tabs.
|
| White Space
|    [3]    = S    ::=3D    (#x20 | #x9 | #xD | = #xA)+
`-----



Martin

------_=_NextPart_001_01C344A0.7252F000--