Re the action for me (Simon Wheatley) to open source my multi-language plugin as part of the “i18n improvements” session.
The Babble multi-language plugin we wrote for and used on Free Speech Debate, is now available on GitHub at https://github.com/simonwheatley/babble. The plugin handles translating posts in all post types and terms in all taxonomies, though the translation of terms badly needs a workflow. Translation of widgets and menus is currently not covered by the plugin, and in the future I’d like to see a much more “work queue” style system for the translation teams in the various languages.
Please feel free to comment, raise issues, fork, submit pull requests, etc.
If you like the approach of using custom post types and taxonomies to store the translations, it’s also worth looking at the Multi-Language Framework plugin by HackLab.
Im happy that this topic came up in the summit.
In the plugin I developed, which Simon mentions, I managed to translate all site options, including widgets, with a filter in the get/add/update_option() functions. This filter checks which language are we visiting right now (int the front end or the admin, does not matter) and allways look for a corresponding option in the current language.
For instance, if you do a get_option(‘option_name’) and are visiting the spanish site, it will try to find an option called ‘option_name_es’. If there is not, it will get the default. Same thing when saving.
Pingback: A Tale of Two WordPresses: WPCS & Pressnomics - WP Realm
whoaaaaa.. it’s rock on.. thanx for the info.. go to GitHub now
Pingback: Managing multilanguage WordPress sites — ms-studio.net