Sorry to hassle with that, but there seems to be a UTF-8 encoding bug using the DataObjectManager and the latest trunk release of SilverStripe. This wasn't happening before.
I need the latest trunk release because I need translations. Since the latest trunk release is more stable than the beta release, I have no choice but using it. Why SS aren't releasing a stable 2.3.2 release? I donnu.
But here's the bug. Maybe there's a quick fix. I hope so :
Looking at the forum, SilverStripe's team claim that they handle UTF-8 caracters. All data is coded in UTF-8 values. So, if I have a page with accents in any text fields, it'll encode properly. Even though phpMyAdmin won't show correctly the accents, in the CMS and in the Live site, the accents show correctly.
If I use your DataObjectModule, I can enter UTF-8 caracters. They show well in the popup. But in the list, and in the live site, they don't show correctly. If I open the popup (edit the record) again, the accent shows well, but in the list, they don't. And one more wierd thing : if I look the record, in PhpMyAdmin, the accents show correctly (the normal behavior is they don't show correctly... because SS doesn't use MySQL directive SET CHARSET = 'utf-8').
I would like to send you a picture. But the forum doesn't allow me.