[Phpmyadmin-devel] charset tests (MySQL 4.0.16)
Hi devs, Testing with CREATE TABLE `testcharset` ( `prénom` varchar(30) NOT NULL default '' ) TYPE=MyISAM; INSERT INTO `testcharset` VALUES ('Josée'); =================== I start the test with this configuration, then I mention what I change and the results. Latest CVS, MySQL 4.0.16, PHP 4.3.4, mysql ext, AllowAnywhereRecoding=TRUE, language en-utf-8, mysql-charset: iso-8859-1 Structure: ok Browse: data ok, column title broken SQL: fields list ok Search: ok Insert: ok Export: ok ------------------ Switching Language to en-iso-8859-1: Structure: ok Browse: data ok, column title ok SQL: fields list ok Search: ok Insert: ok Export: ok ----------------- Switching to AllowAnywhereRecoding=FALSE: All is ok ----------------- Switching Language to en-iso-utf-8: Structure: column name broken Browse: data broken, column title broken SQL: fields list broken Search: fields list broken Insert: fields list broken Export: data broken, column name broken ------------------ Marc
Hi Marc On 15.04.2004 13:16 -0400, Marc Delisle wrote:
Latest CVS, MySQL 4.0.16, PHP 4.3.4, mysql ext, AllowAnywhereRecoding=TRUE, language en-utf-8, mysql-charset: iso-8859-1
Structure: ok Browse: data ok, column title broken
Text gotten from parsed query is not converted, I'm going to fix this. [...]
Switching to AllowAnywhereRecoding=FALSE:
All is ok ----------------- Switching Language to en-iso-utf-8:
Structure: column name broken Browse: data broken, column title broken SQL: fields list broken Search: fields list broken Insert: fields list broken Export: data broken, column name broken
No conversion at all => It has to be broken as you're using different charset that MySQL uses. Choose some translation with iso-8859-2 and it will be also "broken". -- Regards Michal Čihař http://cihar.com
Michal Čihař a écrit:
Hi Marc
On 15.04.2004 13:16 -0400, Marc Delisle wrote:
Latest CVS, MySQL 4.0.16, PHP 4.3.4, mysql ext, AllowAnywhereRecoding=TRUE, language en-utf-8, mysql-charset: iso-8859-1
Structure: ok Browse: data ok, column title broken
Text gotten from parsed query is not converted, I'm going to fix this.
Great!
[...]
Switching to AllowAnywhereRecoding=FALSE:
All is ok ----------------- Switching Language to en-iso-utf-8:
Structure: column name broken Browse: data broken, column title broken SQL: fields list broken Search: fields list broken Insert: fields list broken Export: data broken, column name broken
No conversion at all => It has to be broken as you're using different charset that MySQL uses. Choose some translation with iso-8859-2 and it will be also "broken".
Yes I expected this. But since AllowAnywhereRecoding is FALSE by default in the distribution kit, we might need a FAQ entry about the effects of switching Language. Marc
Oh, nice, thank you very much Michal! Marc, have you always the problem now? If not, we haven't to test other configurations, right? Marcel
Michal ÄihaÅ a écrit:
Hi Marc
On 15.04.2004 13:16 -0400, Marc Delisle wrote:
Latest CVS, MySQL 4.0.16, PHP 4.3.4, mysql ext, AllowAnywhereRecoding=TRUE, language en-utf-8, mysql-charset: iso-8859-1
Structure: ok Browse: data ok, column title broken
Text gotten from parsed query is not converted, I'm going to fix this.
Great!
[...]
Switching to AllowAnywhereRecoding=FALSE:
All is ok ----------------- Switching Language to en-iso-utf-8:
Structure: column name broken Browse: data broken, column title broken SQL: fields list broken Search: fields list broken Insert: fields list broken Export: data broken, column name broken
No conversion at all => It has to be broken as you're using different charset that MySQL uses. Choose some translation with iso-8859-2 and it will be also "broken".
Yes I expected this. But since AllowAnywhereRecoding is FALSE by default in the distribution kit, we might need a FAQ entry about the effects of switching Language.
Marc
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op ick _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Marcel Tschopp a écrit:
Oh, nice, thank you very much Michal! Marc, have you always the problem now? If not, we haven't to test other configurations, right?
Fix confirmed, thanks Michal! Marc
Marcel
Michal Čihař a écrit:
Hi Marc
On 15.04.2004 13:16 -0400, Marc Delisle wrote:
Latest CVS, MySQL 4.0.16, PHP 4.3.4, mysql ext, AllowAnywhereRecoding=TRUE, language en-utf-8, mysql-charset: iso-8859-1
Structure: ok Browse: data ok, column title broken
Text gotten from parsed query is not converted, I'm going to fix this.
Great!
[...]
Switching to AllowAnywhereRecoding=FALSE:
All is ok ----------------- Switching Language to en-iso-utf-8:
Structure: column name broken Browse: data broken, column title broken SQL: fields list broken Search: fields list broken Insert: fields list broken Export: data broken, column name broken
No conversion at all => It has to be broken as you're using different charset that MySQL uses. Choose some translation with iso-8859-2 and it will be also "broken".
Yes I expected this. But since AllowAnywhereRecoding is FALSE by default in the distribution kit, we might need a FAQ entry about the effects of switching Language.
Marc
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op ick _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
On 15.04.2004 13:32 -0400, Marc Delisle wrote:
Michal Čihař a écrit:
Hi Marc
On 15.04.2004 13:16 -0400, Marc Delisle wrote:
Latest CVS, MySQL 4.0.16, PHP 4.3.4, mysql ext, AllowAnywhereRecoding=TRUE, language en-utf-8, mysql-charset: iso-8859-1
Structure: ok Browse: data ok, column title broken
Text gotten from parsed query is not converted, I'm going to fix this.
Great!
In CVS...
No conversion at all => It has to be broken as you're using different charset that MySQL uses. Choose some translation with iso-8859-2 and it will be also "broken".
Yes I expected this. But since AllowAnywhereRecoding is FALSE by default in the distribution kit, we might need a FAQ entry about the effects of switching Language.
That the way it works all the time and nobody complained :-). The new is only that you can select utf-8 translation without charset conversion enabled. -- Regards Michal Čihař http://cihar.com
Michal Čihař a écrit:
On 15.04.2004 13:32 -0400, Marc Delisle wrote:
Michal Čihař a écrit:
Hi Marc
On 15.04.2004 13:16 -0400, Marc Delisle wrote:
Latest CVS, MySQL 4.0.16, PHP 4.3.4, mysql ext, AllowAnywhereRecoding=TRUE, language en-utf-8, mysql-charset: iso-8859-1
Structure: ok Browse: data ok, column title broken
Text gotten from parsed query is not converted, I'm going to fix this.
Great!
In CVS...
Hmmm, pretty printing is now broken when I paste this: CREATE TABLE `testcharset` ( `prénom` varchar(30) NOT NULL default '' ) TYPE=MyISAM; I can't even run this command from the query box! However it works if I remove the "é". Marc
No conversion at all => It has to be broken as you're using different charset that MySQL uses. Choose some translation with iso-8859-2 and it will be also "broken".
Yes I expected this. But since AllowAnywhereRecoding is FALSE by default in the distribution kit, we might need a FAQ entry about the effects of switching Language.
That the way it works all the time and nobody complained :-). The new is only that you can select utf-8 translation without charset conversion enabled.
On 15.04.2004 13:55 -0400, Marc Delisle wrote:
Hmmm, pretty printing is now broken when I paste this:
CREATE TABLE `testcharset` ( `prénom` varchar(30) NOT NULL default '' ) TYPE=MyISAM;
I can't even run this command from the query box!
However it works if I remove the "é".
I couldn't break this thing :-), I just modified libraries/display_tbl.lib.php to convert column name when displaying... -- Regards Michal Čihař http://cihar.com
Michal Čihař a écrit:
On 15.04.2004 13:55 -0400, Marc Delisle wrote:
Hmmm, pretty printing is now broken when I paste this:
CREATE TABLE `testcharset` ( `prénom` varchar(30) NOT NULL default '' ) TYPE=MyISAM;
I can't even run this command from the query box!
However it works if I remove the "é".
I couldn't break this thing :-), I just modified libraries/display_tbl.lib.php to convert column name when displaying...
Sorry Michal, It's not you. My test command containing a "é" is mangled by the parser when my Language is -utf-8. We have an old bug report about this, I think. Marc
participants (3)
-
Marc Delisle -
Marcel Tschopp -
Michal Čihař