Welcome to the official blog of the translators team for the WordPress open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project.
This is where we discuss all things related to translating WordPress. Follow our progress for general updates, status reports, and debates.
We have meetings every week and at various hours every week. Check SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. in #polyglots (the schedule is on the sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. of this page or the meeting schedule page). You are also welcome to ask questions on the same channel at any time!
There are two types of inactive translations: inactive localesLocaleLocale = 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/ and inactive translation editorsTranslation EditorTranslation 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.
If a localeLocaleLocale = 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/ is two or more major versions behind (for example, WordPress is at version 5.5 and the last released language version is 5.3), the locale is automatically considered “inactive” and RosettaRosettaThe 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. will note this.
The local sites for these locales display an automatic message which states that the translation is inactive. The message cannot be removed manually. However, it will disappear automatically after the locale releases a language pack for the most current WordPress version.
Sometimes, individuals start translating WordPress but aren’t able to complete it or keep all the translation projects up to date. In some cases, review requests are left without attention or simply rejected without clear explanation.
When this happens, the contributor might be considered “inactive” and the translation needs to be kickstarted by a new contributor, who can be added as a translation editorTranslation EditorTranslation 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.
If you would like to become a translation editor of an inactive translation, please read carefully and follow these steps:
Step 1: Attempt to contact current General Translation EditorGeneral Translation EditorA 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.(s).
First try to use the contact form of your local site (ex. If you’d like to translate in Bulgarian, use the contact form on http://bg.wordpress.org)
A quicker way to get in touch is to contact the translation editors directly. On the list of current teams, the “Team” link will lead you to the locale’s page where you will find a list of the current Translation Editors. Look for their SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. names and try to contact them on the WordPress Slack Team in the #Polyglots channel.
Some Translation Editors don’t leave contact information on their profiles. If that is the case, go to https://make.wordpress.org/polyglots and write a post, mentioning the translation editors’ username (ex. @petya). In that post, explain you’d like to get involved and ask them to add you as a translation editor. The translation editors should get an email notification because you mentioned them in the post.
Note: It’s possible that the team is not inactive but simply delayed for some reason. Please be patient and give the translation editors at least a week to respond.
Step 2: Contact a Polyglots teamPolyglots TeamPolyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. lead. If you don’t hear back from a Translation Editor after a week, contact a Polyglots team lead (again, by posting on make/polyglots) and let them know the steps you’ve taken so far and that you haven’t heard back, or that you have heard back from a Translation Editor and they are no longer working on translating WordPress.
Note: Global mentors may assign additional GTEGeneral Translation EditorA 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.(s) if there are signs that the team doesn’t function properly, for instance hasn’t released any coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. package for more than one year.
Step 3: Polyglots team lead contacts current Translation Editor(s). The Polyglots team lead will also make a final effort to get in touch with them.
After these steps have been taken, if no response has been given, a Polyglots team lead will vet the candidate and make the translation editors change in the local site, enabling the new contributor to validate their translations and the translations of others.
Added a note about the condition Global ,entors may step in under the step 2 section in “Inactive translation editors”.