-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mashiah Davidson: > Much better than zws. No issues with database strings encoding, compare: > http://wolfsbane.toolserver.org:81/~lvova/cgi-bin/go.sh?language=ru&interface=en&listby=zns > http://toolserver.org/~lvova/cgi-bin/go.sh?language=ru&interface=en&listby=zns
This is not an innate difference between the two, but some kind of configuration difference. I was looking at your encoding problem earlier; the most likely possibility seemed to be that after the MySQL 5.5 upgrade, the default client character set changed to UTF-8, which broke some tools. I've changed that back to latin1 to restore the old behaviour, but it didn't fix your problem. Looking at the difference in environment between the two: <http://wolfsbane.toolserver.org:81/~river/env.cgi> <http://toolserver.org/~river/env.cgi> ... the most obvious difference is that Apache doesn't set LANG=en_US.UTF-8. This doesn't seem to affect the MySQL client, though: river@wolfsbane:~$ LANG= sql enwiki_p ... Server characterset: latin1 Db characterset: latin1 Client characterset: latin1 Conn. characterset: latin1 river@wolfsbane:~$ LANG=en_US.UTF-8 sql enwiki_p ... Server characterset: latin1 Db characterset: latin1 Client characterset: latin1 Conn. characterset: latin1 If you could add the output of SHOW VARIABLES LIKE '%character_set%'; to the script, and see if there's a difference between them, it would help track down the problem. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (SunOS) iEYEARECAAYFAk3/sGoACgkQIXd7fCuc5vKi1gCgtXLmDP7Q6HSNv+q5tsH6fx/9 8zYAnjE1kHL4mctgrCTvYbfsPiccaI5B =1WLY -----END PGP SIGNATURE----- _______________________________________________ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
