Project

General

Profile

Bug #844

Quassel handles special characters case-insensitive, while ircd doesn't

Added by fuzzy76 over 14 years ago. Updated over 13 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Quassel Core
Target version:
-
Start date:
10/29/2009
Due date:
% Done:

0%

Estimated time:
Version:
0.7-pre
OS:
Any

Description

I tried to join #tromsø and #tromsØ simultaneously on efnet. The network sees them as two separate channels, but Quassel didn't. It reported the join, but insisted on showing them in a single buffer. And when I left, I couldn't rejoin until I restarted the client.

History

#1 Updated by dalbers about 14 years ago

  • Assignee set to dalbers

#2 Updated by al over 13 years ago

  • Status changed from New to Confirmed
  • Assignee deleted (dalbers)
  • Version changed from 0.5.0 to 0.7-pre

The problem is that most IRC servers case-fold ASCII or even ISO-8859-something in channel names, but not e. g. UTF-8 encoded characters.
Quassel would need to implement a way to persist channel names when writing them to the database that follows the exact same rules that the IRC server implements regarding case-folding.

Also available in: Atom PDF