Translating Jetpack CRM

Jetpack CRM is growing in popularity every day and as it gets used by more and more countries, “How do I translate Jetpack CRM” crops up as a question more and more.

How to Translate Jetpack CRM

It’s not a secret, the Founders of Jetpack CRM are not great at spoken languages. Our coding brains spend most of their time writing in computer languages, so translating into Dutch, or Romanian or other languages doesn’t come naturally to us.

That’s where you come in to help us help you. But how?

Translating plugins has changed!

In 2017 WordPress translations changed completely. Translations used to be added to plugins by the Plugin Author adding “.mo” and “.po” files to a /languages/ folder and managing translations through there.

Now the responsibility for who creates the translations has changed. Instead of plugin authors, it is now all of us, the plugin users and site managers and everyone together who are responsible for translating plugins into our own language. They’re crowdsourced, so to speak.

Here is where the magic happens (see the Jetpack CRM Project Page)

It’s a big job, but luckily both are providing us with tools and support to help us get reliable translations to every language in the CORE plugin. Join us to reach the goal of making Jetpack CRM available in as many languages as possible, with no BS incorrect or machine translated languages.

Read on to find out more about how to join us #polyglots to #makewordpress.

How to Translate now?

Every language has a team. If you want to be a translator, you should go find out how to join the team for your language:

The general translation project page (showing all the languages supported) is available here:

Getting setup to be able to translate Jetpack CRM

Most translation team leaders are on WordPress slack and you should ask them how to be accepted (in general) as a WordPress translator. Here are the steps to quickly setup your WordPress and WordPress Slack accounts.

  1. Login/Register at
  2. Login/Register (same account) at
  3. Visit and use the same account to register for Slack
  4. Visit to set an image for your new address
  5. Visit and find your language, then click on “View Team”

If you’ve done this already then great you’re already a valued translation team member and all we need now is your help in translating the plugin 🤗

New to joining your language team? What do you do?

Once you know where to find your language team, and you have all your accounts setup, it’s time to say hello to your language team and get accepted as a translator.

Step 1: Introduce yourself on #polyglots
Start with saying “Hi” in the #polyglots channel on WordPress Slack.

  1. Open WordPress Slack
  2. Click the + next to channel
  3. Search for #polyglots
  4. Join the channel
  5. Say “Hello” (or something like it). Introduce yourself, and mention which language team you want to join. For example: “Hello, Iam new, and want to join the language team.”

Say hi to your language team leaders
Next, you can message some of the leaders of the team, to let them know. Visit your language team page, or look through the requests or the Jetpack CRM Translations to find other WordPress users who have validated in the past. Then make a direct message in Slack to say hello to them also:

  1. Open WordPress Slack
  2. Click the plus next to Direct Message
  3. Search for the people from your translation team and add them to the message.
  4. Enter a message and say “Hi” again and introduce yourself, like you did in the #polyglots channel.

Ask your team a couple of questions
There are, at least, two (2) questions that you want to ask your language team leaders before you submit a request for help with validation:

  1. “How do I join the team?”
  2. “Is there anything you can tell me before I make a request for validation?”

Note: Be nice to these folks, as they have worked hard at what they do and obviously care a great deal about translation into your own language. They are your new collaborators, and you are their new team member. Enjoy the opportunity to meet these new colleagues and to work together on translating WordPress

Once you’re in a language team you can translate as many parts of WordPress as you like. Not just Jetpack CRM.

Our goal is to get Jetpack CRM fully translated to your language, but also, have WordPress available to as many people across the globe as possible.

Translate some Strings!

The best way to get started is to click on one of the incomplete projects and then click on “untranslated”. This gives you a list of strings that need translation. Double click and add a translation. Easy!

Here’s the link to find which strings need translating:

Validation of your work

Once you have translated some strings, you can ask your language team for help with validation. You can make your request here:

Here is a template you can use to make your request. All the users tagged in the request will receive a notification.

