There is no way to know if string should be translatable or not (should a ‘fail’ in a json response be translatable?). Some things just need proper code review and can not be automated.
If it’s a text field, why would you? The user can put in whatever they want in their own language. If it’s some sort of select then you just localize the options. Regardless, you’re not supposed to put variables or code inside __() functions because that’s not how translations work. WPML has its own way … Read more
Looks to me like WordPress doesn’t enable UTF-8 mode when it runs the regex. https://github.com/WordPress/WordPress/blob/5.2.1/wp-includes/rest-api/class-wp-rest-server.php#L837 In PHP, matching multibyte characters requires the u flag. (The code above just adds the case-insensitive flag). So although some strings will still match (like “Département”), they’re not matching as whole Unicode characters. For example the following pattern matches when … Read more
Start a new theme from scratch to see if you have the same result. I test with theses files and the translation works style.css /* Theme Name: My Theme */ functions.php <?php add_action( ‘after_setup_theme’, ‘my_theme_load_theme_textdomain’ ); function my_theme_load_theme_textdomain() { load_theme_textdomain( ‘my-theme’, get_template_directory() . ‘/languages’ ); } languages/es_ES.po (file languages/es_ES.mo created with poedit) msgid “Featured” msgstr … Read more
Apply to become a translator If you want to provide your own translations, you have to post a request at https://make.wordpress.org/polyglots/ stating which languages you want to translate yourself, so this implies that you actually speak those languages fluently. This is what I have done and what I will describe in this answer. But if … Read more
It’s possible to achieve this with WordPress Multisite feature. I did this before – with “subfolder” settings, you can create two websites (with one WP instance), example.com/en/ and example.com/de/ … But I did it only once when I didn’t know better. And it was pain in the … to maintain. Then I found Polylang plugin, … Read more
Themes have their own language files. Look in your themes folder for a po file: /wp-content/themes/yourtheme/
One error: the function is load_theme_textdomain(), not load_textdomain(). The former is used for Themes to define/load a textdomain; the latter is for core, I believe. (Plugins have an analogous function, load_plugin_textdomain().) Try using: load_theme_textdomain( get_theme_text_domain(), get_template_directory() . ‘/languages’ );
load_theme_textdomain() needs an absolute path to the directory, so you should set your THEME_URL like so define(“THEME_URL”, get_template_directory()); define(“TRANSLATION_URL”, THEME_URL . “/languages”); It wasn’t working for you because get_bloginfo(“template_url”) is an URL and not an absolute path on your server.
Just add the full string of the plugin name into the plugin’s text domain. WordPress looks this up automatically. Same with Description, PluginURI, Author and AuthorURI. See the internal function _get_plugin_data_markup_translate. The string extractor in Glotpress (and my own plugin Loco Translate) adds these header strings automatically to new POT files.