Re: MSXML / NBSP problem and resolution
> The original problem was how to get an nbsp / #160 or equivalent into > the output, in order to make a table render correctly. (<td/> or <td> > </td> renders differently than <td> </td>.)
Just to chime in, I've had issues with this using XML Spy 4.4 to convert files (via MSXML 4). First, any occurrence of   in the XSL Stylesheet gets replaced with just a space character during processing, so a stylesheet line of
creates the output
This poses an issue within XML Spy since the auto-indent editing feature will truncate the latter to <td/>, but not the former. Furthermore, the stylesheet complains if you use instead, saying that the entity is not defined in a DTD.
Finally, the META tag that it _always_ generates _never_ has a closing tag, so it's essentially generating malformed XML. Example from one of my XSL transformations:
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Variable on One Side</title>
BTW, it's also a shame that MSXML ignores the "indent" attribute of xsl:output, but that's something else altogether.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format