WordPress.org

Author: Heiko Rabe

You can manage and edit all gettext translation files (.po/.mo) directly out of your WordPress Admin Center without any need of an external editor. It automatically detects the gettext ready components (like WordPress itself or any plugin / theme supporting gettext), is able to scan the related source files and assists you using Google translate API during translation. This plugin supports WordPress MU and allows explicit WPMU plugin translation too. It newly introduces ignore-case and regular expression search during translation.

Requirements

1. WordPress version 2.5 and later
2. PHP Interpreter version 4.4.2 or later
3. PHP Tokenizer Module (normally standard, required since version 1.90)

Please visit the official website for further details and the latest information on this plugin.

Details

1. automatic detection of gettext ready components like WordPress, Plugins or Themes
2. creation of new language translation files at choosen language (ensures correct plural definitions too)
3. inplace adjusting of .mo/.po file permissions to be able to tranlate it
4. component specific (re)scan of source file to build the updated catalog entries
5. wrapping multiple plugins using same textdomain into one translation unit (like plugin and it's widget(s))
6. extended editing of full gettext catalog assisted by using Google translate API
7. full catalog search (exact match) with instant result set view for source or target language
8. correct handling of language dependend plural forms by providing appropriated edit dialog
9. first support of WMPU plugins started at version 1.60
10. complete WordPress support related to multiple textdomains included (since WP 2.8 nad higher)
11. complete support of developer code comments for translators
12. complete support of context based gettext functions and displays this at editor qualified
13. supports also translation of non gettexted code parts, that marked as to be replaced in PHP files directly
14. handles textdomain separation for each module (WP, Plugins, Themes) to avoid standard textdomain usage been part of *.mo file
15. support of Theme language file sub folder (introduced at WordPress version 2.7 and higher)

Announcement

As i stated at one of my articles Features and Future Development this Version 1.x trunk will be maintained now only. This is because of complete rewrite and massive feature implementation of version 2.x series. This may also imply, that the new upcomming version (planned for end of September) will run at first release from WP 2.7 and not lower versions. I will nevertheless support the 1.x trunk, but it would not get more features from now. Please look at the article, it also shows more sneak peak screens of upcomming features. Additionally to the statement above (moved to September 2010) i did a step between 1.x and 2.x trunc. The version 1.9 already contains some fully rewritten new core parts out of 2.0 version. The UI is planned to be redesigned in 2.0 version.