Re: Followup on the ccharset idea

[David Oftedal <david@start.no>]

>>>>1) it's a major pain in the ass to change your character encoding in
>>>>Windows.  As near as I can tell, setting a LC_* set of environment
>>>>variables doesn't do anything... assuming you know, for example, that
>>>>UTF-8 is code page 65001.  I can't find anywhere in Windows to change
>>>>the default code page -- only how to change it per-document!  I would
>>>>love to be able to tell X-chat to default to CP65001 automatically.

Hm, it was my understanding (ish) that the internationalized domain 
names weren't PURE UTF-8, but some sort of weird encoded shit based on a 
new standard. I rememner nunames (www.nu) tried making a UTF-8-enabled 
bind, but they then refused to release it based on "Security concerns" 
and wouldn't answer mail about it either. As for the verisign solution, 
at one point I remember there being a solution for international domain 
names that required a plugin that "translated" the domain name to some 
subdomain of VeriSign that didn't resemble the original name at all.

So are you SURE we're talking about pure, unmanipulated UTF-8 here?

-David

--
XChat-discuss: mailing list for XChat users
Archive:       http://mail.nl.linux.org/xchat-discuss/