Hello St�phane, > So is this coming only for migrated data or also for new 4.0.5 data? We currently only have tested our specific configuration with migrated data on MySQL.
> Is this happening only for big texts (stored on the file system) or also for > small texts (stored directly in the database)? Only 100% sure regarding bigtext really. We'll test this tomorrow though. > Do you see the umlauts in > the WYSIWYG Editors when loading the data or is it already wrong here (or > only wrong when saving the data)? Display of migrated data is fine. Webpages are served as UTF-8. The data gets corrupt when you save/update the data. This is why I'm thinking it's a tidy issue or has at least something to do with how tidy is used. > Are you sure your old big texts are still > in UTF-8 format (if you, for example, reinstall the old data on a new > server by zipping/tar.gzing the old data perhaps you this process converted > your text files back in ISO format)? We'll test this. But this wouldn't explain why neither value for tidy works... > Are you sure that your linux config > (etc/sysconfig/i18n) is correct? I'm pretty sure, since we use several webapps (self developed) that use UTF-8 data. They work fine. This is also why I'm thinking that our backups kept UTF-8 encoding. If not, we would have the same problem with them. But I'll crosscheck this. > Finally if everything seems correct, could send us an exemple of big text > with an umlaut and where the error occurs such as: > E:\jahia405\tomcat\webapps\jahia\WEB-INF\var\content\bigtext\1-2-20-de.jahia I would be happy to. I'll send it the next business day to you. Cheers Daniel
