[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
At 2002-11-06 15:17 -0500, Schwartz, Rechell R, ALCAS wrote:
Then it is obliged to be well-formed XML.
When you think you need it, you are probably thinking off on a tangent and are missing the opportunity to do things "cleanly" with nodes.
For best results with XSLT you need to represent the node tree structure of your result in the node tree structure of your stylesheet ... see http://www.biglist.com/lists/xsl-list/archives/200210/msg00411.html for a recent post where I try to emphasize this point.
XSLT is a node manipulation environment, not a markup manipulation environment, and your approach is attempting to do raw markup, which opens up the opportunity to shoot yourself in the foot (and isn't portable to all XSLT processors).
Remember that XML is case sensitive. You say "<TD>" above, but your code says "<td>".
Try restructuring your approach to never use disable-output-escaping.
I hope this helps.
...................... Ken
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Re: [xsl] Disable Output Esacping Problems
Subject: Re: [xsl] Disable Output Esacping Problems From: "G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx> Date: Wed, 06 Nov 2002 15:48:18 -0500 |
At 2002-11-06 15:17 -0500, Schwartz, Rechell R, ALCAS wrote:
I am trying to generate an HTML file that will really be generated as an XML file and then be used as input to another XSL stylesheet
Then it is obliged to be well-formed XML.
In the first XSLT file I need (or I think I need) to disable output esacping
When you think you need it, you are probably thinking off on a tangent and are missing the opportunity to do things "cleanly" with nodes.
For best results with XSLT you need to represent the node tree structure of your result in the node tree structure of your stylesheet ... see http://www.biglist.com/lists/xsl-list/archives/200210/msg00411.html for a recent post where I try to emphasize this point.
XSLT is a node manipulation environment, not a markup manipulation environment, and your approach is attempting to do raw markup, which opens up the opportunity to shoot yourself in the foot (and isn't portable to all XSLT processors).
because I need to generate non-symmetrical XML tags. The disabling of output esacping generates the expected output, but the second XSLT file doesn't seem to recognize the <TD> and <TR> tags whose output was escaped and fails to apply the appropriate styling to these tags.
Remember that XML is case sensitive. You say "<TD>" above, but your code says "<td>".
Try restructuring your approach to never use disable-output-escaping.
I hope this helps.
...................... Ken
-- Upcoming hands-on in-depth XSLT/XPath and/or XSL-FO: - North America: Feb 3 - Feb 7,2003
G. Ken Holman mailto:gkholman@xxxxxxxxxxxxxxxxxxxx Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995) ISBN 0-13-065196-6 Definitive XSLT and XPath ISBN 0-13-140374-5 Definitive XSL-FO ISBN 1-894049-08-X Practical Transformation Using XSLT and XPath ISBN 1-894049-10-1 Practical Formatting Using XSL-FO Next conference training: 2002-12-08,03-03,06
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Disable Output Esacping P, David Carlisle | Thread | RE: [xsl] Disable Output Esacping P, Schwartz, Rechell R, |
[xsl] Disable Output Esacping Probl, Schwartz, Rechell R, | Date | Re: [xsl] Disable Output Esacping P, Joerg Heinicke |
Month |