This is from upstream bug-report:
``We will no longer support broken encodings in KDE. We have had transition code
for several years (at least since 2003) and I think 5 years is enough time for
people to finish transitioning to UTF-8 environments.
This bug is about broken-encoded files. *Properly* encoded filenames should be
working and if they aren't, please open a new bug report on the subject.
You will hate me for this, but this bug is a WONTFIX. 5 years is enough time.
If in 5 years you haven't renamed all your files, you should use the terminal
to do it.
I think their reasons for not supporting broken encodings are valid. However, I think that at least they should provide a tool for fixing the broken encodings. E.g. allowing the user to rename the files to a correct encoding.
This is from upstream bug-report:
``We will no longer support broken encodings in KDE. We have had transition code
for several years (at least since 2003) and I think 5 years is enough time for
people to finish transitioning to UTF-8 environments.
This bug is about broken-encoded files. *Properly* encoded filenames should be
working and if they aren't, please open a new bug report on the subject.
You will hate me for this, but this bug is a WONTFIX. 5 years is enough time.
If in 5 years you haven't renamed all your files, you should use the terminal
to do it.
More info on why this is close to impossible to implement: lists.kde. org/?l= kde-core- devel&m= 122025063320264 &w=2
http://
Do *not* reopen the bug.''
---------
I think their reasons for not supporting broken encodings are valid. However, I think that at least they should provide a tool for fixing the broken encodings. E.g. allowing the user to rename the files to a correct encoding.