Since today phpMyAdmin allows using other charset in HTTP and when working
with mysql. This requires translations to use some charset that won't break
anything during conversion. Currently will be used utf-8 so translations
should be converted to this charset, while also keeping current one to allow
working in some browsers (are there any?) which don't support utf-8.
Majority of these conversion can be done automatically with script I wrote,
but I need you to check if there didn't occur any problem. This script can do
also conversion between charsets being used in one translation (for example
czech translation had till now two version, one in windows-1250 and one in
There are also some "problematical" translations which will require
translators co-operation. These are:
georgian (because of x-user-defined charset is not supported by iconv)
hebrew (because of iso-8859-8-i charset is not supported by iconv)
korean (because of ks_c_5601-1987 charset is not supported by iconv)
slovak (because there are two a bit different translations maintained by two
people and now only one of them is needed, other will be generated
automatically, so I need to know which one will be maintained)
chinesse (there are two translations - chinese_big5 and chinese_gb - and I
really don't know whether to handle them as two separate translations or just
as one in different charsets)
I converted current cvs version to utf-8 (where it worked) and the result is
available at http://cihar.liten.cz/PMA-translations/. There is also script
which does this conversion (sync_lang.sh). So please have a look at your
converted translation and send me your comments.
nijel at users dot sourceforge dot net
I've received some notices, that there are some
unwanted \r\n characters after ?> in lithuanian.inc.php
so PMA outputs a message "Headers already sent".
I've corrected this bug. Please merge it ASAP.
Finally, strNotSet has a second parameter which contains the name of the
$strNotSet = '<b>%s</b> table not found or not set in %s';
and this one is also to translate:
$strConfigFileError = 'phpMyAdmin was unable to read your configuration
file!<br />This might happen if php finds a parse error in it or php
cannot find the file.<br />Please call the configuration file directly
using the link below and read the php error message(s) that you recieve.
In most cases a quote or a semicolon is missing somewhere.<br />If you
recieve a blank page, everything is fine.';
those will probably be the last messages to translate for 2.3.0,
as Release Candidate 1 will be released in a few days.
$strMissingBracket = 'Missing Bracket';
$strHaveToShow = 'You have to choose at least one Column to display';
$strCantLoadRecodeIconv = 'Can not load iconv or recode extension needed
for charset conversion, configure php to allow using these extensions or
charset conversion in phpMyAdmin.';
$strCantUseRecodeIconv = 'Can not use iconv nor libiconv nor recode_string
function while extension reports to be loaded. Check your php
$strMySQLCharset = 'MySQL Charset';
$strComments = 'Comments';
I don't want to set $cfg['DefaultCharset'] statically in config.inc.php3.
Because we can't select the charset to each MySQL server with different charset.
This feature is not good, I think.