Bug 137154 - kio webdav - cannot change remote encoding
Summary: kio webdav - cannot change remote encoding
Status: RESOLVED DUPLICATE of bug 127251
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: webdav (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-10 14:52 UTC by bugs-kde
Modified: 2011-12-25 20:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugs-kde 2006-11-10 14:52:25 UTC
Version:           3.5.2 (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages
OS:                Linux

I'm using kio webdav to access two remote WebDAV repositories, one is running Apache Slide, the other one Subversion:

webdavs://server1.address:8080/slide/files/
webdavs://server2.addres/svn/

There's also a public repository available for testing:
webdav://www.shiny.co.il/ilya/kde-bug-127251-test


In both cases I can connect successfully, and navigate the directory tree and copy files, but only if the directory/file names only contain plain ASCII characters.

If I stumble upon non-ASCII names, I see garbage characters and I cannot copy those files/directories (I receive an error stating "the file or directory webdavs://server2.addres/svn/%C3%90..etc... doesn't exist" - note the hex-encoded characters).

All this could be worked around if the changing of remote encoding would work (through Tools->Select Remote Charset). But when I choose any character set from over there, it stays at "Default" anyway and nothing changes WRT displayed names.

Note that the problem definitely lies in KIO.

Given the same repositories, the Gnome file manager (Nautilus - using dav:// and davs:// URLs) and Microsoft Office (using http:// and https:// URLs in file Open dialog, tested with 2007 Beta, but should work the same with all versions since MS Office 2000) work perfectly.

They automatically detect charsets of those repositories (usually UTF-8) and all names are displayed correctly and files can be opened or copied. I currently open Nautilus to access those repositories.

KIO could handle this perfectly too, if bug 127251 is solved.
Comment 1 bugs-kde 2006-11-10 15:02:10 UTC
Also related: bug 125212 and bug 125351.
Comment 2 Dawit Alemayehu 2011-12-25 20:58:32 UTC

*** This bug has been marked as a duplicate of bug 127251 ***