Let us look at the relevant line. I am reformatting it to easier understand what is going on: printf( _n(‘1 comment’, ‘%1$s comments’, get_comments_number() ), number_format_i18n( get_comments_number() ), ‘text-domain’ ); So what you are doing is calling printf with three parameters, each one now being on a separate line now as I formatted it. But … Read more
Is it worth having two plugin textdomains – one for admin area strings and another one for “frontend”? In theory yes Does it break any guidelines (the plugin is public)? glotpress which drives the wordpress.org translation section is unlikely to ave any of it. For it you have to use only one text domain which … Read more
Since WP 4.6 load_theme_textdomain() (and consequently load_child_theme_textdomain()) will give priority to .mo files downloaded from WP’s online translation platform (translate.wordpress.org). Due to some new code (here, on line 769) these functions will completely ignore your local .mo files if the textdomain is found in the general languages/ directory. You can, however, use the more basic … Read more
In my opinion you are focusing on a wrong issue in this case. For instance, if I want to change the Read More message I have to browse all files to see if it is there. This doesn’t indicate localization problem. This indicates templating problem. What if you want to change markup of Read More … Read more
You can call load_plugin_textdomain() multiple times in each plugin, but I would not do that. Put the common files into a separate plugin, for example luke-carbis-library. In that plugin create two simple functions for setup and loading extra files: add_action( ‘plugins_loaded’, ‘lcl_init’ ); function lcl_init() { $dir = plugin_dir_path( __FILE__ ); $url = plugins_url( __FILE__ … Read more
After searching a little bit more, I found that in the generation of the .pot file, the strings of plugin header already appear there. The tool I used to generate .pot file for my plugin was this command of wp-cli: https://developer.wordpress.org/cli/commands/i18n/make-pot/ I don’t know if another tools to make plugin translation do that. The reason … Read more
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