On Jul 30, 8:31 pm, jeb <jo...@ibiz.se> wrote:
> I think it's more a question of how the data is stored in the
> database.
> In my layout i have:
> <meta http-equiv="content-type" content="text/html;charset=UTF-8" />
> and in application.rb:
> config.encoding = "utf-8"
>
Also possible. If previously the database connection was configured as
some latin1 variant and your columns were also latin1 but you were
stuffing utf8 data into them then switching to mysql2 would cause data
to appear messed up.
Fred
> :-) j
>
> On 30 Juli, 20:15, Frederick Cheung <frederick.che...@gmail.com>
> wrote:
>
>
>
> > On Jul 30, 7:00 pm, jeb <jo...@ibiz.se> wrote:
>
> > > When using the mysql2 gem with my excising databases all non-standard
> > > chars gets messed up:
>
> > > från is shown as från in the browser
>
> > > Is this possible to fix or do I have to continue using the old mysql-
> > > gem?
>
> > IIRC mysql2 forces use of utf8. If you're elsewhere telling the
> > browser that you're using a different character set then you'd get
> > unwanted results.
>
> > Fred
--
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
No comments:
Post a Comment