Well,if we can specify a different encoding it should be the default xwiki encoding; of course it's UTF-8 in my case. Of course ideally, it should be just absent because, as you say, you can't be sure of the charset before you actually sniff into it.
Where is this coded for the download action?The problems that it cause are simple: applet parameters get garbled and thus make the applet non-working.
thanks in advance paul Le 04-oct.-09 à 11:30, Sergiu Dumitriu a écrit :
I wish you were right and it would be configurable by the tomcat but it's not the case. The same tomcat serves: http://i2geo.net/files/movies/index.htm with: Content-Type: text/html; charset=utf-8 so you are saying you can't do anything against it?We can specify a different encoding, but how can we guess it? We could use a library that guesses the encoding of a file. But is it worth the (computational) effort? What problems does this cause?
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
