8 Apr
2007
8 Apr
'07
10:56 p.m.
On 4/8/07, Zeljko Trogrlic <zeljko_t(a)post.htnet.hr> wrote:
Vincent Massol wrote:
Because we can't change the way the server starts, given the fact that there
are dozens of containers and platforms.
--
http://purl.org/net/sergiu
On Apr 7, 2007, at 8:00 PM, Zeljko Trogrlic wrote:
Of course, bur Java already has file.encoding. Why another property?
Vincent Massol wrote:
xwiki.encoding already exists. The point here is to make platform =
xwiki encoding = database driver encoding = web encoding = all encoding
used everywhere, all this without the user having to change 7 places... Exactly which is why this is best left to the
user to decide which
encoding they need to use... I don't think we should force our
encoding. However I'm proposing that we do:
System.setProperty("file.encoding", getParam("xwiki.encoding")) in
XWiki initialization to set the platform encoding to be the encoding
specified in xwiki.cfg.
I think it should be vice-versa. Stick to platform or use UTF-8 don't
add new encoding parameter.