Re: Still upgrading to Tiger, MySQL accentuated characters issue
Re: Still upgrading to Tiger, MySQL accentuated characters issue
- Subject: Re: Still upgrading to Tiger, MySQL accentuated characters issue
- From: Dev WO <email@hidden>
- Date: Sun, 7 Aug 2005 16:27:00 +0200
OK, after reading the connector/J documentation, I was able to find a
temporary fix:
in the connection dictionary, instead of using:
useUnicode=true&characterEncoding=utf8
I did
useOldUTF8Behavior=truecharacterEncoding=utf8
and now it's working.
But I really don't want to trick like this as the database now
support UTF8 so I shouldn't need to add abything to the connection
dictionary? am I correct on this?
And anyone knows how to get a final fix?
Thanks:)
Xavier
Am Sonntag, 7. August 2005 15:35 schrieb Dev WO:
Hi Michael,
I have
AddCharset UTF-8 .utf8
No, unless .utf8 is the extension of your files that are presented
by the
webserver. I'm not sure, but .php would be fine. From the Apache
manual:
AddCharset Directive
Description: Maps the given filename extensions to the
specified content
charset
Syntax: AddCharset charset extension [extension] ...
Context: server config, virtual host, directory, .htaccess
Don't forget to reload your server config. You may use the line in
a .htaccess-file, so it won't bother other websites.
WebObjects applications don't "usually" provide .html files, that's
why I'm not sure it will correct the issue. But I'll try that in a
minute.
If this does not work, please see the phpmyadmin manual. I think your
MySQL-setup is correct, sinve you're able to see the right values
with your
desktop applications, aren't you?
In fact I did a mistake, no client MySQL application display the
data correctly (I tried Cocoa MySQL and YourSQL), Cocoa MySQL
display the BLOB data correctly, but not the varchar and other.
OTOH, it could be possible that you declared utf-8 in MySQL, but your
application uses MacOSEncoding, resulting in garbage. You could
analyze the
packets with a network sniffer to see what's transmitted...
The application uses UTF-8, and talked to the database using
"useUnicode=true&characterEncoding=utf8" and it was working prior
to the upgrade.
What make me think it's a MySQL issue is that v4.0.xx wasn't
supposed to handle UTF-8, so we trick it using
"useUnicode=true&characterEncoding=utf8", but now it should handle
that correctly but I probably have to change something... but what:)
HTH, Michael.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40anazys.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40anazys.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden