[Bug 304226] New: Unable to open files with 2-byte unicode whitespace from within kde

[karl.r.ernst at gmail.com]

https://bugs.kde.org/show_bug.cgi?id=304226

            Bug ID: 304226
          Severity: major
           Version: 4.8
          Priority: NOR
          Assignee: unassigned-bugs at kde.org
           Summary: Unable to open files with 2-byte unicode whitespace
                    from within kde
    Classification: Unclassified
                OS: Linux
          Reporter: karl.r.ernst at gmail.com
          Hardware: Gentoo Packages
            Status: UNCONFIRMED
         Component: general
           Product: kde

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

-- 
You are receiving this mail because:
You are the assignee for the bug.