Alexandre N. Safiullin wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >>>>>>"a" == admin <[EMAIL PROTECTED]> writes: >>>>>> > > a> On Tue, 12 Feb 2002, Matthias Wimmer wrote: > >>> I believe that JIDs are not case sensitive, but case should be retained > >>> for display. > >> The user and domain part is not case sensitive - the resource part is. > > a> Note that some transports are buggy. At least AIM-t and ICQv7-t both are > a> case sensitive concerning JIDs. > > Yeah.. In order to properly fix it plz tell me whether user (and server ;) ) > parts of JID can be non-ASCII (i.e. UTF8)? > Tough question :-) Case insensitivity is only done in most implementations based on US7ASCII characters, i.e � != �.
I do not think DNS allows for non-US7ASCII characters at all currently (at least if you go by RFCs), but the host portion is meant to have the exact same restrictions as DNS names. I believe that some implementations will allow you to declare local components named with extended characters, in this case those same implementations would most probably default to case-sensitive comparisons of those characters. Completely undefined behavior :-) -David Waite _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
