Simple Punctual Translation - ChoosePlugin.com

A plugin for WordPress that allow to translate any post type in another languages. Translate only the single view.

Author:	BeAPI (profile at wordpress.org)
WordPress version required:	3.0
WordPress version tested:	3.1.4
Plugin version:	1.0.2
Added to WordPress repository:	15-02-2011
Last updated:	15-02-2011 Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
Rating, %:	0
Rated by:	0
Plugin URI:	http://www.beapi.fr
Total downloads:	10 052
Active installs:	20+
Click to start download

A plugin for WordPress that allow to translate any post type in another languages.

The user features can be summarized in the ability to switch between multiple languages and on the single view of content. Thus, a page can be translated in X languages.

The architecture chosen for development is fully consistent with WordPress 3.0, we created a content type translation, and we created a taxonomy for the site languages. We customized the WordPress admin console to provide the translation functionality, a bit of AJAX to make the convenient interface. Finally, we created a widget that displays the languages available for the currently loaded content.

A translator role is automatically created with the plugin, it allows a user to this role only to create and manage translations.

The plugin offers settings:

Automatic insertion of languages available to the end of the article
Language detection URL : via a "lang" parameter in the address or via a prefix beginning of the address:
- http://www.herewithme.fr/contenu/?lang=de
- or http://www.herewithme.fr/de/contenu
Enabling translations on their choice of post types
2 modes for the translation mechanism, which I will explain in FAQ.

Screenshots
FAQ

What differences between the 2 translation engines ?

For this plugin, we did not impose an architecture defined for the translation engine, so we proposed an automatic or manual mode.

Automatic mode

The automatic mode is rather aimed at the general public, because no change is necessary in the source code. The idea is that, when sailing on the German version of a page, WordPress retrieves data from the original page, and our plugin is automatically injected the contents of German 3 fields, title, content and extract .
This means that the German version in automatic mode will keep, if your theme display it, publication date, comments, author, tags and categories of the original post.
This mode is quite sufficient to use the basic translation plugin on content types native, it is compatible to 99% on the existing WordPress installations.

Manual mode

This second mode is much more powerful than the first. The manual mode does not modify any data from the initial query of WordPress, so no modification is made on the theme, your content will not even be translated! To switch language, we were inspired by functions of WordPress Mu allowing switch between blogs, either switch_to_blog() and restore_current_blog().
And we have created 2 functions switch_to_language() and restore_original_language().

The first function switch_to_language() toggles the content in the translated version, while the second function restore_original_language() allow to restore the original language of the content.

Example :

<?php
the_title(); // Title in English

switch_to_language();
 the_title(); // Title in French
restore_original_language();

the_title(); // Title in English
?>

This pair of functions allows developers to be extremely precise about which fields to translate. This mode in my opinion, should be widely preferred because it is clean, it does not interact with the original application of WordPress. Nevertheless, there are some flaws such as:

The title page’s HTML is not translated
Plugins breadcrumb does not take into account the translation

These are mainly defects on the SEO aspect, and indeed on this first version of the plugin that we have worked the functional aspect. We rely on community feedback to improve the plugin …

Hide FAQ

ChangeLog