And wget and probably many others command unix tools and don't, care because with the exception of de factastic and ultra cool Qt 4 encodign system and KDE 4, all command programs and desktop environment in linux CAN HANDLE this files.
My congratulations for the mind behind Qt 4 encoding design. Not adding support for broken encoding names is as brilliant like desing a car only for cities and highways, that stops every time you drive for a road.
KDE 4 is an eyecandy desktop, but not a rock solid desktop for production. This bug, an all related to connecting to servers not working in english UTF-8, confirm this point.
I now really understand why Gnome was been using as default desktop in corporative linux distributions. Think in a spanish corporation, with thousands of old zip files and hundreds of workers with this problem.
And wget and probably many others command unix tools and don't, care because with the exception of de factastic and ultra cool Qt 4 encodign system and KDE 4, all command programs and desktop environment in linux CAN HANDLE this files.
My congratulations for the mind behind Qt 4 encoding design. Not adding support for broken encoding names is as brilliant like desing a car only for cities and highways, that stops every time you drive for a road.
KDE 4 is an eyecandy desktop, but not a rock solid desktop for production. This bug, an all related to connecting to servers not working in english UTF-8, confirm this point.
I now really understand why Gnome was been using as default desktop in corporative linux distributions. Think in a spanish corporation, with thousands of old zip files and hundreds of workers with this problem.