Bug 162009 - wrong encoding in message saying that file does not exist
Summary: wrong encoding in message saying that file does not exist
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
: 166123 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-05-12 19:44 UTC by Andrew Belitsky
Modified: 2010-09-19 04:26 UTC (History)
5 users (show)

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 Andrew Belitsky 2008-05-12 19:44:00 UTC 
Version:           1.0.99 (using 4.00.73 (KDE 4.0.73 >= 20080507, compiled sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-ARCH

system locale is ru_RU-UTF8
1. Create file with non-english characters in name, for example "/home/andrew/тест";
2. Open ~ folder in dolphin, copy this file with Ctrl+C, move this file to thrash.
3. Press Ctrl+V
4. Dialog window appear, and it say 'The file or folder /home/andrew/ÑеÑÑ does not exist.'
Comment 1 David Faure 2008-07-09 12:29:49 UTC 
*** Bug 166123 has been marked as a duplicate of this bug. ***
Comment 2 FiNeX 2008-12-20 12:23:40 UTC 
This could depend on #165044 but I'm not sure: bug #165044 is about opening and browsing files with particular encoding. This is about a string not printed correctly.

Anyway the root could be the same.
Comment 3 Dominik Tritscher 2009-06-12 21:36:33 UTC 
I don't think that this has anything to do with encoding. I just tested this using KDE4.3beta2 with a file name containing german umlauts "äöü" as well as with a file named "test". In both cases I got the same error claiming the file would not exist when I delete it after copying but before pasting.
Comment 4 Mark 2010-09-19 03:04:46 UTC 
Hi,

Please confirm that this issue is still present in that latest stable KDE version.

Thanx,
Mark
Comment 5 Andrew Belitsky 2010-09-19 04:26:05 UTC 
The error doesn't exist any more, bug can be closed.