Notes from the Polyglots chat on June, 1st

LocaleLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in stats

Releases: 162 localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in 65 locales up to date. 0 locales behind by minor versions. 12 locales behind by one major version. 15 locales behind more than one major version. 61 locales have a site but never released. 9 locales don’t have a site.

Locales up to date changed from 61 to 65! Yay!

Translations: 162 locales. 65 locales at 100%. 2 locales have more than 95%. 3 locales have more than 90%. 22 locales have more than 50%. 60 locales have less than 50%. 10 locales don’t have a WP project.

Change: +3 new locales at 100%. -1 locales have more than 95%. -2 locales have more than 90%. Indonesian is at 100% too but has no latest release. @ocean90 will take a look.

Technical updates

An graphical overview of all locales can now be found at

Cross locale PTEs

We had a discussion based on @nao’s post and the comments below:

The Italian Community has agreed in their meeting to the following

  • we do not oppose the initiative of cross-locale PTEs
  • we are neutral with regards to the trial, willing to help if it should be a go, but ok even to just go without it
  • we feel developers should be free to decide whether or not to translate directly or to pass through the community; both has advantages and disadvantages
  • we think that the community, though, should cater to those who decide not to proceed with their own translation and therefore should not be asked/required to work (voluntarily) on projects that are being translated by paid professionals. For this reason we encourage the development of a specific team that could supervise this work. This solution would free up resources in the Community and at the same time allow for Devs the opportunity/freedom to make whatever choice they deem in their best interest
  • we think that the translations should be “signed” in some way as being “proudly provided by the Community” or provided by Dev/whomever. This will induce a clearer view as to the quality of the work (and also gratify the work of the Polyglots”
  • obviously style guides, glossary and indications will be freely shared and Devs encouraged in asking their translators to follow them
  • the “pro-*TE” team could also randomly test and verify translations periodically to assure quality standards are kept high
  • this way, we feel, we could allow both the freedom for the Developers and the standards of the platform, giving value to the work of the Community and of all parts in the process

Much of the following discussion was about keeping standards up without putting added abnormal work on community resources.

  • Does the polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. has resources and wants to review translations, that have been contributed from outside the community?
  • How should feedback be provided and what should happen, if third party translations don’t meet our standards?
  • Do we offer feedback to a translator or an account that doesn’t speak our language? Are we speaking to a person who has to report it to another? Will that be the person who made the translation?
  • Is a review by the community “required”? (Suggesting receiving feedback is a key to improve the quality at least during the onboarding period.)
  • Can we keep standards up without adding too much work on community resources?
  • Community translations are always welcome and preferred. PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party users know more about the context. But at the same time because of limited resources we can’t rely on the community for every plugin release.
  • Professional translators should be seen as a possibility to fuel translation percentages, not to replace community.

Everybody is invited to add further comments to @nao‘s blog post.

Next step should be to finalize criteria to grant permissions for Cross-PTEs (during the discussion also referred to as pro-PTEs). Also needed is a list of criteria for adding potential trial plugins and trial periods and ways to monitor imports. @nao will set up a handbook page for review next week.

Status of the Handbook FAQ page

As the FAQ is a living document, the content of the Google Document can be moved into a handbook page. There is no need to wait until WCEU.

Global WordPress Translation Day videos on

@casiepa couldn’t attend the meeting in person, but left a note that the WordPressTV-Team is still finalizing the last videos. Around 17 are already visible. When all are there, @casiepa asks that someone goes over them and check descriptions, to make sure it’s all OK.

Open discussion

@ocean90 reminded, that locale being interested in being first to upgrade should report back on the blog post. Qualifications include moderator consensus and having fewer than 10k combined topics and posts. (Sorry, Germany and Russia.)

The Italian community has worked on a PTE Bot. More information can be found here:

#weekly-meeting-notes, #weekly-meetings