Again on WP migration.
My previous 2.0.11 installation was having DB collation and Character Set configured as latin1 (by default with WordPress 2.0.x).
Bad thing happened when I exported my sql db and reimported in new 2.3.1 installation (defaulting at UTF-8) and saw all accented characters displayed as question marks, ugly signs, etc. ð
I also tried exporting as UTF-8 in WP 2.0, but soon realized that WP 2.0.x does not include support for UTF-8 Character Set.
Found a solution in a blog, and reporting it here to avoid spending again two days in future Googling… and testing. Continue reading »