Subject: Re: [xsl] MSXML / NBSP problem and resolution From: David Carlisle <davidc@xxxxxxxxx> Date: Fri, 8 Nov 2002 12:34:22 GMT |
The other more pressing reason is that if you are starting the serialization of each node of the result tree as soon as it is added, which is what many XSLT processors attempt to do, you have to keep state while outputting the contents of the <head> element, in order to know whether you've reached the end and haven't yet output a <meta http-equiv="Content-Type">. That might be more work than the spec wants to require of an XSLT processor. actually it says it should output the meta immediately after the start of the head so it is not required to do this check (and saxon I think will give you two meta elements if you explictly write one into teh head within the stylesheet) David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] MSXML / NBSP problem and , Mike Brown | Thread | Re: [xsl] MSXML / NBSP problem and , Mike Brown |
RE: [xsl] MSXML / NBSP problem and , Thomas V. Nielsen | Date | [xsl] SiteGen software for managing, James Smith |
Month |