Thanks @toscho — The problem plugin in particular is wp-pagenavi. The backend strings are being translated, however; the frontend remains in default en_US locale. I found this: https://wordpress.org/support/topic/translation-91
To be more specific, the text field values on plugin options page do not get translated so my assumption is that translations are malformed somewhere in the codebase.
Related Posts:
- Translate a plugin using .po .mo files
- What is the way to ship read-me strings like plugin-strings for internationalization?
- Override plugin text domain in child theme
- Making my plugin translation ready. Poedit not working
- Two text domains in one plugin
- Use translated taxonomy labels in plugin
- What can be reason for no plugin-strings available under stable section on translate.wordpress.org?
- Is there a way to test that readme looks in other language before submitting translation?
- Setting Email locale before retrieving gettext translations
- Translation issue with global variables
- How to ignore extra whitespaces in translation functions like _e?
- Plugin not properly prepared for localization
- How to translate user added content in a plugin
- Use localized plugin name and description even when the plugin is disabled
- I dont know why my localization is not working
- Admin Notice is only localized when displaying the “Plugins” Backend Page
- Can I leave off plugin textdomain for terms used in core?
- [Plugin WPML] : How to create a translation of a post using the WPML API?
- __(): What if I have to pass in a variable?
- Overriding single plugin translation
- Using plural-only translation of register_post_status() in plugin
- Can’t set proper WooCommerce language translation [closed]
- Override plugin localization
- Adding a text domain to every __(), _e() and __n() gettext call without a plan to create own translations
- Force Plugin to English Translation
- Overwrite textdomain of plugins by default – Lost Translation
- Why can I not use a class constant as text domain?
- What is the purpose of adding a .po file?
- Internationalization and the plugin description
- translation does not work with text_domain
- How can I translate the name of my Plugin for other languages?
- Is it necessary to translate WordPress key terms when localizing a plugin
- Plugin readme.txt and assets internationalization
- Plugin translations problem
- Translate wordpress plugin [closed]
- Translate third party plugin and save translation files in custom theme
- Suggestions for i18n plugin [closed]
- Why load_textdomain work but not load_plugin_textdomain?
- Language Translation is not working?
- How WordPress knows where to find locale files?
- Automatically translating from existing .po and .mo files?
- Are contributed plugin translations automatically installed in WordPress?
- Prepare plugin options for multi-lingual support
- Translating plugin inside the theme [closed]
- Can I use the same textdomain in two separate plugins?
- Localiztion in javascript
- Internationalization: Not loading plugin translated text
- load_theme_textdomain path
- Read text defined under __()
- Loco Translate: Custom Post and Custom Taxonomy Labels not translated in wp-admin menu
- Internationalization autocomplete JS variable
- How to add links in .po (language) file in wordpress?
- Change the backend language of a single plugin
- Translating long texts with html formatting
- How to translate __(”) strings in admin [closed]
- Working with .po and .mo files translation
- Is it possible to use multiple post_name, post_title and post_content?
- How to merge two .PO language files?
- A new translation folder overrides my usual translation from “nowhere”
- Is there any way to use google input tool or any other language keyboard with WordPress [closed]
- Can I load the textdomain before a plugin is activated?
- Translation for the plugin using redux framework does not work
- How WordPress is able to change locale without using setlocale
- How I can internationalize variables within the function _e () __ (), etc?
- Plugin for single language localisation [closed]
- Cart66 localization hardcode strings [closed]
- Localize plugin name
- Using wordpress translations strings in plugin
- Using Variable in WordPress Translate Functions
- Translations for my plugin don’t show up
- How to translate WP Blog (search, category etc.)?
- Plugin translation not working on WordPress.org
- How to translate wordpress error message
- How does translation (gettext) work for translating config file of plugin?
- Update-safe translating of single text string in plugin
- Override translation of 1 word
- Replace woocommerce | (pipe) separator in product variation to , or another character?
- Localise settings section headline
- I’m looking for a visual composer / builder plugin that supports RTL
- How to install a translation for a WP plugin?
- Rename existing cpt and taxonomy with new textdomain
- Translations not appended even strings are edited
- How can I change a translation for a string in a plugin?
- How to translate wordpress blog to other languages?
- translate wordpress website from english to arabic
- How to change WordPress core language using Loco Translate?
- Securing langugae folder
- How connect my plugin translation to my page
- Suspect incomplete .pot file – what to do?
- Plugin: Translated plugin is “not translated”
- Translation plugin with default language?
- Plugin Translation project not found
- WP internationalization not loaded
- Internationalization of Blog Posts
- Google Language Translator – Manage Translation
- Translate Woosidebars plugin strings
- Apostrophes replaced by '
- plugin translations not reflected in admin dashboard
- Plugin translations are not loaded from translate.wordpress.org
- plugin translation *.mo file not getting loaded for custom post