Say one can successfully see the UTF-8 in an SQL dump with $ mysqldump --default-character-set=latin1 my_database | less
OK, now how about browsing with phpmyadmin? no matter what I set, browser charset or various phpmyadmin choices, fields like 'ar_title varchar(255) latin1_bin' come out as mess.
I just want to browse them, not change or 'injure' them.
(That is the varchars, phpmyadmin won't let me browse the blobs.)
On Sat, Mar 14, 2009 at 2:02 AM, jidanni@jidanni.org wrote:
Say one can successfully see the UTF-8 in an SQL dump with $ mysqldump --default-character-set=latin1 my_database | less
OK, now how about browsing with phpmyadmin? no matter what I set, browser charset or various phpmyadmin choices, fields like 'ar_title varchar(255) latin1_bin' come out as mess.
I just want to browse them, not change or 'injure' them.
(That is the varchars, phpmyadmin won't let me browse the blobs.)
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Maybe try asking the phpMyAdmin support? This has nothing to do with MW specifically.
-Chad
Chad schrieb:
On Sat, Mar 14, 2009 at 2:02 AM, jidanni@jidanni.org wrote:
Say one can successfully see the UTF-8 in an SQL dump with $ mysqldump --default-character-set=latin1 my_database | less
OK, now how about browsing with phpmyadmin? no matter what I set, browser charset or various phpmyadmin choices, fields like 'ar_title varchar(255) latin1_bin' come out as mess.
I just want to browse them, not change or 'injure' them.
(That is the varchars, phpmyadmin won't let me browse the blobs.)
Well, it has to do with the fact that MW declared fields to be latin1 and then fills them with utf8. I don't know if there is a way to tell phpmyadmin to ignore the charset info the database is providing.
-- daniel
wikitech-l@lists.wikimedia.org