#566 closed defect (fixed)

Does not support Cyrillic (Russian) and possibly any non-ASCII nicknames in Jabber chats

Reported by: roman@… Owned by:
Priority: normal Milestone:
Component: BitlBee Version: 1.2.4
Keywords: unicode, utf-8, cyrillic, russian Cc:
IRC client+version: XChat 2.6 Operating System: Linux
OS version/distro: Debian Testing


In Jabber conferences (chats), Russian nicknames of consideralble length are displayed simply as "_" (one or several underscores).

Jabber conference tested: linuxforum on

Attachments (0)

Change History (7)

comment:1 Changed at 2010-02-28T23:39:53Z by Wilmer van der Gaast <wilmer@…>

It's unknown to me if using Cyrillic characters in IRC nicknames. Do you know of any client and/or server that allows it? BitlBee has to respect the IRC standard, for as much as one exists...

comment:2 Changed at 2010-02-28T23:54:02Z by anonymous

Yes, there's a lot of them. For example:

  • (UTF-8 encoding), the RusNet network (~10000 users)
  • (windows-1251 encoding) - DalNet.RU (~2000 users)

etc. As for the encodings, UTF-8 (and not any of the legacy ones) should be preferred.

comment:3 Changed at 2011-06-24T12:20:05Z by denis1482@…

Bump on this. Cyrillic nickname support is needed.

comment:4 Changed at 2011-06-24T12:24:52Z by wilmer

Bumping is okay, but keep in mind that this is a free software product with pretty much only one developer, there's only so much one person can do in his spare time. Maybe I'll get to this some day but there are *many* things to be done here.

Patches are much more useful than bumping.

comment:5 Changed at 2011-06-24T12:36:25Z by anonymous

Pardon me for being rude, I just wanted to show that the above user is not the only one who needs the thing. I do not thing I am skilled enough to make some productive patches, but I think I can cut off some lines from your code that check nickname validity... May be I'll give it a try. Thanks for your software and prompt answer!

comment:6 Changed at 2011-06-24T13:37:48Z by Wilmer van der Gaast <wilmer@…>

Removing the checks should not be too hard, no. But that'd not be enough as you do have to avoid characters like at least @, ! and spaces in the nickname. IRC protocol parsers will break horribly otherwise.

Also, you have to be careful with nickname comparisons as making those case-sensitive could also cause confusion. That'd be a ~simple matter of using an utf-8-safe comparison function though.

And yeah, no problem, your bump wasn't rude compared to many others I've seen. It's just important that people remember they're using a free product, too many users with an attitude as if they were my biggest paying customer.

comment:7 Changed at 2015-10-23T17:09:23Z by dx

Resolution: fixed
Status: newclosed

This was fixed around the 3.2.1 release (two years ago) with the addition of the utf8_nicks setting. Just confirmed it does work in this particular case, i see "Кощей", "Жаба" and "Котэ-Готэ" in the nick list of those channels.

Modify Ticket

as closed The ticket will remain with no owner.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.