As described in After Your Contribution page, translations need to be reviewed and approved before they become available.

A General Translation EditorGeneral Translation Editor A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale. (GTEGeneral Translation Editor A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale.) can moderate translations and 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 https://make.wordpress.org/polyglots/teams/ Manager (LM) can appoint a user as Project Translation EditorProject Translation Editor 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. (PTEProject Translation Editor 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.) in the backend of the RosettaRosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. site. There are two types of users who may request a review and/or PTE status:

• The relevant 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party/theme author
• A translator

As a plugin/theme author whose project is on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ plugin/theme directory, you can nominate existing active translators to become PTEs for your project.

As a translator who understands and meets our General Expectations, you can request to become a PTE of any plugins, themes, or metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. projects. You don’t need approval from plugin/theme authors to become PTEs for their projects, since it’s the Polyglots community’s responsibility to manage the translation of all the projects hosted on WordPress.org directories.

In both cases, note that many language teams have their own validation process to make sure that contributions from a translator have acceptable quality before a PTE role is granted. It’s best to check your team’s start guide or other relevant translation documentation first. 

For Translators #For Translators

If you are a translator, you may request PTE status by following the steps and sample text listed in the After Your Contribution page.

Likewise, if you are a plugin or theme author, you can help your contributors to request PTE status by encouraging them to follow the instructions and steps listed in the After Your Contribution page.

Top ↑

Plugin/Theme Author Translation Review/PTE Request #Plugin/Theme Author Translation Review/PTE Request

To request a translation review or PTE assignment to your plugin/theme, follow the instructions below:

1. Log in to WordPress.org.
2. Go to https://make.wordpress.org/polyglots/.
3. Copy and paste the text below and modify as needed. Multiple plugins can be listed in the initial sentence.

(Post Title) PTE Request for [PLUGIN_NAME]

I am the plugin author for [plugin Name(s)]. We have a number of great translation editors that we'd like to be able to approve translation for our plugin(s). Please add the following WordPress.org users as translation editors for their respective locales:

[link(s) to plugin directory, e.g. https://wordpress.org/plugins/hello-dolly/]

o #ar – @username
o #bn_BD – @username, @username
o #da_DK – @username
o #de_CH – @username
o etc...

If you have any questions, just comment here. Thank you!

Please remember the GTE/Locale Managers who review translations and grant permissions are volunteers. It may take some time for them to respond to your request.

For more information, please refer to the Plugin/Theme Authors Guide.

Top ↑

Cross-Locale Project Translation Editor #Cross-Locale Project Translation Editor

A Cross-Locale Project Translation Editor (CLPTE) is an account owned by a plugin or theme author (or the authoring organization), which uses professional translators to localise their product. The cross-locale project translation editor can import/validate strings on a specific project for more than one locale. This role has the same capabilities as a Project Translation Editor over multiple locales instead of one. Cross-Locale Project Translation Editors need to meet a set of criteria before being appointed by General Translation Editors.

Criteria for a Cross-Locale Project Translation Editor #Criteria for a Cross-Locale Project Translation Editor

To be granted access to import/validate strings for more than one locale, an organisation/plugin/theme author must cover the following criteria:

1. Make sure that the translators they hire use the community style guides and glossaries or create ones based on them and provide public links.
2. Create a new translator account for this role (examples), and fill in its profile page with contact information so that the local translation teams can get in touch.
3. Disclose the sources of translation (e.g. translation vendor) and reviewers (.org username) on the description of the new WordPress.org account.*
4. List steps for other .org community volunteers to get involved in the review process.
5. Have a Slack account on chat.wordpress.org and provide notice to the General Translation Editors of each locale after imports.
6. Update their WordPress.org name to indicate that this user is a CLPTE. For example, “XYZ Translation Team (CLPTE)”.

*Note: Our general expectations also apply to translators working for a CLPTE. Please make sure you understand that machine translation without human review by a speaker of the language will NOT be considered as an accepted source.

Last updated: July 7, 2021