Hello #polyglots! I translated some strings with our project language team and we need your help with validation. o fr_FR @MyUsername @woodyhayday @mikemayhem3030 Pleased to answer comments and questions below in the comments.


CAUTION: Your language team will be happier if you contact them by WordPress Slack to say hi, first, BEFORE you request help.

Your team may also have additional suggestions or rules about joining their team. Be sure to ask “How do I join the team?” before you ask “Is there anything you can tell me before I make a request for validation?”.

It’s just a better experience all around – they’re people at the end of the day.

Project Translation Editors

Once you translate some strings, the strings must be validated by someone who is a member of your language team, or a “PTE” for short.

Remember the person you said “hi” to above? Someone like them. Once you join your language team, and then complete a translation for Jetpack CRM, you can ask a leader of your language team to set you up as a PTE for Jetpack CRM for your language.

PTEs can validate strings. PTEs are assigned by the WordPress language team to projects in their language.

For example, a person who translates Jetpack CRM into Russian would go and talk to the Russian team members and ask them to validate the new translations. Then, when they finish, the translation team might make them a PTE for the Jetpack CRM Russian translation.

Being a PTE means that your strings are automatically validated, and you can validate the contributions of others, too.

New Translations

Jetpack CRM grows all the time as we add new features. So new translation strings are added all the time. Being an editor means you can fast track your translations as well as approve ones in the queue.

Jetpack CRM: Translation Leads

Are you committed to keeping Jetpack CRM fully translated for your native language? Here’s what you have to do (and get)

  • Join the WordPress language team for your native language.
  • Complete and continuously update the translation of Jetpack CRM core and readme.txt on for your language.
  • Complete and continuously update the translations of our extensions*
  • Follow your own WordPress language team’s guidelines for translations and collaboration with other translators.

You’ll get one of our special Jetpack CRM translation team swag bags as a special thanks.

*We’ll be adding support for crowdsourced translation of our extensions as part of our v3.0 release.

Phew, sounds like a LOT of work vs the old method

Sure, translating via .mo and .po files was easier, however it was a lot harder to keep updated and also prone to error (which would go unchecked, since we don’t speak French, for example).

So, say we add 50 new strings to the CORE plugin in an update, the .po files would need to be regenerated then they need adding to the CORE via sending to us, us adding to the /languages/ folder and updating that way.

Plus, as good as a translator people may be, typos could happen, or certain phrases mean different things in different areas of a locale, so having a centrally sourced translation area helps here and makes the translations as good as they can be.

Having it all online means new translations are picked up automatically, and translated as we add them to the core (as long as we have willing translators), then automatically delivered to everyone using Jetpack CRM in that language – without needing to manually update the .mo and .po files all the time. Winner.

Translating Extensions

We have a ton of extensions available for Jetpack CRM and these are (unfortunately) not part of the bigger WordPress system (with crowdsourced translations) and teams working together to validate the translations*. 😭😭

That doesn’t mean we don’t need and want your help here too. If you have a extension you’d like to offer translation for please do contact us using the form here and let us know which one.

Make sure you put “Translation Request: {extension}” into the subject line (putting in the name of the extension over {extension}).

*We’ll be adding support for crowdsourced translation of our extensions as part of our v3.0 release.

Jetpack CRM Translation Rewards

To help give back to the community who help us translate Jetpack CRM we’ll be giving out some rewards to those who help us translate.

If you have translated Jetpack CRM via this page, let us know and we’ll sort you out some swag, a little like the swag the translation team leaders get, but not quite as, swaggy.

Simply submit a ticket to us and we’ll sort you out your reward (let us know your WordPress username in the submission too)

For translating extensions, use the same form, and contact us. A lot of our extensions do not have too many language strings in them (on purpose) so will be a lot easier to translate.


Updated on August 26, 2020

Was this article helpful?

Still not found an answer?
If you've searched the knowledge base and still can't find a solution, please submit a ticket.