Bug 182934 - Charset don't work in web Shortcuts
Summary: Charset don't work in web Shortcuts
Status: RESOLVED FIXED
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-03 00:21 UTC by Ignacio Serantes
Modified: 2009-11-02 14:59 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 Ignacio Serantes 2009-02-03 00:21:57 UTC 
Version:           4.2.00 (KDE 4.2.0) "release 83.3" (using 4.2.00 (KDE 4.2.0) "release 83.3", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (i686) release 2.6.27.7-9-pae

I'm using en_US.UTF-8 as my encoding.

I have a web shorcut to search for lyrics in goo.ne.jp with this configuration:

Name: goo
Search URI: http://music.goo.ne.jp/lyric/search.php?n=\{@}&lyric=%B2%CE%BB%EC%B8%A1%BA%F7&t=2
Charset: EUCP-JP

in Konqueror 4 and in Konqueror 3. If I search for goo:宇多田ヒカル in Konqueror 4 the URL generated was:

http://music.goo.ne.jp/lyric/search.php?n=宇多田ヒカル&lyric=�λ측��&t=2

and the search fails.

If I do the same search in Konqueror 3, goo:宇多田ヒカル, the URL generated was:

http://music.goo.ne.jp/lyric/search.php?n=%B1%A7%C2%BF%C5%C4%A5%D2%A5%AB%A5%EB&lyric=%B2%CE%BB%EC%B8%A1%BA%F7&t=2

and the search works.

I detected similar problems in other applications, like Ktts, kfmclient, Amarok, etc... and seems that character encoding in KDE 4 is extremely buggy.
Comment 1 Thiago Macieira 2009-08-05 00:33:32 UTC 
From your message, it looks like you wanted 宇多田ヒカル to be encoded as %B1%A7%C2%BF%C5%C4%A5%D2%A5%AB%A5%EB, which is not UTF-8.

That is a valid use-case, but apparently not supported yet.

So, this is not WONTFIX. This is a normal, missing feature.
Comment 2 Ignacio Serantes 2009-10-29 00:32:40 UTC 
Thanks to a member of KDE forums, generalzod, I test this bug again and is fixed in 4.3.2 but I don't know who or even when the correction was made.
Comment 3 urwald 2009-10-31 20:27:37 UTC 
Tested with 4.3.2 (openSUSE). Doesn't work. Still same, buggy behavior.

Please reopen the bug!
Comment 4 Ignacio Serantes 2009-10-31 20:45:15 UTC 
Works for me using openSUSE 11.1 with KDE 4.3.2 (KDE 4.3.2) "release 2" (packages labeled as 4.3.x in openSUSE repository, http://en.opensuse.org/KDE/Repositories#KDE_4.3.x).

If you can explain here a test case that fails I could determine if the bug is the same and I reopen it.

Please note that url don't use url encoding but encoding translation was fixed.
Comment 5 urwald 2009-11-01 08:01:08 UTC 
Well, my problem is the missing URL (percent) encoding.

Should I open a new bug for the URL encoding?
Comment 6 Ignacio Serantes 2009-11-01 11:21:18 UTC 
Yes, because this bug was related to encoding conversion and not about url encoding usage or not.
Comment 7 urwald 2009-11-01 15:12:40 UTC 
New Bug 212621 has been reported.