This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Avoiding disable-output-escaping
- To: "Xsl-List (E-Mail)" <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] Avoiding disable-output-escaping
- From: Sebastian Schirmer <schirmer at sitewaerts dot de>
- Date: Fri, 27 Apr 2001 12:46:53 +0200
- Reply-To: xsl-list at lists dot mulberrytech dot com
>> I try to generate JSP from XML. In these JSPīs, I need output
>> tags like this one:
>
>> <sw:hpath startscan="0" endscan="100" startpath="2" />
>Just write the following in your stylesheet, making sure the namespace is
>declared:
><sw:hpath startscan="0" endscan="100" startpath="2" />
>>
>> How can I get such an expression without disable-output-escaping?
>Why do you think you need disable-output-escaping for this?
Ok, for these tags it works fine now but how to realise this:
<%@ include file="/includes/futuna.inc" %>
>> from a lookup in an external XML file that looks like this:
>>
>>
>> <env-entry>
>> <env-entry-name>JSPHeader</env-entry-name>
>> <env-entry-type>java.lang.String</env-entry-type>
>> <env-entry-value><![CDATA[
>> <head>
>> <sw:base target="_UNTEN" />
>> <title><sw:cv key="name" /></title>
>> <sw:meta />
>> <link rel="stylesheet" type="text/css"
>> href="styles/content.css"/>
>> </head>
>>
>> ]]></env-entry-value>
>> </env-entry>
>>
>Ah, you've got a problem there. The CDATA section is telling the XML parser
>to treat the stuff inside it as text rather than as XML, so you lose all
the
>benefits of using XML markup. Why are you doing this?
So a page designer who knows HTML can easily work or change parts of pages
without knowing XML. He does not have to pay attention to unclosed <img> or
other tags, ....
Sebastian Schirmer
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list