Notes from the Polyglots chat on September, 21st

Locale stats

Releases: 162 locales. 65 (+3) locales up to date. 3 (-2) locales behind by minor versions. 8 (±0) locales behind by one major version. 19 (-1) locales behind more than one major version. 59 (±0) locales have a site but never released. 8 (±0) locales don’t have a site.

Translations: 162 locales. 65 (±0) locales at 100%. 5 (±0) locales have more than 95%. 4 (±0) locales have more than 90%. 27 (±0) locales have more than 50%. 53 (±0) locales have less than 50%. 8 (±0) locales don’t have a WP project.

(Values in parentheses indicate change against previous week.)

Two locales are waiting for system issues to be resolved to release. We’ll have our first Khmer release and the Czech team is waiting to manually release.

We currently have 15 unresolved editor requests and 9 unresolved locale requests.

For statistic references, request should be tagged as editor request and the locale, too. (e.g. editor requests, nl_NL, en_GB, de_DE)

Tech update

We have had technical issues with the servers last week, which now are solved.


A new GlotPress version will be released next week, a beta was release Monday. (For more information see
The new version includes locale updates like the Latin version of Hausa and will include a fix for translations which are using the placeholder for tab characters (see still uses an old version because of a pending systems requests. Dominik (@ocean90) hopes to sort that out soon.

The next release will focus on glossaries, enhanced queries, support for Cross-Locale PTE and maybe JS localization. Milestone:

Team Sites

The first rollout of team sites will include following sites:


Some highlights:

  • Uses o2
  • Editors from the base site are also editors on the team site
  • Any registered member can post. For unknown users the post is set to pending. (like make/polyglots)
  • Autocomplete for -mentions
  • ToDo module (like make/polyglots)
  • Editors can change theme settings and site title in the customizer

All existing Editors on the base site are now Locale Managers. They have the same permissions as the previous Editor role and GTE. Locale Manager is now the top access level for a Rosetta site and a locale. Editors now can only edit content on Rosetta sites and GTEs can only approve translations and don’t need to be involved in Rosetta or writing for the community. Locale Managers can do manual releases of translations.

There are some CSS issues for RTL sites, that will be fixed. Also, if you find any bugs you can report them here or on

A page regarding team sites will be added to the Polyglots Handbook.

The German Polyglots team has an old team blog on Dominik (@ocean90) will import it’s content to the new site. Dominik also asks Polyglot teams to ping him, if they want content imported, too.

WordPress theme Twenty Seventeen

The new WordPress theme Twenty Seventeen, beautifully designed by @melchoyce, has been announced. Mel would like to take into account non latin characters for the font and figure out how to avoid what many of us have experienced with default themes before. There’s an issue opened for this
Petya (@petya) has listed script families we need to take into consideration. Mel is looking for developers who are also polyglots to help out with that part.

Global WordPress Translation Day 2

Petya created an Organizing spreadsheet, which can be accessed via–GaJZFoxCqb6NHBl2QYv4lH3Y6inIGBwr5Ln9SIaic/edit#gid=1512653702
The spreadsheet outlines many tasks. Take a look and if there’s something you’d like to pick up, please put your name down. We’ll do local/remote events like we did the last time – if you’d like to organize an event, put your name and location down.

Here are some roles you can take on:

  • Local organizer – organize an event in your city
  • Remote event organizer – take on helping people speaking your language from a remote location in set hours
  • Speaker – do a session about translating WordPress in your language
  • Reaching out to local communities and encouraging them to organise a local event
  • Helping figure out the sessions – what sessions did we have last time, what sessions do we want this time
  • Promo video – you can take on the role of reaching out to people and gathering the videos
  • Promo video production – create the video from the videos everyone sends


  • post about GWTD on make/polyglots announcing to the team and calling for help (@petya) (@petya)