Encoding setting

Encoding of characters are one of the most important aspects of a global content management system. InfoGlue supports Unicode and suggests that UTF-8 is used as the default charset.

It’s important to understand how InfoGlue works when receiving data from forms etc both in deliver mode and in the tools. It is also important to understand the issues caused by Apache Tomcat and some other application servers and browsers. The fact is that many appservers and browsers do not behave correctly when sending/receiving data. The browsers sometimes does not send which encoding the data is coming in and Apache Tomcat for example therefore does not decode it correctly. This is a known issue and the solution is to use a servlet filter which sets the encoding in the request object before InfoGlue gets it.

We use this technique both in the cms and deliver applications and the filter (SetCharacterEncoding) is defined in the web.xml. If you’re having problems with the wrong encoding coming in you may want to try to set a different encoding in that file than the default UTF-8.

Outgoing encoding is totally managed in the management tool under languages. There you set what charset to use when presenting data to the users browser. We suggest using utf-8 as much as possible.

NiceURI effects:

If you have turned on NiceURI – you may want to change the filter SetCharacterEncoding to use a different match in web.xml as there are no longer any action in the url. Set it to “/*” instead of “.action”. Otherwise get/posts to the deliver engine may not turn up rightly encoded.

comments powered by Disqus