Looks like we originally missed one thing, before I took over as the developer from my employer WebDevStudios:
https://github.com/tw2113/WP-Contributions/blob/master/wp-contributions.php#L2-L13
Need to specify the textdomain in the plugin header area.
Beyond that, I’m looking around the files and the hardcoded strings and we were really good about using the gettext functions and we load the textdomain at https://github.com/tw2113/WP-Contributions/blob/master/wp-contributions.php#L72
If you know if/that the Polyglots UI depends on the plugin header textdomain property, then I can get that fixed up pretty readily, and probably should anyway, even before confirmation on their UI depending on it, just in case.
I have to believe it’s either the header, or maybe we shouldn’t be running some things on plugins_loaded hook, because a good amount of the text should all be translation ready already.
I’ll get it figured out one way or another.
Added the textdomain to the plugin header
Also removed the local languages folder in favor of letting WP.org handle more things, so hopefully it gets marked as translation ready soon. Beyond that, I’m not sure what’s preventing things, because we have the spots in place and the textdomain getting loaded.
Not sure how long it takes for https://translate.wordpress.org/projects/wp-plugins/wp-contributions/ to refresh its checks.
@presskopp Looks like it’s good to go via .org translation tools.
