Bug 304226

Summary: Unable to open files with 2-byte unicode whitespace from within kde
Product: [I don't know] kde Reporter: karl.r.ernst
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: major    
Priority: NOR    
Version: 4.8   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description karl.r.ernst 2012-07-29 07:55:51 UTC
If a filename has a 2-byte whitespace in it, I am unable to open it from within KDE. Filetype seem to not matter, tested with .jpg imags and plain text files.
Also tested to click on the file from within dolphin, and on the folder view on the desktop, both don't open.
Happens also withnon-kde apps, "open with -> gimp" also fails.

Another weirdness is that KDE seems to think this are 2 seperate files.
a file "test .jpg" -> open with -> gimp shows the gimp error message:
"/home/karl/test could not be openend: file not found
/home/karl/Dokumente/.jpg could not be openend: file not found"

Any other unicode 2-byte character seem to work fine though. Also "file -> open" from within the applications itself (like gwenview, kate) still work fine for the files

Reproducible: Always

Steps to Reproduce:
1. create a textfile "test"
2. open it and write something in it
3. rename the file to e.g. "te st"
4. try to open it
Actual Results:  
kate shows 2 empty files

Expected Results:  
the file with the string should be opened
Comment 1 Jekyll Wu 2012-07-29 08:00:04 UTC
Thanks for reporting.

*** This bug has been marked as a duplicate of bug 268771 ***