Automatic file encoding detection
GENERAL
TESTING
GENERAL
TESTING
Description
Attachments
3
- 09 Mar 2011, 09:43 AM
- 17 Sep 2010, 03:21 AM
- 11 Dec 2009, 01:49 AM
incorporates
is depended on by
is related to
Activity
Show:
Anthony Whyte August 9, 2011 at 3:52 AM
Changing the fix version to 1.1.13 to better express what version of kernel-1.1 contains the fixes that eliminate the regressions introduced by KNL-589.
David Horwitz August 9, 2011 at 12:43 AM
all related fixes now merged
Stephen Marquard August 3, 2011 at 10:31 PM
All the related issues need merging to 1.1.x. This change has caused several serious bugs which are fixed in the related issues.
Anthony Whyte July 28, 2011 at 2:39 PM
1.1.x r95856.
Sam Ottenhoff March 9, 2011 at 9:43 AM
Okay here are the steps to replicate this issue:
1) Go to a course site -> Resources
2) Upload the ejemplo.htm file attached to this JIRA
3) Note that pre 2.8 Sakai instances would serve the file as UTF-8 even though the file is encoded as ISO-8859-1
Sakai 2.8.0 should attempt to detect the encoding of the file and should correctly serve the file as ISO-8859-1.
Ways to test are Firebug (check the response headers) or curl.
If you create a file with non standard characters (for example: España) and try to access it, you will get strange symbols. That's because charset is not set neither in ResourceProperties when you upload the file nor BaseContentService when serving the file. I attach the patch for our 2.6.x installation under kernel 1.0.12.