General Actions:
Below you have the configuration for UTF-8. Note that this is valid for XWiki 1.0 b5 and above. Easier configuration might be provided for upcoming releases.
Change the charset enconding in these XWiki files:
Change the HTML encoding in XWiki through Administration --> Preferences --> Presentation --> HTTP Meta information.
Inside this textbox locate the Content-type meta tag and make it look like this, changing the encoding to UTF-8
Add the following lines in the hibernate.cfg.xml file:
It's common practice that the MySQL configuration file, in *nix systems is located in $$/etc/mysql/my.cnf:
Instead of the config system variable LANG you can use JVM properties.
in server startup script.
In order to enable UTF-8 in tomcat, you have to add
to each connector enabled/used in conf/server.xml. For example the non-SSL HTTP Connector should read:
To run XWiki with UTF-8 in Glassfish you will need to recreate the xwiki-enterprise.war file and do a change to the glassfish config. First, in the Administration GUI under Domain => General => Locale enter en_US.UTF-8.
Now you will need to add all the aforementioned changes from this document to the files in the war file, create a new warfile, and deploy that one to your glassfish installation. This is required due to the fact that Glassfish will not accept changes to a deployed web.xml file. So you need to deploy a ready changed web.xml file inside your war file because all subsequent changes to the deployed web.xml file in the filesystem are totally ignored.
Create a new directory that we will use as a temporary place to edit our war file:
Unpack the warfile:
Edit the files as mentioned in the beginning of this article:
Now let's create a new warfile which contains all the changes:
Now you can deploy your new .war file to Glassfish and it will have all the changes in it and wll be correctly deployed.
Add the following variables to your system:
If OpenOffice import turns characters into question marks or HTML Entity you need to edit registrymodifications.xcu located in user profile used by the OO server by adding: