You are confusing yourself, as I stated multiple times above, this has nothing to do with reading characters between two mirc clients.
I have zero problems talking to other clients who use mirc 5.x. I am connected through UTF8 server and those others are connected from other server that supports EUC-KR charcode set. THIS IS NOT THE PROBLEM I AM DESCRIBING.
The link you posted has nothing to do with the issue above.
This is not a compatibility issue between clients.
It's a bug where any character with UTF-8 hexadecimal header that has A0 at the end that prevents me from joining or making a channel.
