Improper display of documents containing unicode content in Resources
Description
Attachments
is incorporated by
Activity
Neal Caidin November 18, 2013 at 1:14 PM
Closing this issue based on Jean-Francois comment. If this does not work in a supported version of Sakai (currently Sakai 2.8.x and Sakai 2.9.x) please feel free to open a new ticket.
Jean-François Lévêque March 4, 2010 at 3:45 AM
This seems to be fixed at least since 2.6.0. Could you check again on QA servers, Andrew?
David Horwitz January 25, 2010 at 4:57 AM
MAINTANCE TEAM: Unassigned so these get reviewed by the Maintance Team
Peter Knoop January 9, 2008 at 12:20 PM
[Bulk Comment] This issue had 2.5 as a Target Version, however, the issu has not been updated since 01 December 2007. For now its Target Version is being rest to know, but please update this field when you have a new estimate of when you tentatively plan to address the issue.
Peter Knoop April 18, 2007 at 7:57 AM
Is this still an active issue as of 2.4.0? If so, please update the Affects Version to include the latest 2.4 tag (e.g., 2.4.0.010). If not, please Close it with a resolution of Incomplete. Thanks.
Documents containing unicode characters are incorrectly displayed by Internet Explorer 6 and Firefox. Unicode characters appear as question marks.
Strangely, if you View Source and save the source to a local file then open that local file using the same browser, the unicode characters display correctly. It seems that neither Sakai nor the browser are munging the unicode characters, but when the browser sources the file from Sakai it displays them differently than when it sources them from an identical local file.
The Content-Type header sent by Sakai appears to specify "charset=UTF-8". Is this not enough to convince the browser to render unicode characters?
> GET /access/content/user/ajpoland/J200Session14.html HTTP/1.1
User-Agent: curl/7.13.1 (powerpc-apple-darwin8.0) libcurl/7.13.1 OpenSSL/0.9.7i zlib/1.2.3
Host: oncourse.iu.edu
Pragma: no-cache
Accept: /
< HTTP/1.1 200 OK
< Set-Cookie: JSESSIONID=648c0c9c-4c2e-4a71-80ea-cfedda84fff0.wsa412; Path=/
< Set-Cookie: X-Mapping-dnpmnlfm=9C6D6F3C155C12E1D2317FE9767D66FA; path=/
< Content-Length: 34868
< Date: Tue, 01 Aug 2006 20:31:33 GMT
< Content-Disposition: inline; filename="J200Session14-fixed2.html"
< Server: Apache
< Content-Type: text/html;charset=UTF-8
This problem happens in a 2.2 maintenance branch based production environment as well as in the current nightly build.