Well, the point is, to my knowledge no ircd (atleast not dalnet and undernet), support upper and lower cases for none a-z chars. Implementing something into mIRC that is not supported by the major networks is not very smart. It can maybe push the developers into action and add the support, but it is not a small change of the ircd and will take time. Until then we are left with this problem. And if someone register the channel #Ö with the networks channel registration service, and later the network decide that #ö and #Ö is the same channel, it will cause yet another problem where one user loose a channel in favor of another.
This just wasn't smart to ad until the major networks fully supported utf-8.
I understand your point, but please consider that mIRC was not the first IRC client to support UTF-8... in fact, it was one of the
last major clients to do so. This problem really has nothing to do with mIRC.
