Affects Version/s: trunk
Fix Version/s: None
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
< 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.