Working with .po and .mo files translation
Working with .po and .mo files translation
Working with .po and .mo files translation
Translation for frontend
I was able to fix the problem by switching the xdebug extension. I had a vc9-nts version installed and switched to vc6-nts which solved the issue.
You need create a es_ES.mo file, using the .po file included with the Theme. Try using something like POEdit or a similar utility.
I haven’t tried this myself but theoretically it should work. It just requires some hacking. First of all, this involves using qTranslate. If you don’t want a multilingual site, you can always fill only the default language. Then to force display only the default language on the post pages, you will need to modify the … Read more
You’ll first need to create your .POT file, here are some instructions: http://weblogtoolscollection.com/archives/2007/08/27/localizing-a-wordpress-plugin-using-poedit/
When every message is hard coded in the theme files there can be no problem with gettext anymore. So, yes, depending on the theme WordPress can use different templates for home and other pages. But no, this has nothing to do with automatic translations. You have simply forgot to translate some strings, possibly in front-page.php … Read more
Most translation tools are really hard to use when you try to handle a long text, so the translators have to use a HTML editor anyway. Use separate files, but use the language prefix as directory name: en main.html help-main-options.html help-special-options.html de main.html help-main-options.html help-special-options.html That’s easier to handle for translators and for you too. … Read more
The default text domain is registered in wp_load.php before plugins are loaded. See the function wp_load_translations_early(). So when you register your action callback, the text domain has been loaded already. For an alternative way to list all registered text domains see this answer: List of Default Translated Phrases.
First, actions added to plugins_loaded hook will not work from theme functions.php or any theme file because at that point it will be already fired (too late from theme files). What you can do is to hook your action into after_setup_theme and unload buddypress text domain first and then add your custom buddypress text domain … Read more