I realise true unicode would be a lot easier, but until that's really added (and let's be honest, todo list items are not fixed sequencially) moving at least one unicode-related problem to the background would stop a lot of people I know from bitching about it (me included =).
porting a program wide switch to a window-relevant switch is a var addition to whatever struct or class that is used to control window settings, and moving the interpretation function into the window class from the probably lowerlevel incoming prvmsg it is now... that's debug included hard to imagine being more than an hour's work.
I'd gladly pay $30 for mirc if it had at least enough control to use for Japanese, for me. Of course that wouldn't help people in israel, thailand, or china, but then again those people aren't worse off either. it's just a temporary quickfix for a segement of users until the real issue (true unicode and codepage selection) is finally tackled by the mirc devteam.
Mike "Pomax" Kamermans
