Re: [xsl] MSXML / NBSP problem and resolution

[Greg Faron <gfaron@xxxxxxxxxxxxxxxxxx>]

At 02:34 AM 11/8/2002, you wrote:
>   stylesheet line of
>   <td>&#160;</td>
>   creates the output
>   <td> </td>
>
> really a space or just a literal no break space character that looks
> like a space.
> In the former case it's a bug in the system.
>
>   latter to <td/>,
>
> even if it's a real space <td> </td> shouldn't get written using />

  Well, if anyone has figured out a way to prevent XML Spy from changing
<textarea ... ></textarea>  to  <textarea ... />
or
<script ... ></script>  to  <script ... />
or
<td ... > </td>  to  <td ... />,
I would love to know about it.  This changes happens when you use the 
auto-indent editing feature.
  Also as I've said in a previous post, a &#160; in the stylesheet becomes 
an honest-to-God regular space in the result.  This makes it difficult to 
put non-breaking spaces in HTML results without cheating and using the very 
sinful
<xsl:text disable-output-escaping="yes"><![CDATA[&#160;]]></xsl:text>.  I'd 
love to hear a fix for that one too if anyone know it.


Greg Faron
Integre Technical Publishing Co.



XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list