Hi friends,
Over the last 6 months, the number of PTE A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves. requests has exploded. Typically, we now receive more PTE requests per day, than we previously had in a week.
We also see more and more machine translations being uploaded without first being checked by people, who actually know the target language well.
Some of these machine translations are surprisingly good, while many are still really bad.
Plugin 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. and theme developers expect GTEs to check and fix an enormous number of strings A string is a translatable part of the software. A translation consists of a multitude of localized strings., especially for the large and popular locales 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 https://make.wordpress.org/polyglots/teams/.
At the same time, we’re still just volunteers, with limited hours for our contributions. And we always have some dormant locales.
There are many things we need to improve:
- Can we push developers towards better interactions with the Polyglots’ team? How? Is there any point in the translation process where we could make sure that the developer understands our procedures and quality expectations before they make too big a mess?
- Can we improve the PTE request process? Currently, it’s just a blog, where we follow up by manually editing the posts. (And sometimes the requester by mistake remove their post from follow-up by ticking boxes or clicking buttons “out of turn”.
- Some locales are shifting their PTE request process towards two-way chat communication as a way to check language knowledge and provide translation feedback before approving the PTE role. How does this work? What to do if I push requesters to Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/, but the locale 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 https://make.wordpress.org/polyglots/teams/ team still doesn’t respond on Slack?
- The #ja team has a very structured style guide where they manage to quickly educate new translation contributors. What are your experience from this process? Do you get these good results thanks to how your style guide and your processes are done, or is this more a Japanese culture of being better at reading and following instructions in general?
- Can we make it easier for translators to roll back their pending strings in bulk?
- Can we make it easier for translation editors Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles:
General Translation Editor and Project Translation Editor to bulk reject/bulk approve large submitted translations without having to wade through page-after-page to handle each line separately, and without risking approving or rejecting strings from other contributors at the same time?
- Should we allow developers to provide machine translations via our central repository The WordPress Localization Repository at https://i18n.svn.wordpress.org/ is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details., but without them being added as approved strings in GlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org., and without forcing each plugin to distribute these translations within their plugin packages? Would this be possible? How?
- @psmits1567 has suggested automated checks that glossary terms are applied in translations. For which languages would this be useful? How would we need to change the glossary structure for this to work (where one English term may have several correct words or word forms, and where some glossary entries are more like hints than mandatory terms)? What to do for locales where enforcing glossary terms isn’t possible?
- Do we need to update our handbook? Are any needed things missing?
- Anything else we need to discuss?
Also: it would be nice to see and hear some of you!
So I suggest a video-meeting on Zoom on Saturday October 3, 2026 at 15 hrs UTC
Here’s an attempt to show the same time in your local time:
Saturday, October 3, 2026, 15:00 UTC
Mark your calendar. Add comments below. I’ll share the Zoom link in Slack just before our meeting.
Looking forward to seeing you,
Tobi