Plugin user

And by the way, I say this issue is NOT resolved until all of us are translating this plugin without having to edit the core every time the plugin is updated!

Wordfence is a great plugin!

And it is actually ready for us to translate to many languages. The messages are already using I10n functions. The pot file is easily created with poEdit and translate the messages and saved them in mo files.

The only thing missing in this plugin is to load the texdomain (once the mo translation files are ready).

This is the way I do it.

Because I do not want to edit Wordfence every time they update the plugin, I load the textdomain for WordFence in my own plugin like this:

/* Translate Wordfence plugin */
// Added by Horacio Figarella
add_action( 'init', 'Translate_Wordfence' );
function Translate_Wordfence() {
$browser_lang = substr($_SERVER['HTTP_ACCEPT_LANGUAGE'], 0, 2); // Get the browser language
switch ($browser_lang){											// Set language independently of the country version
	case "es": $locale = 'es_ES'; break; case "fr": $locale = 'fr_FR'; break; case "it": $locale = 'it_IT'; break; case "pt": $locale = 'pt_BR'; break; case "co": $locale = 'co'; break; default: $locale = 'en_US';
}	// and set it to one of these 6 languages of this site
$domain = 'wordfence';		// Domain 1
$mofile = $domain . '-' . $locale . '.mo';  // Contains all translation for all 3 domains
unload_textdomain( $domain );
load_textdomain( $domain, WP_LANG_DIR . '/plugins/' . $mofile );
$domain = 'wordfence-2fa';  // Domain 2
//$mofile = $domain . '-' . $locale . '.mo'; // Not needed
unload_textdomain( $domain );
load_textdomain( $domain, WP_LANG_DIR . '/plugins/' . $mofile );
$domain = 'wordfence-ls';  // Domain 3
//$mofile = $domain . '-' . $locale . '.mo';   // Not needed
unload_textdomain( $domain );
load_textdomain( $domain, WP_LANG_DIR . '/plugins/' . $mofile );
}

Eventually the plugin developers will integrate a version on this code in their plugin with support for more languages. I am only interested in 6.

I may understand what Tim says above because they are too busy making the plugin that good.

But it really does not take much time to make a plugin translatable. All is needed is to add 2 words to every text to be output.

__( ‘text to be output’, ‘domain’ ) when you want the text translated but not echoed and _e( ‘text to be output’, ‘domain’ ) otherwise.

The advantage of translation, Tim, is to the client, the final user.

This message on the screen:

“Email verification invalid or expired. Please try again.”

You know what it means, I do too, but this person in another country visiting my web site which is all in his/her language and this message pops up in English makes it difficult for them to understand what we want them to do.

Yeah, they can use a machine translator. But I prefer to say exactly what I want, and not to depend on another translator. ¿Entiendes lo que digo?

Horacio

• This reply was modified 6 years ago by Plugin user.