Hi everybody,
I’ve been scouring the forums, but haven’t found anything with quite this kind of encoding issue. We’ve got a site in English that we’re translating to Spanish as well. I dumped the database to our translation bureau, who returned to me a SQL update file with only the Spanish parts, and all that data seems to import just fine into all the right places (custom fields, etc) in the database.
When I look at the Spanish data through Sequel Pro (I’m on a Mac) all the accents and such seem to appear correctly in the body_es custom field (a Wygwam field),and in the title_es custom field (simp text field). In the control panel, the body_es still looks fine, but the title_es displays the “special” characters appear as white question marks in black diamonds.
At this point, if I view the site, any Spanish characters appear corrupted (even the body_es ones that look good in CP), unless I force the browser to use Western (ISO Latin 1) encoding which makes everything display correctly. The weird thing is that if I simply save the entry without making any edits at all, then all the data still looks exactly the same in the Control Panel as it did before, but the site starts to display correctly under the default encoding (UTF-8) and no longer looks right under forced Western Latin; except the “corrupted” titles retain their questions marks in CP and on the site.
It’s almost as if the SQL import is bringing everything into the database correctly, but ExpressionEngine doesn’t recognize it as UTF-8 until I save the entry, but saving every entry individually isn’t really an option, clearly…
As far as I can tell, I did my best from the beginning of the project to make everything UTF-8 the whole way through. The SQL dump has default encoding UTF-8 for all tables, and it seems still to be that watt after the import.
It’s a 1.6.9 install with mySQL 5.1.0. Any other data tat might be helpful?
Anyone has any ideas what might be going on?
Thank you so much,
Willhaus