WebDAV does not recognize UTF-8 characters (I18N)
Description
Activity
John Leasia January 4, 2008 at 7:23 AM
Tested using IE7 and FFox 2.0, XP, on qa1-US (oracle) and qa1-UK (mysql).
Created 2 folders, uploaded using resource file upload the 3 files into 1 folder, and uploaded the 3 files into the other using webdav. Files looked ok and all 6 files opened ok with resources and webdav.
Changed details to include copyright notice, and all 6 files again opened ok with both resources and webdav.
I did notice that the 'I agree' copyright window didn't dissapear after clicking I agree. Will file another Jira on that.
Beth Kirschner June 1, 2007 at 2:36 PM
Testing:
1. Create both ascii & unicode test files, e.g. test.doc ¿¿¿¿.doc Español .doc
2. Verify files can be viewed, downloaded, and revised from Resources tool
3. Verify files can be viewed, downloaded and revised from WebDAV client
4. Set the copyright notice on the files and again verify files can be viewed, downloaded & revised from Resources tool
(note WebDav does not currently recognized copyright restrictions – this should be written up separately if desired)
5. Verify above with both Mozilla and MS IE browsers (note Windows needs to support the specified language before testing)
Beth Kirschner May 29, 2007 at 2:39 PM
Note that related to this issue, there is a known problem with the Safari browser: If you attempt to download a UTF-8 encoded filename via the Resources tool (not WebDAV), you will successfully download the file, but the filename will be the percent-encoded version of the actual name.
Beth Kirschner May 29, 2007 at 2:34 PM
The problems opening UTF-8 encoded filenames have been resolved.
Beth Kirschner May 29, 2007 at 8:06 AM
There are still some outstanding issues with opening files with UTF-8 filenames...
WebDAV does not currectly represent pathnames (filesnames and directory names) with UTF-8 characters. This affects file uploads, downloads and /access/.../{resource-file-name} as well.