Support » Plugins » What to do when plugin maintainer does not accept translations?

  • Niklas


    Despite the philosophical and social nature of the topic title I am looking for a solution to a peculiar problem. I am using a plugin from an active developer who’s plugin sees hundreds if not thousands of active installs currently.

    As his plugin was prepared for translation with __() and _e() wraps around text strings, as well as a functional code that loads translation files. A .pot file was even provided inside a languages directory in the plugin package.

    While no translation files (.po, .mo) were supplied though. I sent him my translation files but the developer did not accept it on the grounds that it would add to the bandwidth cost of the plugin user plus the fact that it would add bloat. Potentially tripling the total plugin folder size if there were many languages included.

    How do I best solve this by side loading the translation file whenever the plugin is updated?

  • The topic ‘What to do when plugin maintainer does not accept translations?’ is closed to new replies.