Bug 294944 - akregator cannot open page with accented characters.
Summary: akregator cannot open page with accented characters.
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: internal browser (show other bugs)
Version: GIT (master)
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-27 19:12 UTC by Luis Silva
Modified: 2016-09-25 18:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luis Silva 2012-02-27 19:12:22 UTC
Version:           GIT (master) (using KDE 4.8.0) 
OS:                Linux

Some feeds link their articles to pages with accented characters. Double clicking on these articles in akregator opens a browser but the acented characters in the url are not passed correctly so the page does not open without manual intervention (manually correcting the characters in the url bar).

Reproducible: Always

Steps to Reproduce:
Add the following feed to akregator:
http://feeds.feedburner.com/PublicoCiencias
Try to open any of the articles in an external browser.

Actual Results:  
The browser opens but since the url has accented characters, the page never shows and a "404 - File or directory not found." error is shown.

Expected Results:  
Accented characters should be passed correctly to the browser.

OS: Linux (i686) release 3.2.0-17-generic-pae
Compiler: gcc
Comment 1 Maarten De Meyer 2014-01-16 14:18:01 UTC
I'm sorry, the feed example you give no longer exists.
Could you give a new one?

Thanks.
Comment 2 Denis Kurz 2016-09-24 19:37:58 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Luis Silva 2016-09-25 17:17:42 UTC
I cannot reproduce this bug any more.
Tested with 5.3.0 on Neon.
Comment 4 Denis Kurz 2016-09-25 18:31:06 UTC
Thanks for your feedback, Luis.