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 can assists you using Google Translate API or Microsoft Translator 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. BuddyPress and bbPress as part of BuddyPress can be translated too. Produces transalation files are 100% compatible to PoEdit.
- WordPress version 2.5 and later
- PHP Interpreter version 4.4.2 or later
- PHP Tokenizer Module (normally standard, required since version 1.90)
- PHP Curl Library (if Microsoft translation API services should be used)
Please visit the official website for further details and the latest information on this plugin.
- automatic detection of gettext ready components like WordPress, Plugins or Themes
- creation of new language translation files at choosen language (ensures correct plural definitions too)
- inplace adjusting of .mo/.po file permissions to be able to tranlate it
- component specific (re)scan of source file to build the updated catalog entries
- wrapping multiple plugins using same textdomain into one translation unit (like plugin and it’s widget(s))
- extended editing of full gettext catalog assisted by using Google or Microsoft translate API
- full catalog search (exact match) with instant result set view for source or target language
- correct handling of language dependend plural forms by providing appropriated edit dialog
- first support of WMPU plugins started at version 1.60
- complete WordPress support related to multiple textdomains included (since WP 2.8 and higher)
- complete support of developer code comments for translators
- complete support of context based gettext functions and displays this at editor qualified
- supports also translation of non gettexted code parts, that marked as to be replaced in PHP files directly
- handles textdomain separation for each module (WP, Plugins, Themes) to avoid standard textdomain usage been part of *.mo file
- support of Theme language file sub folder (introduced at WordPress version 2.7 and higher)
- support of BuddyPress and also bbPress as integration part of BuddyPress
- support of *.pot file content during new language file creation
- support of encrypted premium plugins but with security risk warning
- support of low memory conditions (32M memory_limit) with big translation files or source codes
- support of IDN based installations if PHP version is 5.0 or higher
Starting with version 3.4 of WordPress I faced a restructured handling of localization within the Core Files, can be read here: Important Changes for WordPress 3.4 Because I had to cope with this, the translation process of WordPress itself has been rewritten. The pugin now supports backward compatibility (for older WordPress versions) and also generates two new structured *.mo files. It depends on your installed version, if it’s less than 3.4-alpha, than you will get the old files generated otherwise the new files.
Support & Development
The plugin stays for a long time at major version 1.x now and it was planned to come up with a new major release 2.x several month ago. But because of massive changes at the WordPress core, not having that much time I would need, the new major version will be delayed again. I can’t estimate currently a timeframe for availability. That’s why I continue maintainance of version 1.x as long as I’m working on version 2.x at alpha stage in parallel.
Translation API’s & User Interface
Introduced with version 1.99.17 of this plugin, the translation API’s of Google and Microsoft have been integrated. Both require at least subscriptions and the Google API is a paid service. The plugin knows, which API is able to translated what language, so you will find the information next to your language file to be translated at the list. I did reshape the User Interface a bit more closer to WordPress Standard UI, so it should be more intuitive to use it from now on.
The german translation has been created with this plugin itself. Feel free to make your translation related to your native language. If you have a ready to publish translation of this plugin not pre-packaged yet, please send me an email. I will extend the package and remark your work at Acknowledgements.