Bug 194704

Summary:	Not able to send UTF-8 to channel with Latin-1 name
Product:	[Applications] konversation	Reporter:	Roger Olsson <master_pumpkin_>
Component:	general	Assignee:	Konversation Developers <konversation-devel>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	hein, wordsizzle
Priority:	NOR
Version:	1.2-alpha2
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:

Description Roger Olsson 2009-05-31 03:07:02 UTC

Version:           1.2-alpha2 (using KDE 4.2.3)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Fedora RPMs

If I'm on a channel whose name contains Latin-1 characters (like umlaut letters), and then select UTF-8 as that tab's encoding (actually, it's always UTF-8 in the 1.2-alpha2 version), Konversation translates the channel's name into UTF-8 and tries to send the message there, to a channel that doesn't exist. This bug occurred also in 1.1. The channel's encoding has to match that with which the channel's name is written, otherwise it's impossible to send anything there. (So, using the alpha is impossible on Latin-1 channel's.)

Comment 1 Travis McHenry 2009-05-31 06:53:33 UTC

SVN commit 975769 by tjmchenry:

Fix a porting bug caused by a connect listening for an incorrect signal. 
This bug caused the actions in the Set Encoding context menu to have no effect.
Setting encodings should now be possible again.
CCBUG: 194704

 M  +1 -1      mainwindow.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=975769

Comment 2 Travis McHenry 2009-05-31 07:03:52 UTC

With the above bugfix it should now be 'possible' for you to join Latin-1 channels. Please provide a complete set of steps (including a channel name) to reproduce the other part of your bug. 
Template:
Join channel *x*
Set encoding to *y*
Send message to channel *x*
Channel message gets sent to non-existant channel *z*

That way I can see the bug personally and have an easier time tracking it down.

Comment 3 Roger Olsson 2009-05-31 23:24:51 UTC

1. Set your profile's default encoding to "Western European ( ISO 8859-1 )".
2. Connect to IRCnet.
3. Join channel "#über" (doesn't exist right now).
4. Set the channel's encoding to "Unicode ( UTF-8 )".
5. Type something to the channel.

Result: "[Error] #über: No such nick/channel."

By using irssi-proxy (Irssi's proxy module) between IRCnet and my Konversation, I've found out that in this case Konversation tries to send the typed line to channel "#über" where "ü" is a UTF-8 character (Irssi creates a second log file).

Comment 4 Roger Olsson 2009-05-31 23:40:43 UTC

PS. You could start up another IRC client and with it join the UTF-8 channel and see how the message ends up there (provided that the channel's "n" flag is not set). The "No such nick/channel" error happens only if the other channel does not exist.

Comment 5 Eike Hein 2013-04-15 01:11:17 UTC

I can't reproduce this with current git, writing to an IRCnet channel with an umlaut in the name while using UTF-8 seems to work just fine here. Guess we fixed this at some point.