Umbrella issue to track the handling of special chars in the Sakai conent store and related tools.
Colon allowed in filenames, leading to problems copying to WIndows folders
Broken link in Resources if folder created in WebDAV with apostrophe in name
Aliases with special charcters are allowed to be created, but the links do not work
UTF-16 text is misidentified as utf8
resources can't handle file with quote in the ID
Unable to export Roster with UTF-8 character names
utf8 support of edit a page name
Page title does not support special characters
Improper display of documents containing unicode content in Resources
utf8 support of user search
Cannot view attachment with foreign character file name
Folder name with _ and & can cause js issues
resources can't fetch a file with # in the name
Files with non-ASCII characters in their names attached to the submitted assignments are not accessible
webdav can create file names that content can't fetch
Tools sorting incorrectly international characters
Could not browse the uploaded recourse in the Vietnamese or Japanese folder
Creating site with special characters creates site, bu thet Site id is invalid.
Realms with special charcters are allowed to be created, but the links do not work
SiteAction doesn't allow UTF8 Aliases
Web content accepts URL with special characters, which is translated into a broken URL.
Uploaded files not using UTF-8 Unicode encoding do not display properly
Improve Unit tests re special chars in ContentHosting
URLs don't preserve utf8
Some test examples:
Will test against trunk Monday 15th 2010 and see if we can get a fuller list.
We should first verify that the tomcat, database and the database connector are all correctly configured for UTF-8 before trying to "work" on any of these issues. I resolved a few of them by just correctly configuring QA-6 and running through the QA.
Downgrading this, please upgrade sub tasks if you like but we don't want critical parents