I've added the container-encoding (ISO-8859-1) and form-encoding (UTF8 withouth dash) and my special characters are saved. I also changed the exml serializer back to its original value, and that is still not good. If I create a document, the first line says encoding="UTF-8", but after I save it, the first line changes to encoding="ISO-8859-1".
We are using the xopus editor. Could it be that the editor is calling the wrong method on the CMS and thus the exml serializer is used instead of the normal serializer? If so, where can I change that? With regards, Nick Stolwijk -----Original Message----- From: [EMAIL PROTECTED] on behalf of Ard Schrijvers Sent: Mon 3/3/2008 14:24 To: Hippo CMS development public mailinglist Subject: RE: [HippoCMS-dev] Hippo CMS and encoding Hello Nick, my guess is (anybody else?) that there is a good reason for the ISO-8859-1 encoding. It is only used for some serializers (default is xml, the ISO-8859-1 is for exml). I am quite certain that you should not change it. Are you running in tomcat (which version) or jetty? You might have to add the form-encoding to the web.xml. It must be utf8 there (not utf-8) : --------------------------------------------------- Issue: Special characters when editing documents in cms. Reason: special characters in documents were not being saved in the good format.So when the documents were published, the user sees a lot of weird signs on the product page. Cause: this is because when moving to tomcat, tomcat uses the specs for the configuration of container-encoding, which was not the case in jetty. Solution: change the container-encoding in the web.xml of the cms: <init-param> <param-name>container-encoding</param-name> <param-value>ISO-8859-1</param-value> </init-param> <init-param> <param-name>form-encoding</param-name> <param-value>UTF-8</param-value> </init-param> --------------------------------------------------- Hope this helps. You really should not have to change code in the cms! I would recommend to revert your changes -Ard > Changing the serializer to UTF-8 solved at least our problem > with saving documents as the wrong encoding. It did not solve > our ability to insert special characters like é. We are now > looking where it goes wrong. Does any of you have seen this before? > > We are working on CMS 6.05.01, repository 1.2.13 and oracle > jdbc as backend for the repository. > > With regards, > > Nick Stolwijk > > > -----Original Message----- > From: [EMAIL PROTECTED] on behalf of > [EMAIL PROTECTED] > Sent: Mon 3/3/2008 12:32 > To: [email protected] > Subject: [HippoCMS-dev] Hippo CMS and encoding > > > We are having some issues with the Hippo CMS and encoding. We > are saving our documents with UTF-8, but now we noticed in > editor/src/site/actions/sitemap.xmap that they are encoded as > ISO-8859-1. Is it safe to adjust this serializer to use UTF-8 > as encoding? > > With regards, > > Nick Stolwijk > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
