After this viewtopic.php?t=82685 thread has been closed and my question is still unansered I want stress it once more:

Do you think it is OK to have files that KDE4 cannot open nor rename?

As far as I see this concern to filenames on:
- samba shares exported non-UTF8, e.g. ISO8859-15 exported
- archived file systems
- zip/rar/zoo/lha archives

Consequences:
- no access to these files
- nepomuk/strigi wont index these files

Further question:
- can nekomuk handle handle files where the content is ISO8859-15 encoded?

To cearify: these files and filenames are no problem outside KDE4.

First of all, I think that reasons exposed for "neverendingo" are valid for close previous topic and was a good decision.

Second, obviously the question is trivial and the answer is no.

But, the problem is not a question of opinion or not because the person that must fix this problem can't do it and, for him, bug "don't care". As I explain in the previous post, the problem was not in KDE and is the origin is a mixture of bad design and wrong decisions taken for the designers of Qt4.

I work in a company that develops a very specific framework and I know a lot about compatibility decisions and, my experience of almost ten years, told me that break compatibility without offers and alternative is the worst decision. Naturally we have a customers that pay us so, if we broke something we must fix it and with KDE that kind of obligation don't exists.

Well, we can see the funny side. We now have two glorious computer phrases:
1) "640K is more memory than anyone will ever need" (attributed to Bill Gates).
2) "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" (Thiago Macieira 2008, https://bugs.kde.org/show_bug.cgi?id=165044#c12).

It is not Ok !!

Please, can anyone provide a plugin for dolphin to fix this problem ?

i sometimes face the same with files on a usb drive which are written to it from windows

to rename the file open konsole and go to the folder

attempt #1
mv filename newname
if the 1st letters of the filename are english write them and click tab to let bash complete the rest the way it sees right

attempt #2
mv filename newname
write the filename of the bad file - substituting any unknown letters with ?'s. you still can try to use tab for automatic completion

attempt #3
remove everything else including hidden files from the folder with the affected file
mv * newname

And, do you think this behaviour is ok?

Zayed wrote:It is not Ok !!

Please, can anyone provide a plugin for dolphin to fix this problem ?

You can vote the next wish https://bugs.kde.org/show_bug.cgi?id=204768 that I created.

samhain wrote:And, do you think this behaviour is ok?

Seriously, what are you targeting at? Do you really think it is a question if it is okay or not and done?
Like Ignacio already said, the problem is a bigger one. Thiago also said in the bugreport the WONTFIX means he won't fix it because of missing infrastructure.
So, collecting yes' and no's is no solution at all.
Maybe not even wishlist items. What is needed is a person/a group of persons willing to take up the huge task of fixing it.

Ignacio Serantes wrote:You can vote the next wish https://bugs.kde.org/show_bug.cgi?id=204768 that I created.

I already did that

The only way to have this bug fixed at the moment would seem to be to fix it yourself.

While it is said that the true origin of the bug is in the qt4 infrastructure, someone will either have to patch that code, or, rewrite huge chunks of other code to work-around the problem.

While this is the default behavior of KDE, the only current work-around is use of the command line. For users without the required command line expertise, another option would perhaps be to use Gnomes file manager to deal with this issue.

Where's the point in using KDE4 then? KDE4+workaround is hard to maintain.

Well, the point is that outside of English, KDE 4 is not for normal users so, sadly, I don't recommend KDE 4 in an Spanish environment.

I'm not sure if I right but, KDE 4 will be the default desktop in openSUSE 11.2 but, in Novell Suse Enterprise I doubt that dare to do that.

how is the l10n pack used related to all this ?

ash wrote:how is the l10n pack used related to all this ?

In any form I guess. Legacy encoding problems was not related with l10n.

I believe that both SLES and SLED use KDE 4 at this time, or will in the not too distant future.

bcooksley wrote:I believe that both SLES and SLED use KDE 4 at this time, or will in the not too distant future.

Despite my criticisms of some aspects of KDE 4 I'm a fan, if not why I would lost my time using it, but for enterprise environments KDE 4 is not ready outside English language.

I think this will be a wrong idea because you can play with open source version without problem, it's free, it's your decision, but for a corporate environment, when you pay for your solution, play with your customers it's not good for your business.