Modify ↓
Opened at 2017-03-05T10:12:54Z
Last modified at 2021-09-21T08:10:21Z
#1285 new enhancement
Support unicode channel names.
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | BitlBee | Version: | devel |
Keywords: | Cc: | ||
IRC client+version: | Client-independent | Operating System: | Public server |
OS version/distro: |
Description
I am using bitlbee with libpurple-telegram. Unicode nicks work well with setting utf8_nicks on. Unfortunately unicode symbols in channel names are replaced with question marks. Seems that g_convert_with_fallback function fails to transliterate cyrillic symbols (german letters work fine).
I dug into the code and have found in irc_channel.c this comment:
/* RFC 1459 keeps amazing me: While only a "few" chars are allowed in nicknames, channel names can be pretty much anything as long as they start with # or &. I'll be a little bit more strict and disallow all non-printable characters. */ }} I am wondering if it is possible to introduce new setting 'utf8_channels'?
Attachments (0)
Change History (3)
comment:1 Changed at 2017-09-25T17:27:16Z by
comment:2 Changed at 2018-01-16T17:44:24Z by
The same problem. Have huge number of question marks instead of channel names.
comment:3 Changed at 2021-09-21T08:10:21Z by
The issue is still there. Is there any hopes to get it fixed please?
Note: See
TracTickets for help on using
tickets.
Yes, I second that issue. Cyrillic channel names in telegram make groups unusable -- even if transliteration goes fine (supported by locale), you really can't use regular procedure with "chat list" followed by "chat add" and "/join" with telegram-purple. Even if you manage to create the channel, after joining any message triggers "sending message failed", and parting the channel triggers "nil: no such channel" from server.