Frederick Cheung wrote: > On 11 Sep 2008, at 16:37, Aa Wilson wrote: > >> the gist of things: >> production environment (in which case, everything comes out exactly as >> compensate for whatever is giving this wonky output. As it is, we're >> pretty stumped. >> > > Could be what your terminal is set to dispay, eg if the terminal on > the production machine is set ti displaying stuff in ISO-Latin-1 and > the underlying data is too but everyone else is expecting the data to > be utf-8 then you might get what you observe. I'd check if the > database encoding setting (in database.yml) matches what the database > is doing and that any headers on the actual page saying what the > content-type/charset are also match that. > > Fred
It turned out to be a setting in our freetds.conf (client charset=utf8) that was missing. It took us forever to find out that was the case, because the damn production console behavior was throwing us off, so we worked our way through the entire chain before we eliminated everything but tds. Thanks for your response! -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
