On Tue, 2003-10-21 at 02:03, Rimas Kudelis wrote: > Hi again, > > And Moz 1.4 =) > > `tiz because they use the same engine etc. :) How about IE? there is an > option to encode url's as UTF-8 AFAIR, right? There are plugins for MSIE apparenlty... http://nic.se/english/projekt/programvara_idn.shtml > > > But IDN support in XChat is a much different issue than changing the > > > default and/or current character set. To that issue, I have two > > > contributions (if you consider them that!) to the discussion: > > > > Well, no, not if you are forced to change the charset that the entire app > uses. > > That's a bug, IMHO ;) It should be *FIXED*, not feature-added. No, thats how X-Chat is designed, now guess why i want to be able to set a default charset =). > > > 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. > > LOL! of course you can't change the charset in windows! Especially to UTF-8. > Windows only changes it's default charset when you change your locale > (Lithuanian/Russian/Swedish). Anyways, Win2000/XP support unicode and use it > internally, so i guess it's a problem of X-Chat being ported from UNIX, that > it's not recognized as a unicode app. Hummm, i admit it's been to long, but couldn't xchat run utf8 on a common winshit machine? or, gtk2 relies to much on the local os and stuff? -- Ian Kumlien <pomac@vapor.com>
This is a digitally signed message part