[Phpmyadmin-devel] problems with charsets?

Alexander M. Turek alexander.turek at stud.uni-karlsruhe.de
Thu Apr 15 14:22:22 CEST 2004


Hi there,

Marcel Tschopp wrote:
> 
> You can test it as following:
> In UTF8 mode (eg: en-utf-8) create a new field 'tést' on a 
> table. Then switch to an ISO mode (eg: en-iso-8859-1) and 
> look at the table structure. Now the character 'é' has been 
> replaced...
> 
> Anyone knows how to solve the problem?

Use MySQL 4.1 :-)

MySQL 4.0 / 3.x does not have multi-charset support afaik.
So if you access a MySQL 4.0 server with PMA using a language file encoded
with charset XY, everything is sent in XY because the user agent sends it in
XY.

MySQL expoects all clients to use the same charset. Using clients with
different charsets results in such problems as long as the clients are not
recoding the users' inputs.

This is why Michal initially created the recoding functionality: The
interface charset could be independant from the db charset.

When using MySQL 4.1 we leave all recoding and just tell the MySQL server
that we are using the charset XY. The rest is up to MySQL.

Regards,

-- 

Alexander M. Turek
<rabus at users.sourceforge.net>

       _           __  __          _       _           _
 _ __ | |__  _ __ |  \/  |_   _   / \   __| |_ __ ___ (_)_ __
| '_ \| '_ \| '_ \| |\/| | | | | / _ \ / _` | '_ ` _ \| | '_ \
| |_) | | | | |_) | |  | | |_| |/ ___ \ (_| | | | | | | | | | |
| .__/|_| |_| .__/|_|  |_|\__, /_/   \_\__,_|_| |_| |_|_|_| |_|
|_|         |_|           |___/ 
                                    <http://www.phpmyadmin.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 2242 bytes
Desc: not available
URL: <http://lists.phpmyadmin.net/pipermail/developers/attachments/20040415/8cd41c1e/attachment.bin>


More information about the Developers mailing list