I think I have found the problem:

Doing Select @@character_set_database , results, client and connection it
all returns
latin1

I tried set character_set_xxxxx = utf8;  for them all but it did not work,
they stayed latin1 and need to be utf8

Any ideas how to change this?

Thanks,
James


----- Original Message ----- 
From: "Gleb Paharenko" <[EMAIL PROTECTED]>
To: <mysql@lists.mysql.com>
Sent: Tuesday, August 16, 2005 11:16 AM
Subject: Re: French Characters, Still no answer


> Hello.
>
> > Also when we use EMS mysqlmanager to view the data, it is fine, it is
only
> > when it comes back to the tomcat server it seems.
>
> That means that data on the server is ok. Check the values of your
> character_set_client, character_set_connection and character_set_results
> variables from Tomcat's application. See:
>   http://dev.mysql.com/doc/mysql/en/charset-connection.html
>
>
> > If no one has anymore ideas I think our best route is to dump it,
install
> > 4.0 on this server and import it back in.
>
> Perform an import so that all fields in your table have an utf8 character
> set. And tune properly the connection variables.
>
>
> "James Sherwood" <[EMAIL PROTECTED]> wrote:
> > Sorry, dont know how I missed: http://lists.mysql.com/mysql/187794
> >
> > The old msql was 4.0 and the new one is 4.1.
> >
> > When we first imported the data the database was in latin1(my mistake)
and
> > we put it into production as everything seemed to work fine.
> >
> > We have one site that uses french characters sometimes and they
compained 1
> > week later.  By that time it was too late to roll back so now we have
this
> > problem.
> >
> > We tried converting the database over to Utf8 but it did not seem to
fully
> > work.
> >
> > We can put the french characters in, even from the tomcat server, but
when
> > they come back out to the webpage(we have a content management system)
they
> > are garbled.
> >
> > One night we did some testing and hooked the tomcat to the old database
and
> > everything worked fine with french characters so it has to be the new
> > database.
> >
> > If no one has anymore ideas I think our best route is to dump it,
install
> > 4.0 on this server and import it back in.
> >
> > Everything looks ok as far as Utf8 on the tables and such, I feel that
we
> > are just missing one key thing that is garbling the characters.
> >
> > Also when we use EMS mysqlmanager to view the data, it is fine, it is
only
> > when it comes back to the tomcat server it seems.
> >
> > Thanks for your ideas thus far,
> > James
> >
> >
>
>
> -- 
> For technical support contracts, goto https://order.mysql.com/?ref=ensita
> This email is sponsored by Ensita.NET http://www.ensita.net/
>    __  ___     ___ ____  __
>   /  |/  /_ __/ __/ __ \/ /    Gleb Paharenko
>  / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
> /_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
>        <___/   www.mysql.com
>
>
>
>
> -- 
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
>
>



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to