You are completely loading your language file wrong in your plugin, and your file naming is also wrong. load_theme_textdomain(‘my_plugin’, plugin_dir_path( __FILE__ ) . ‘/languages’); should be load_plugin_textdomain(‘my_plugin’, false, dirname(plugin_basename(__FILE__)) . ‘/lang/’); Also, your mo and po files should be named my_plugin-en_US.mo and my_plugin-en_US.po. Go have a look at this tutorial also, this will help you … Read more
You don’t need to change any code. get_the_date without an argument will use the date_format option in your WordPress settings. The option F j, Y will substitute F as “September”, but if you have a translation of “September” it will be used. Comments have suggested the use of date_i18n. This is used automatically when you … Read more
Is it really need to escape translatable strings? Yes. If a string is translatable then that means its value can be changed from an external source. This means it’s not safe. and how shall i do that? See the documentation on how to escape with WordPress. When it comes to translatable strings, there are two … 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
Custom values are not translated
I have no words 🤦♂️ A simple change dirname(plugin_basename(__FILE__)) . ‘/languages/’ inside wp_set_script_translations() function (3rd argument) to plugin_dir_path(__FILE__) . ‘languages/’ fixed the problem
Translations for readmes on .org are done through https://translate.wordpress.org. You could contribute translations for your own plugin if you wanted. Start by picking a locale/language you want to translate into, search for your plugin, and select the Readme Sub Project. You don’t need to do anything special to the readme itself.
Since you have already figured out what the text domain is – the last parameter of __() – I want to add something most people forget when custom post types or taxonomies are made translatable: slugs. Your post type or taxonomy name can mean something very different or even embarrassing in another language. Or it … Read more
Own theme If you are using your own theme, no need to worry about, because /languages folder is in your control that way. 🙂 Other’s theme But your concern is about other’s theme and you want to apply your translations into that theme, then the best way is to make a Child Theme. Because you … Read more
When naming your po and mo files in a theme, you need to only make use of the language code to name these files. Any other convention will not work For example, my blog is in Afrikaans and the localization language code is af_AF. My mo and po files are named accordingly, ie, af_AF.po and … Read more