codestyling

There was a download issue if the provider doesn’t permit the connection to other servers from domain space. In this case it’s not possible to check the svn repo for languages. the code detected the issue but failed to display the error for and died at scripting.
This has been solved with version 1.3.7 and will show now the error reason correctly.
Furthermore you can select now other versions of WordPress for language files, if you are able to check svn. In some cases higher version doesn’t get updated as quick as possible by translation teams, so you can use now the language files from lower version until higher versions provide them.

This has been changed with version 1.3.7 and support for all WordPress versions equal or higher than 3.0 the admin bar quick switcher only. The header switcher is only available for lower versions, where WordPress still have this backend header.

Languages at WordPress are not only releated to the speaking itself, they are related to the countries as well. So you have as example at spain small differences between countries. Thatswhy spainish is defined per country as examples:

es_AR -> Español/Argentina
es_BO -> Español/Bolivia
es_CL -> Español/Chile
....
es_ES -> Español/España
....

and catalan at spain is described as

ca_ES -> Сatalà/Espanya

So flags are usefull to separate it to be sure to have the correct modification per country. If you are using only short appreviations for languages (as some multi language plugins prefere but doing wrong), then you will get the wrong results. But this is the nature of your shortening and is not a problem of correct language/country handling.

Sorry, i can’t find an official description about the locale definition of “am_MA” I only found “ar_MA” for Morocco.
Could you point me to an official definition of such a locale, so I can handle it.

Files created with the plugin doesn’t do disappear. If you create the translation base (*.po) and it pops up inside the list of available translations, than it will be found always there. If afetr creation the file doesn’t show up at list, the server configuration is somehow not standard.

if it worked yesterday but missing today, do you have any cleanup or monitoring tool removing any files on some cirumstances?
Do you have other plugins installed dealing with languages (like multi language plugins, backup or routing things)?

Its difficult to say, what went wrong without the physical access to the affected machine for investigation. Locally I can’t reproduce the issue. If it would be an option to permit access to the affected machine, please let me know by mail (can be found at my imprint page).

This plugin load the textdomains the none standard way and is not compatible as expected:

if ($this->current_lang && $this->current_lang != $this->options['forum_lang']) {
	$plugin_dir = basename(dirname(__FILE__));
	$lang_dir = ABSPATH.'wp-content/plugins/forum-server/languages/';

	if (file_exists($lang_dir.'vasthtml_'.$this->current_lang.'.mo')) {
		load_textdomain("vasthtml", $lang_dir.'vasthtml_'.$this->current_lang.'.mo');
		// global wordpress translate method with wp-config.php WPLANG
		//load_textdomain("vasthtml", $lang_dir.'vasthtml_'.$this->current_lang);
	} else {
		die('Language (.mo) file doesn\'t exist or accessible');
	}
}

Normally it should never call die if the translation file is missing, nor it should explicitly load it with gerneric version of load method.

The prefered way loading the textdomain for this plugin should be:

load_plugin_textdomain("vasthtml", PLUGINDIR.'/forum-server/languages', 'forum-server/languages');

This is strongly bound the the blogs language. If the Forum has their own lang management, there are quiet better ways to do this.

My plugin will generate a translation file (and did it at my local install) like: “vasthtml-hu_HU.po” and is able to translate and generate the appropriated *.mo file.

But the forum plugin tries to load “vasthtml_hu_HU.mo” which doesn’t exist. The author of this forum plugin exchanged (mistakenly ?) the minus char with the underscore char. This leads to not loading translations did by my translation plugin.

Please inform the author of forum server to correct the issues.

Some deprecated warnings has been issued by the new API usage of upcomming WP 3.4 Theme core. This has been resolved with version 1.99.18 and should now work as expected.

This has been repaired with version 1.99.18, please re-test it.