You can use the translation option via “GlotPress” on each plugin in the official plugin repository. You find all relevant hints in this post of the make blog at wordpress.org. In short, on each plugin you have a translation link and that give all users the chance to contribute translations.
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 … Read more
These terms are not proper nouns and are translated in localized versions of WP Core. Therefore, they should also be translated in plugins. Ideally, you could use them without a textdomain and WP would load it’s own translation.
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
Basically all themes out there are written in English, and localizations strings will look something like this _e( ‘Some English text’, ‘domainname’ );. Usually authors include a pot template with the theme. I qoute from the codex “POT (Portable Object Template) files The first step in the localization process is that a program is used … Read more
How to properly load text domain of custom mu plugin
Use the plugin Edit Author Slug: This plugin allows an Admin to change the author slug (a.k.a. – nicename), without having to actually enter the database. You can also change the Author Base (the ‘/author/’ portion of the author URLs). Two new fields will be added to your Dashboard. The “Edit Author Slug” field can … 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
EDIT – apparently this is all wrong so please disregard. You can use the WP_LANG_DIR constant to load translations from the update-safe languages directory first, and fall back to your plugin languages directory for any plugin-supplied translations. The default location is wp-content/languages, and users can set WP_LANG_DIR themselves in wp-config.php. When you load translations from … Read more