[Phpmyadmin-devel] charset tests (MySQL 4.0.16)
Marc Delisle
DelislMa at CollegeSherbrooke.qc.ca
Thu Apr 15 11:26:41 CEST 2004
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 at lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
>
>
>
More information about the Developers
mailing list