[jdev] SASL debugging
norman at rasmussen.co.za
Sat Dec 10 03:56:35 CST 2005
Supporting the stringprep profiles is not the same same as what is
normally understood by 'full unicode support'. Stringprep is used to
convert characters that look the same, into the same character. e.g.
you use 'e', and I use 'ê', someone else uses 'è' - after nodeprep
they would all be 'e' (as far as I understand).
As you found, sometimes the .net framework actually does a utf-16
encoding when you ask it for utf-8. This has nailed me recently when
trying to use webservices. I ended up having to add and remove the
'marker' bytes (0xff, 0xfe) at the front of the byte array to get it
to work properly.
On 12/9/05, Yves Goergen <nospam.list at unclassified.de> wrote:
> On 09.12.2005 17:22 (+0100), Matthias Wimmer wrote:
> > Yves Goergen schrieb:
> >>Btw, is it allowed to use non-Latin1 (real Unicode) usernames and
> >>passwords? Maybe I should test this, too, to see if it works.
> > Yes, there are many characters above U+0100, that are allowed in
> > usernames. What is allowed is defined by a stringprep profile called
> > "nodeprep".
> > Same for the passwords, but using the SASLprep profile.
> Umm... I followed that word and its references but stopped reading all
> of them because after a few lines each I realised I didn't understand a
> word. So I guess I simply assume full Unicode support... The relevant
> parts of the used protocols are UTF-8-encoded, so it should work fine
> Yves Goergen "LonelyPixel" <nospam.list at unclassified.de>
> "Does the movement of the trees make the wind blow?"
> http://newsboard.unclassified.de - Unclassified NewsBoard Forum
- Norman Rasmussen
- Email: norman at rasmussen.co.za
- Home page: http://norman.rasmussen.co.za/
More information about the JDev