3

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.


2

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"), ...


2

Nabil’s answer is fairly complete but there is an easy variation provided: Your plugin is on the WordPress.org plugin repository You’re willing to require that your plugin only work with WordPress 4.6 or higher. The steps are these: In your plugin’s readme.txt file, add Requires at least: 4.6. See https://developer.wordpress.org/plugins/wordpress-org/how-...


2

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(...


1

The nonce authentication method is only for requests made from within WordPress, as described in your own link (emphasis mine): It is important to keep in mind that this authentication method relies on WordPress cookies. As a result this method is only applicable when the REST API is used inside of WordPress and the current user is logged in. In ...


Only top voted, non community-wiki answers of a minimum length are eligible