If xchat is used with the crypt module, any received UTF-8 characters will be displayed as gibberish, regardless of the specified charset.
I believe it does this because the character perpended to the string ('€' on my system, '¤' on other's) is not a valid utf-8 character code. I've tested this, modifying the crypt.cpp file removing the old code (227 if i recall) and replacing it with an asterisk. Xchat should not change charsets just because it finds an invalid character there, and I'll file that bug with them. ZNC shouldn't be mixing character sets. The easiest way to fix the problem would be to choose a different character with an ASCII code below 128 or allow the user to configure which character to display explicitly.
If xchat is used with the crypt module, any received UTF-8 characters will be displayed as gibberish, regardless of the specified charset.
I believe it does this because the character perpended to the string ('€' on my system, '¤' on other's) is not a valid utf-8 character code. I've tested this, modifying the crypt.cpp file removing the old code (227 if i recall) and replacing it with an asterisk. Xchat should not change charsets just because it finds an invalid character there, and I'll file that bug with them. ZNC shouldn't be mixing character sets. The easiest way to fix the problem would be to choose a different character with an ASCII code below 128 or allow the user to configure which character to display explicitly.
<!-- github-sync-id:6727451 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
If xchat is used with the crypt module, any received UTF-8 characters will be displayed as gibberish, regardless of the specified charset.
I believe it does this because the character perpended to the string ('€' on my system, '¤' on other's) is not a valid utf-8 character code. I've tested this, modifying the crypt.cpp file removing the old code (227 if i recall) and replacing it with an asterisk. Xchat should not change charsets just because it finds an invalid character there, and I'll file that bug with them. ZNC shouldn't be mixing character sets. The easiest way to fix the problem would be to choose a different character with an ASCII code below 128 or allow the user to configure which character to display explicitly.