Could you clarify exactly what the issue is? Every instance of static text in the plugin is wrapped in i18n functions, so there should be no problems with translation.
Thanks.
Well, it might be possible to translate your plugin but it is not ready for Glotpress, which seems to be WP standard.
If it were ready, there would be no banner saying
This plugin is not properly prepared for localization (View detailed logs on Slack). If you would like to translate this plugin, please contact the author.
We might take an extra work and use tools to localize. And what about maintaining?
You guys have such a strict coding and testing standards for contributors, that I can’t keep from suggesting you to make a final effort to fit into common WP translating standards and give WP translators opportunity to do and maintain their translations as usual here.
As Brad said, we have already prepared the plugin for localization by implementing all of the i18n hooks in the code. We can’t guarantee compatibility with all third party plugins. I can look into why this particular plugin is failing to see if it is a general issue that could be addressed, however.
