Textdomain problem?

Hi @sebastienthivinfocom,

Sorry for the troubles – we definitely want translators (and international users generally) to have a successful experience with our plugins.

Can you be a little more explicit, though – which string or strings are the problem, exactly?

I’m sorry, I didn’t note the string URL :-/
But the matter was close to https://github.com/moderntribe/tribe-common/pull/380
a text-domain used in the PHP different from plugin name so unused by WordPress.

Our Tribe Common module is something of a special case, as it is used in multiple plugins. It does indeed utilize a different text domain and so translations need to be handled differently, via our own Glotpress installation.

OK but we’re translating for nothing in WordPress GlotPress. We’re volunteer to translate… so It will be great to remove string with a different TextDomain to avoid working for nothing…
Why not mmaking a plugin “tribe-common” on the WordPress directory which be installed by TEC?

That’s something we might consider, but it’s not likely to happen soon.

We do of course appreciate you are volunteering your time and knowledge for free when you provide translations – whether it is done via the translation site provided by www.remarpro.com or our own, it’s really great to see and helps lots of users as I’m sure you know.

There is no requirement, though, to purchase a license if you wish to submit translations on our own GlotPress installation and the workflow is very similar.

Hey there! This thread has been inactive for a while so we’re going to go ahead and mark it Resolved. Please feel free to open a new thread if any other questions come up and we’d be happy to help. ??