You shouldn’t be using a constant (in your case CORE_THEME_NAME) for the textdomain. This is because the call to __ is parsing your code, not running it. Simply said: it’s not looking up the value of the constant. So, it won’t translate. Quoting the famous Otto: Inside all translation functions, no PHP variables are allowed … Read more
From the source code of load_plugin_textdomain it becomes appararent that the function will first look for $domain . ‘-‘ . $locale . ‘.mo’ (so, that’s myplugin-fr_FR.mo) in WP_LANG_DIR . ‘/plugins/’ . $mofile. Only when the file is not there, it will start looking at the specified path and if it is not there in the … Read more
Load translation files as late as possible for your plugin’s use-case. This allows other plugins as much time as possible to fully initialise. Why should you care about other plugins? Because they may be involved in the localisation process too. For example, changing the site language or filtering translation file paths. They can’t do those … Read more
‘;)’ => ‘icon_wink.gif’, is in line 2477 in the current version, you should never just change or delete core files, unless you know how to run a private branch of WordPress. Line 2925 is the second trigger_error() in this function: function _deprecated_argument( $function, $version, $message = null ) { do_action( ‘deprecated_argument_run’, $function, $message, $version ); … Read more
Here is a patch for 3.5 to use this with plugins. Use wp-content/languages/plugins/textdomain-pt_BR.po Apply this via SSH with: patch -p1 < no_plugin_overwrite.patch Hopefully its gonna be released in 3.6. Ticket #18200 (new task (blessed)) Implement language packs for core, plugins, and themes.
I was having the same problem and this is how I solved it: First, the generated JSON file has some errors. You need to update where it says messages with your text domain. There are three places where that needs to be changed. I also had to change the lang attribute to be all lowercase … Read more
You could hook into the action switch_blog. You get the new blog ID as the first argument here. But loading the complete translation files here is expensive, you also have to restore the old files after that. WordPress does not use native gettext functions, but some custom code that is much slower. See #17268. The … Read more
load_theme_textdomain() returns TRUE on success and FALSE if no file was found. For debugging try the following change: function my_theme_setup(){ $path = get_template_directory() . ‘/languages’; $result = load_theme_textdomain(‘my_theme’, $path ); if ( $result ) return; $locale = apply_filters( ‘theme_locale’, get_locale(), ‘my_theme’ ); die( “Could not find $path/$locale.mo.” ); }
Have a look at the wp-settings.php file. You’ll see that the plugins_loaded action is triggered before the theme is loaded. The first action available for themes to hook into is the after_setup_theme action.
TL;DR: If you use strings that are in the parent theme, exaclty how they are used in parent theme, you don’t need to have a text domain for your child theme. But if you use strings that aren’t used in parent theme, to make them translatable, you’ll need another text domain with related translation (.mo) … Read more