Marco a écrit : > > I just recognized that the default encoding for CPS sites is iso-8859-15. I > thought it would be utf8. Does that mean that the site has problems with > flex docs, attachments, or member names having utf8 characters? >
It's just that CPS has been developed with Latin characters-only in mind. The CPS code base is able to deal with UTF8 characters just as well. It "just" requires some long hours to make the impacted code evolve. There are 2 problems if CPS 3.4 was to be switched to UTF8 : 1. do a total cleanup of everywhere iso-8859-15 is hardcoded and only use the unicode python object in the code 2. provide a migration path for all existing contents of portal The point 2. would be a pain to do. > Would it be save to change this property to utf8? I.e. would it break links > or some thing like that? > Simply changing this property would not be enough since there are many hardcoded iso-8859-15 setting in the code. > Which type of content would be necessary to convert? > All contents. Cheers, -- Marc-Aurèle DARCHE NUXEO (Paris, France) http://nuxeo.com/ Nuxeo Collaborative Portal Server (CPS) http://www.cps-project.org/ Gestion de contenu web / portail collaboratif / logiciel libre _______________________________________________ cps-users mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/cps-users
