If you have bought a theme you should have support for other languages. See the chapter Internationalization in the theme developer handbook for more information, or e.g. more specific on translation functions like __() the Code Reference. If you independently developed a theme, you probably forgot about this element. If not, check if your theme … Read more
This is the notation of the (pretty old) Plugin qtranslate. It was abandoned way back and replaced by mqtranslate and later qtranslate-x, which at this point are also abandoned. You can however convert your content to be used with wp multilang, which works with gutenberg, by replacing the <!–:lang–> tags with kinda shortcodes [:lang]. So … Read more
None. Escaping should happen late, on output. This is just registering the strings for later use, so it’s too early to escape. All the places in WordPress where the post type label is used automatically, WordPress should already be escaping it. If you’re outputting any of the labels yourself, you would probably use esc_html(): $post_type_object … Read more
If you load a text domain in child theme, you may need call it in after_setup_theme filter which loads immediately after all the theme functions.php. You may refer to this note It could be due to the loading sequence. Since I haven’t seen it in your above code. I guess you load the text domain … Read more
No, there isn’t. The text domain needs to be hard coded, otherwise it can’t be read by localization tools which parse the code without executing it. See this note from the Internationalization documentation The text domain should be passed as a string to the localization functions instead of a variable. It allows parsing tools to … Read more
The notes to translators aren’t required, as far as I can tell, but they will definitely help anyone out who’s trying to translate your plugin. You might want to think of them as best practices rather than requirements. As to your second question: Since WordPress 4.6 translations now take translate.wordpress.org as priority and so plugins … Read more
I found the solution: In the constructor I had to add this public function __construct() { // your code goes here add_action( ‘plugins_loaded’, [$this, ‘load_text_domain’] ); // your code goes here } public function load_text_domain() : void { load_plugin_textdomain(‘your-plugin-textdomain’); } This finally made sure that the language displayed followed the settings of the user profile … Read more
Your first line of code looks ok, are you sure you have a translation for the ‘Featured’ string in your PO file? Your second issue is an excellent example of how you should not use the gettext functions. You are trying to translate dynamic string ‘<a class=”more-link” href=”‘. get_permalink($post->ID) . ‘”>Read More</a>’ for which you … Read more
As documented (always read the docs), printf() returns: …the length of the outputted string. That’s why you’re getting 30. If you’re adding a value to an array or a string you need to use a function that returns a value. Not one that prints. printf() prints the value and returns the length of the printed … Read more
What I now want to be able to do is set the locale for a function call of __(), to retrieve the translation you defined on your plugin’s .mo for a translation which is different from the current locale. I’d prefer my translations to be translated all in the same way, using the same logic … Read more