(In reply to comment #60)
> Yes, by all means, keep posting comments like these.
>
> The apex of offensive, non-constructive and baseless...
Actually I think Ignacio managed to express exactly how I feel about this bug, on the first two paragraphs of comment #59.
If you (KDE, kdelibs, Qt, whatever) chose to not support those filenames, fine. But that's _your_ design decision[1], don't blame the other tools. I would even find this Qt/KDE design requirement acceptable if I had a tool to "fix" my filenames. But I don't have even that.
I know you don't have any obligation implement that to help your users, but refusing to do so is a great way to send the message that you don't care about your users.
---
[1] If you still disagree with that, try submitting a Linux kernel patch to make it reject non-utf8 filenames, and see what happens. ;)
(In reply to comment #60)
> Yes, by all means, keep posting comments like these.
>
> The apex of offensive, non-constructive and baseless...
Actually I think Ignacio managed to express exactly how I feel about this bug, on the first two paragraphs of comment #59.
If you (KDE, kdelibs, Qt, whatever) chose to not support those filenames, fine. But that's _your_ design decision[1], don't blame the other tools. I would even find this Qt/KDE design requirement acceptable if I had a tool to "fix" my filenames. But I don't have even that.
I know you don't have any obligation implement that to help your users, but refusing to do so is a great way to send the message that you don't care about your users.
---
[1] If you still disagree with that, try submitting a Linux kernel patch to make it reject non-utf8 filenames, and see what happens. ;)