Bug 212736

Summary: shortcut encoding doesn't work for external browsers
Product: [Applications] konqueror Reporter: urwald <urwald>
Component: generalAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: adawit, kde
Priority: NOR    
Version First Reported In: 4.3.2   
Target Milestone: ---   
Platform: unspecified   
OS: Unspecified   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description urwald 2009-11-02 14:56:58 UTC 
Version:            (using KDE 4.3.2)

Shortcut that are defined in konqueror are accessible also through KRunnder (Alt+F2).

However, the encoding settings doesn't work if konqueror is not your standard browser, but for example Firefox.

Example: I'm using a web shortcut to access the "Duden", the most common german
ortografic dictionary. This is the search term:
http://www.duden.de/suche/index.php?suchwort=\{@}&suchbereich=mixed
The encoding is ISO 8859-1.

Result when searching for "Täter" in konqueror:
http://www.duden.de/suche/index.php?suchwort=T�ter&suchbereich=mixed
This one works fine.

When pressing Alt+F2 and entering "shortcut:Täter" in KRunner who will launch Firefox as default browser, than Firefox will open this URL:
http://www.duden.de/suche/index.php?suchwort=Täter&suchbereich=mixed
This one doesn't work because the internet page doesn't accept this encoding.

One possible solution could be make a percent encoding in the charset that was specified for the shortcut (in this case ISO 8859-1) and than call Firefox with the resulting URL. Because the URL has only ASCII character after the percent encoding, this should work reliable. In our example, the URL would be:
http://www.duden.de/suche/index.php?suchwort=T%E4ter&suchbereich=mixed
Comment 1 Ignacio Serantes 2009-11-02 15:14:42 UTC 
Confirmed. KRunner don't do a proper encoding conversion even if your default browser is konqueror.

So, web shorcuts charset conversion works in konqueror but not in krunner Web Shorcuts plugin.
Comment 2 Dawit Alemayehu 2011-12-20 17:23:32 UTC 
This has been fixed already. Feel free to reopen if that is not the case for you with the latest version of KDE, v4.7.4 or higher.
Comment 3 Christoph Feck 2012-03-02 18:47:51 UTC 
Setting status correctly, see comment #2.