Subject: Re: Using the disable-output-escaping attribute From: "Chuck White" <chuck@xxxxxxxxxxxxxxxxxxxxxx> Date: Wed, 18 Aug 1999 08:10:51 -0700 |
So using the disable-output-escaping attribute was unnecessary. I used the xsl-output element's text attribute at the top level in my original code, and removing the disable-output-escaping attribute didn't alter the results (in other words, it still gave me what I wanted). So I guess it's the output element I should be cheering. Thanks for clearing that up. Chuck White Creative Director ADVANCE Recruitment Advertising, Inc. chuck@xxxxxxxxxxxxxxxxxxxxxx http://www.advancerecruitment.com ---------- >From: James Clark <jjc@xxxxxxxxxx> >To: xsl-list@xxxxxxxxxxxxxxxx >Subject: Re: Using the disable-output-escaping attribute >Date: Wed, Aug 18, 1999, 3:29 AM > > >The disable-output-escaping attribute is best for those cases where you >are producing something that is almost HTML or XML but not quite (eg XML >with some ASP or JSP directives). If you are producing something that is >not at all like XML, it's easier just to add a top-level declaration: > ><xsl:output method="text"/> > >James > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: Using the disable-output-escapi, James Clark | Thread | xsl parser listing, Russell Allen |
xsl parser listing, Russell Allen | Date | Outputting multiple HTML files, Alexandre Ratti |
Month |