Version: (using KDE KDE 3.5.2) Installed from: Debian testing/unstable Packages On a WebDAV URL whose Content-Type is text/xml; charset="utf-8", the webdav protocol uses the wrong charset to decode file and directory names. The relevant code in /kdelibs/kioslave/http/http.cc seems to only use SlaveBase::remoteEncoding(), which in turn only relies on SlaveBase::metaData("Charset"), which is a property set by the calling application, not derived from the server's hints.
You may use the following URL for testing: webdav://www.shiny.co.il/ilya/kde-bug-127251-test/ It contains an English, a Hebrew and a Russian file name.
The problem is even more significant because manual changing of remote charset doesn't work properly for WebDAV (see bug 137154).
*** Bug 148016 has been marked as a duplicate of this bug. ***
*** This bug has been confirmed by popular vote. ***
Oops, I was only voting, but now I've managed to confirm the bug en passant - nice accident. :-) See bug 148016, the previous "target" of my vote and now a duplicate of this one, for some test results including a sniffed HTTP exchange posted by me.
New test url: webdav://webdav.directserver.org The old one does not work anymore.
BTW This is fixed in Suse's version of KDE3 and KDE4 (tested KDE 3 under Suse 10.3 and KDE 4 under Suse 11)
This seems to be fixed now (using KDE 4.3.2 (kdemod) in ArchLinux)
I confirm. It seems ok with KDE 4.2.3
Seems to be fixed.
*** Bug 137154 has been marked as a duplicate of this bug. ***
Created attachment 67156 [details] fix for KDE 3 I’ve looked at how KDE 4.2.4 fixed this and sorta re-implemented this in Qt3/KDE3 API. Please commit this to Trinity and Kubuntu LTS. Test-built by adding this to kdelibs-3.5.10/debian/patches/ then “dch --nmu” to make a 3.5.10-0ubuntu1~hardy1.5tarent1 version, building it in a clean Hardy cowbuilder chroot, and installing the result.