These are the most fragile parts I find.Provided xwiki fully switches to utf-8, it should care that a form that is submitted via POST or GET is properly received. What I reached with simple xwiki and default settings were pretty poor in this respect (till the fact to recommend no accents in titles).
Is there a way to provide at the application level the parsing of URIs?I think that's the critical part, and is mostly fragile for the parameters where user-input appears.
paul PS: Looking with envy to clean URLs such as http://fr.wikipedia.org/wiki/été which is properly redirected to: http://fr.wikipedia.org/wiki/été and has translation: http://fa.wikipedia.org/wiki/تابستان Le 17-mars-09 à 15:09, Sergiu Dumitriu a écrit :
There are a few more settings for various containers. For example, Tomcat users must use these (http://tomcat.apache.org/tomcat-6.0-doc/config/http.html):(7) URIEncoding - Tomcat treats different parts of the request differently:- URL path using UTF-8 - URL query using ISO-8859-1 - request body using the specified encoding (see 2 and 5) Previous versions of Tomcat (4.1) used the body encoding also for the query string, but they fixed this (this is in accordance with thespecs). So, in order for request.getParameter to work fine, this settingmust be specified. (8) useBodyEncodingForURI - see above, this makes tomcat use the body encoding also for the query string. Either (7) or (8) should be set. (9) For Jetty, -Dorg.mortbay.util.URI.charset=UTF-8 can influence the encoding used for parsing the query string. The difference is that by default they use UTF-8 in recent versions. --
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
