History of the Team

Welcome to the official blog of the translators team for the WordPress open source project.

This is where we discuss all things related to translating WordPress. Follow our progress for general updates, status reports, and debates.

We’d love for you to help out.

Translate WordPress

You can help translating WordPress to your language at any time. Just log in to the translation platform with your WordPress.org account, and suggest translations. If you want to help in managing and validating translations, please make sure to get in touch with the existing language team and follow the glossaries & style guides if the team has them.

Don’t see your language?

Request support for it by following this guide.

Weekly Meetings

We have meetings every week and at various hours every week. Check Slack in #polyglots (the schedule is on the sidebar of this page or the meeting schedule page). You are also welcome to ask questions on the same channel at any time!

Posting here

In order to post to this site, you will need to log in with your wordpress.org account. Your first post may take a while to show up, as it is moderated. Please follow our tag policy when posting.

For many of us, we’ve always known WordPress as a global, multi-lingual, and multi-cultural endeavor. As of today (August 2020), we have over 200 locales into which WordPress is translated. Each locale is a representation of the community behind it – for every language, there is a community of WordPress enthusiasts.

But this wasn’t always the case! The Polyglots team, as it is now known, all began with this short, but meaningful post. Internationalization was first added in version 1.2 via the gettext() method, which we still use today. The first internationalized versions of WordPress we saw are tied back to the Hindi, French, Japanese, and Norwegian communities.

At the time, the translation process was much more manual and coordinated primarily via the wp-polyglots listserv. Translators would manually translate .po files (usually in a text editor or a desktop software like Poedit) and then generate the necessary .mo files using a script, and prepare an internationalized package by placing them on subversion. In late 2009, GlotPress was announced as the new tool for WordPress.com translation. Then in early 2010, WordPress.org locale teams started using translate.wordpress.org for core translation of WordPress 3.0.

Following the 2012 Community Summit, even more focus was placed on developing a global Polyglots community, around which many Polyglots-related efforts centered on the further integration of GlotPress and global coordination. During the same Community Summit, team representatives were developed to help with coordinating across WordPress teams and projects, which later paved the way for the Polyglots Global Mentors that we have today.

In 2015, the online translation mechanism of translate.wordpress.org became available for all plugins and themes in the WordPress.org directory, lowering the technical barrier for translation contributors.

In 2016, the first ever WordPress Translation Day was organized. The 24-hour event drew in nearly 500 people and was another step in the global organization and community building of the Polyglots team. There have been four additional Translation Days organized since, and we’ve even seen individual teams host their own translation days, including the French and Italian communities.

Last updated: August 18, 2020