OK, sorry for not saying this clearly.
I'll give you phpbb2 as an example of translations using php (associative arrays). Drupal for example uses gettext, which I favour, too.
$lang = array_merge($lang, array(
'ADMIN_CONFIG' => 'Administrator-Konfiguration',
'ADMIN_PASSWORD' => 'Administrator-Passwort',
'ADMIN_PASSWORD_CONFIRM' => 'Bestätigung des Administrator-Passworts',
[...]
message_die(GENERAL_MESSAGE, $lang['No_posts_topic']);
I would like to propose a system similar to the following:
We collect all the strings which are necessary in a template and use them for the localisation with amuleweb. It is possible to scan the template files directly for strings to translate with xgettext, so this is an automated task.
The actual translation task will be done by our translation team (after automatically merging as many strings as possible, a small duplication is imho not avoidable) just like it is done with the main application. This is important because our translators already know how to use po files.
To actually use translated strings in a template, we need an interface between the gettext functions in C and the amuleweb PHP language. (
http://www.gnu.org/software/gettext/manual/gettext.html#Language-Implementors) Important are the functions GonoszTopi mentioned (normal messages and plural messages) and the function to set the currently used locale.
What do you think?
iz0bbz: We will not abandon other ways of controlling aMule remotely, but *I* would like to focus my current work on the web interface.