Re: RE: XSL and White Space help PLEASE

> > 7)   isn't legal in all encodings.  Make sure you are using an
encoding
> > for which it is acceptable.  Too bad, some browsers (especially
older ones)
> > don't interpret these encodings the same way.
>
> For both the html and xml output method, the XSL system must
> output   as a legal construction no matter what output encoding
is
> specified. (If 160 is in the encoding, it may use character data,
> otherwise a numeric character reference or a named entity reference
(eg
>  ) will be used.

And if   does make it through to the html output and so be left for
the browser to interpret, from HTML3 onwards the browser is *supposed*
to resolve the numeric reference as a Unicode code point and use that to
ask the rendering subsytem for an appropriate glyph. It should *not*
interpret it as a code point within the current encoding or the system's
default code page, though this frequently happens, and is even sometimes
quoted as "correct" behaviour. The (very good) idea behind this is that
(if properly implemented and supported by the OS as well as the browser)
it lets html pages contain characters that are outside the client's
default encoding repertoire.

Michael
-------------------------------------------------
Michael Beddow
http://www.mbeddow.net/


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