RE: [xsl] Problems rendering nbsp entity

["Michael Kay" <michael.h.kay@xxxxxxxxxxxx>]

You can probably force your processor to use either the entity reference
  or a character reference such as   in the output by using
<xsl:output encoding="us-ascii"/>.

Note with MSXML, however, this only affects the output if you are using
the XSLT processor's serializer, not the DOM's serializer, and if you
are outputting to a byte stream rather than a character stream.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx 

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx 
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of 
> John Aschenbrenner
> Sent: 26 September 2002 02:07
> To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx'
> Subject: [xsl] Problems rendering nbsp entity
> 
> 
> I know I've seen this before but I can't seem to find it in 
> the archives. My apologies if this has been answered one too 
> many times.
> 
> In the past when I wanted to render a non blanking space when 
> using XSL to render HTML I have just used the entity &#160; 
> I've even noticed that the &#160; entity is rendered as 
> &nbsp; in the HTML file when using the Saxon parser.  Most of 
> the time MSXML will render this appropriately as well.  
> However for some reason this does not work this time when 
> using that parser.  Now instead of getting the nicely 
> formatted document that I want, I end up with question marks 
> all over the place.  When I look at the HTML that was 
> rendered there are no actual question marks in it just blank 
> spaces where I wanted the &nbsp; to be.  I am assuming that 
> for each question mark rendered I am seeing the space.
> 
> Now after all that............
> 
> Is there a way when using MSXML to get it to return the 
> actual entity &nbsp; in the rendered HTML instead of some 
> space character.  For example instead of <td> </td> have it 
> render this <td>&nbsp;</td> The problem as many know with 
> using the entity &nbsp; as a literal in XSL is that it is not 
> defined.  Also, I do not really want to output it as a non 
> blank space in the HTML but rather render it directly as is - &nbsp;
> 
> Much Thanks in Advance,
> John Aschenbrenner
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 


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