Subject: Re: XSL formatting objects to HTML From: Paul Prescod <papresco@xxxxxxxxxxxxxxxx> Date: Fri, 16 Oct 1998 21:31:47 -0400 |
Chris Lilley wrote: > > XML does not have these restrictions because there is no hard-coded > processing of the elements. Also, it is much easier to generate a > consistent parse tree from XML than from an SGML application (no omited > start or end tags, etc) and for consistent presentation of CSS- (or > indeed of XSL-) styled documents, a consistent parse tree is essential. It isn't really true that it is hard to parse SGML-based HTML. In fact, it is very easy, with or without an SGML parser -- substantially easier than parsing XML (no general text entities, for example). If browsers cannot properly and consistently parse valid HTML, then there is no real excuse for it. The real problem is that the de facto definition of HTML is very different from the de jure definition, and the de facto definition is *brutal* to parse reliably. But that shouldn't affect their support of real HTML (though it probably does). Paul Prescod - http://itrc.uwaterloo.ca/~papresco 4'33" is rarely performed as an encore. - Steve Newcomb (for info about 4'33": http://www.lenzo.com/~sburke/stuff/cage_433.html http://www.intrex.net/rwgarr/johncage.htm) XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: XSL formatting objects to HTML, Chris Lilley | Thread | Re: XSL formatting objects to HTML, \"Pasqualino \\\"Tit |
Re: XSL formatting objects to HTML, Chris Lilley | Date | Re: The XSL-List Digest V1 #184, Jonsm |
Month |