Codestyling Localization

It also can support the WordPress MU platform and allows explicit WPMU plugin translations.

Installation:

Unpack and upload it to the /wp-content/plugins/ directory.
Activate the plugin through the 'Plugins' menu in WordPress.

Features:

• 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 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 nad 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)

What is new in this release:

• Bugfix: sub directory detection for language files at plugins/themes sometimes accidentally failed.

Requirements:

• WordPress 2.5 or higher
• PHP Interpreter version 4.4.2 or higher
• PHP Tokenizer Module