16 Dec
2005
16 Dec
'05
12:55 p.m.
Michal Čihař a écrit :
Hi
On Tue, 13 Dec 2005 12:59:58 -0500
Marc Delisle <Marc.Delisle(a)cegepsherbrooke.qc.ca> wrote:
Ok, the bug comes from libraries/url_generating.lib.php, line 79.
Previous version used htmlspecialchars(), now it's htmlentities().
Can't we go back htmlspecialchars?
Marc
can you reproduce this? I create a table named
école and after the
CREATE TABLE, the name is corrupted (the name is internally encoded in
UTF-8 by MySQL 4.1.x but it's not properly decoded when displayed in PMA).
Then I can no longer work with the table (insert, search, etc).
Same problem happens when connecting to a MySQL 4.0.x or 5.0.x server.
This must be caused by a recent change in HEAD.
I can reproduce this, however I have no idea what could cause this.
More what I noticed: such badly encoded table is going to be messed
even more later, so I guess we do some conversion twice.
Create table zkouška, it becomes zkouÅ¡ka. Go to export, click Go and
now you have zkou�¡ka (and html instead of dump in textarea).