[Phpmyadmin-devel] problems with charsets?

[Michal Čihař]

On 15.04.2004 23:05 +0200, Alexander M. Turek wrote:
> 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.

Exactly.

> 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.

Shouldn't we with MySQL 4.1 offer just unicode translations? 

-- 
Regards
	Michal Čihař
	http://cihar.com