From abaacb664385395ca8eb631cebc047c970107481 Mon Sep 17 00:00:00 2001 From: Bram Matthys Date: Mon, 27 Nov 2017 11:41:07 +0100 Subject: [PATCH] Permit 0xa0, if it appears inside UTF8 (via set::allowed-nickchars). This is the "non breaking space" outside UTF8 and thus was previously blacklisted. Keeping it blacklisted even if it appears in UTF8 is not really an option as it means some UTF8 characters can never be used, like the letter "nun" in Hebrew, and likely others. --- src/modules/charsys.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/modules/charsys.c b/src/modules/charsys.c index f9d3ed93e..97e1ec1fe 100644 --- a/src/modules/charsys.c +++ b/src/modules/charsys.c @@ -152,7 +152,6 @@ ILangList *ilanglist = NULL; /* These characters are ALWAYS disallowed... from remote, in * multibyte, etc.. even though this might mean a certain * (legit) character cannot be used (eg: in chinese GBK). - * - no breaking space * - ! (nick!user seperator) * - prefix chars: +, %, @, &, ~ * - channel chars: # @@ -161,7 +160,7 @@ ILangList *ilanglist = NULL; * [CHANGING THIS WILL CAUSE SECURITY/SYNCH PROBLEMS AND WILL * VIOLATE YOUR ""RIGHT"" ON SUPPORT IMMEDIATELY] */ -const char *illegalnickchars = "\xA0!+%@&~#$:'\"?*,."; +const char *illegalnickchars = "!+%@&~#$:'\"?*,."; /* Forward declarations */ int _do_nick_name(char *nick);