Hi

The   depends on "character encoding" only, it hasn't much to do
with xmpp.

It's the same with 
ü for ü
ö for ö
...

If you want to use   you have to start the stream with
"us-ascii" (which is default encoding for html - xhtml has utf-8 as
default encoding):

<?xml version='1.0' encoding="us-ascii"?>
<stream:stream xmlns="jabber:client" to=" ... " version="1.0"
xmlns:stream="http://etherx.jabber.org/streams"; >

Jabber Servers maybe don't support it.

Since windows 95 we have unicode (utf-8) it makes no sense to go back to
old us-ascii, iso-8859-x, EBCDIC, BCD,...

Bernhard


Am Donnerstag, den 04.01.2007, 22:35 +0200 schrieb Norman Rasmussen:
> What about just making whitespace significant in the xmpp spec?
> 
> i.e. most client will want to replace space with nbsp before
> displaying to the user, or maybe you can set a flag on the html
> renderer
> 
> On 12/15/06, Bernhard Zwischenbrugger <[EMAIL PROTECTED]> wrote:
> > Depends on encoding
> > &nbsp; is encoding="us-ascii"
> > > Is it possible to use &nbsp ?
> > >
> > >
> > UTF-8 does not allow &nbsp;
> > use &#160;
> >
> > Bernhard
> >
> >
> 
> 

Reply via email to