Lots of plugins exist for human translation (as distinct from automatic machine translation). Here’s a blog post that lists and compares some of the best ones: http://www.wpmayor.com/plugin-reviews/best-wordpress-translation-plugins/ In my personal experience, WordPress Multilingual seems to be the most solid one for a long-term commitment: http://wpml.org. They have a few different price options (including free for … Read more
I think you can just move the languages folder to /wp-content/languages/ then you prevent the theme to update your translations of the theme. And then you can add your own little plugin to change the load_theme_textdomain path to the new folder in wp-content: Add this as a plugin in /wp-content/plugins/buttercream-lang.php /** * Plugin Name: Buttercream … Read more
I got back to this issue today and I solved it like a boss thanks to the Zanto plugin. Just to recap, I was trying to translate the front-end of only one site from a multisite setup with the least possible hassle while leaving every other site unchanged. All I did was copy the general … Read more
Translating dynamic strings
You can use __(), _e(), _x() or _ex() and your textdomain to make your theme or plugin translatable. I stripped your code snippet to the basics, so you will get the idea more easily: <select class=”widefat”> <?php foreach ( $this->getImageSizes() as $name => $atts ) : ?> <option value=”<?php echo $name; ?>” ?>> <?php echo … Read more
Translation update successful but apparently not
I’ve encountered exact same problem. Bad news it is not well supported by WPML… To be more specific it is supported in a very strange way: syncing values for selected custom metaboxes is supported but only “one way” (from original to translated contents but not the other way round). So in your city example you … Read more
Translation for the plugin using redux framework does not work
Ok I made it, it was a problem in po file, missing some arguments or informations in headers. I’ve generated a new one and replaced with my previously done translations keeping only headers. Loco translate made it work. Cheers !
This is, in fact, already available by default. If specific locale isn’t available in plugin’s folder WordPress will try to fallback to languages directory. It is defined by WP_LANG_DIR constant and for plugins the default location would be wp-content/languages/plugins. Note that name is expected to follow the specific format: name-locale.mo.