Bug 161582

Summary: Can't talk in channels whose name is composed of multibyte(at lease japanese) characters.
Product: [Applications] konversation Reporter: Yoshinari Takaoka <mumumu>
Component: generalAssignee: Konversation Developers <konversation-devel>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Yoshinari Takaoka 2008-05-04 01:16:42 UTC
Version:           the latest trunk (build #3223) (using KDE 3.5.9)
Installed from:    Ubuntu Packages
Compiler:          gcc 4.2.3 
OS:                Linux

I can't talk in channels whose name is composed of multibyte 
character(at least japansese). We cannot create such multibyte channel
in freenode, but can do it in Japan WIDE IRC Network ircd.

When I send privmsg in such channel, I got Error message
 "Error: #???? No Such nick or channel.", #???? is channel name 
which is garbled...

----

- How Reproducible.
Always

- Reproduce steps: 

1. Run Konvi, and Press "F2".
2. On Server List, Press "New".
3. Specify server "irc.nara.wide.ad.jp" which is ircd in Japan WIDE Network.
4. Press Identity "Edit" Button.
5. In Detail Tab, Specify Encoding "Japanese(iso-2022-jp)".
 (euc_jp, jis7, sjis is also ok)
6. Connect to the server. 
7. Join channel whose name is composed of multibyte character,
for example "/join #ใƒ†ใ‚นใƒˆ" (which means "/join #test" in English)
8. send privmsg to it, for example "/privmsg #test test"

- expected result:

i can see "test" in message view.

- actual result:

I got error. "Error: #???? No Such nick or channel.",
#???? is garbled ...
Comment 1 argonel 2008-05-08 21:05:30 UTC
SVN commit 805572 by argonel:

-new encoding handling now only applies to blowfish messages
-little bit of cleanup in ::_send_internal
BUG:161582


 M  +7 -9      blowfish/blowfish.cpp  
 M  +1 -1      blowfish/blowfish.h  
 M  +21 -29    server.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=805572
Comment 2 Yoshinari Takaoka 2008-05-08 21:29:20 UTC
I confirmed your fix with ascii, UTF-8(irc.ustream.tv), iso-2022-jp(Japan WIDE IRC Network). Many Thanks! argonel!