[Bug 510018]

[Hpj-u]

Calling this filesystem corruption is just an arrogant way to say:
we will not fix real world issues, we insist in the world fixing this.

Given, how easy it is to create such an item, e.g.:

        touch $(printf "snaf\374.txt")

this attitude is ridiculous.

Apart from unzip, we are bitten by a winscp/sshd combination, that doesn't encode properly
(all current versions).

@Thiago: wrongly encoded file names will *never* go away.

What would you thing, if the kernel would forbit access to files, that
you saved in a crypted filesystem container, because its filename has an
invalid encoding. Say, this contains an important work of yours. Guess
what, you would call this kernel names.

Next logical step would be to automatically *format* such a media in
order to prevent further propagation. Your argumentation would even
justify this. But face it: middle age is over, and the world isn't
turning around KDE, KDE is actively loosing users, because of this
attitude.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in Ubuntu.
https://bugs.launchpad.net/bugs/510018

Title:
  Cannot delete file with bad filename

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/510018/+subscriptions