Bug 120393 - special characters in file name cause these files cannot be opened from URI in preview
Summary: special characters in file name cause these files cannot be opened from URI i...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 3.4.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-18 17:26 UTC by CzarnyZajaczek
Modified: 2017-01-07 22:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description CzarnyZajaczek 2006-01-18 17:26:03 UTC 
Version:           3.4.2 (using KDE 3.4.2, Mandrake Linux Cooker i586 - Cooker)
Compiler:          Target: i586-mandriva-linux-gnu
OS:                Linux (i686) release 2.6.12-12mdk

I created new To-do, and added to it attachments, on local disk, in path to them are special characters (especially - polish letters). 
Then in a preview of this To-do, there are links to these attachments, encoded just like web-browsers do. But when i click on it, it cannot be opened, it shows message like this:

"
Unable to run the command specified. The file or folder file:///home/all/Dokumenty/Szko
Comment 1 Thiago Macieira 2006-01-21 18:31:48 UTC 
What is your system locale setting? (the value of the LANG variable)
Comment 2 Reinhold Kainhofer 2006-11-02 18:58:24 UTC 
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 3 Denis Kurz 2016-09-24 18:53:54 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 korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:44:26 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.