Releases: 162 locales. 69 (+4) locales up to date. 1 (-2) locale behind by minor versions. 8 (±0) locales behind by one major version. 18 (-1) locales behind more than one major version. 59 (±0) locales have a site but never released. 7 (-1) locales don’t have a site.
Translations: 162 (±0) locales. 65 (±0) locales at 100%. 5 (±0) locales have more than 95%. 5 (+1) locales have more than 90%. 26 (-1) locales have more than 50%. 54 (+1) locales have less than 50%. 81 locales have a language pack. 81 locales have no language pack. 7 (-1) locales don’t have a WP project.
(Values in parentheses indicate change against previous week.)
We currently have 8 unresolved editor requests and 9 unresolved locale requests.
After setting up some first team sites with the O2-theme, Dominik (@ocean90) asks for feedback. One suggestion was to also announce the new team site locally so that everyone is aware it may officially be used. Please feel free to add more feedback in the comments.
The team sites don’t allow to run separate team pages. Users are encouraged to tag posts to makes it easier to distinguish teams.
Request for feedback on GlotPress shortcuts
Members of the Polyglots Team are kindly asked, to briefly give a feedback regarding Shortcuts for copying original strings in GlotPress, see GitHub issue https://github.com/GlotPress/GlotPress-WP/issues/554 .
Receiving contributions for translations
In the past couple of weeks several people asked Petya (@petya) if it’s ok to get paid to translate a plugin or a theme. She clarifies, that translating WordPress, including the free plugins and themes, is a contribution. There are a lot of people who get sponsored to contribute on the project, some people having all of their time covered. If someone would like to sponsor your time to work on a plugin or a theme, that’s perfectly ok. Refusing to translate the core software unless your time is covered would not be great, but also understandable. Not acceptable would be, if a General Translation Editor would refuse to work on a project unless sponsored while at the same time standing in the way of volunteers who would like to translate.
Global WordPress Translation Day 2 (November 12th) – video, website, official announcement, content, local events
So far six events already are planned for the 2nd Global WordPress Translation Day. (For more details see
If you are organising an event, please add it to the spreadsheet. New events will go into this map: https://drive.google.com/open?id=12Gni4JMfShyWHPqGNwh5-PMneMM&usp=sharing
Our website for the event will be again https://wptranslationday.org/. If anyone would like to help us out with the website, they should raise their hand – we’ll need content management and some tweaks here and there.
We also have our CrowdCast event set up and you can sign up. https://www.crowdcast.io/e/gwtd2
An official announcement for Global WordPress Translation Day 2 is planned for this week. It would be nice to see the announcement find its way to as many Rosetta sites as possible.
Reviving the Asia Pacific meeting
Petya (@petya) talked to Naoko (@nao) about reviving the Asia Pacific weekly Polyglots meeting. Meetings are scheduled for Wednesday, 6am UTC. The next meeting will also be announced via local Slack channels and with an extra post on the Polyglots blog.
The question came up, how we deal with translations of Child Themes, if the Parent theme has been removed from the WordPress directory. As the theme still may be available through other sources, there are no reasons not to translate their Child Themes. It was considered to add a ticket on Trac for further discussion, if some information about should be displayed on translate.wordpress.org that contributors deal with a child theme.