UserFriendly - 3:54 am on Jul 16, 2010 (gmt 0)
So you think it is simply the case that the data was inserted over a connection declaring the wrong encoding?
If so, at least you've uncovered the cause of the strangeness.
As for re-encoding the existing data, there's probably a way of doing that automatically if you work out in which encoding it was sent to the database. But that's a whole other can of worms, and probably only worth the hassle if you have hundreds or thousands of records to fix.