On Sep 14, 11:56 am, michael_teter <[email protected]> wrote: > Bummer, this didn't work for me. I think I'm having a similar problem. > > I was using mysql gem, database was utf8, but I was getting an occasional > template encoding error. That prompted me to update my driver to mysql2 > (which solved my template problem), but resulted in formerly "correct" > characters getting botched. > > Björn became Björn. Or maybe it always was that, but mysql driver was > somehow presenting it as we want to see it. Regardless, going to mysql2 > left me with a lot of screwed up names :( > > I also tried the column -> blob -> text trick, and sadly that didn't appear > to change anything. >
I once had a case where through an accident of history, some data was doubly bad, so I had to go through the text->blob->text approach multiple times F6 is actually a latin1 code point, which suggests that you still haven't got things in utf8 properly Fred > Do you think there's some simple algorithm I can use to map screwy things to > their correct versions? > > Thanks! -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
