Bug 193002 - command charset doesn't work, returns encoding not valid
Summary: command charset doesn't work, returns encoding not valid
Status: RESOLVED FIXED
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks: 187307
  Show dependency tree / graph
 
Reported: 2009-05-17 14:08 UTC by kaddi.bug
Modified: 2009-05-17 16:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description kaddi.bug 2009-05-17 14:08:12 UTC 
Version:           Version 1.1.75+ #3400 (Debian 1.1.75+svn965785-0ubuntu1~jaunty1~ppa1) (using KDE 4.2.3)
OS:                Linux
Installed from:    Ubuntu Packages

Hi,

when entering the command /charset utf8 or /charset iso-8859-1 the encoding isn't changed, but the following error message appears:
"[Fehler] iso-8859-1 ist keine gültige Kodierung."
("[Error] iso-8859-1 is not a valid encoding")

The command worked a couple of weeks ago, both with utf8 and iso-8859-1. I upgraded from KDE 4.2.1 to KDE 4.2.3 in between, it might be related. 

regards
Comment 1 Peter Simonsson 2009-05-17 16:19:45 UTC 
SVN commit 969156 by psn:

Make ambiguousNameToShortName work as expected by using a QHash for
looking up the encoding. Fixes the /charset command.
BUG: 193002


 M  +7 -16     irccharsets.cpp  
 M  +2 -4      irccharsets.h  


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