WordPress Help
Official documentation, learning resources, and contributor guides collected from WordPress.org.
-
translate.wordpress.org (GlotPress)
User Roles and Permissions First of all let’s take an overview on which kind of users can work on translate.wordpress.org. There are three user roles in translate.wordpress.org: Guest, Contributor, and Translation Editor. Guest Guests are all users who don’t have any account or are not logged into their WordPress.org account. Guests can see the projects…
-
Releasing WordPress Packages
Once your translation of WordPress for your language is ready, it’s time to release it so that users can select it on install, from their user dashboards, or download it from your local site (locale.wordpress.org). There are two ways to release translations: Automated Release Packages Manual Release Packages To-do
-
Working with the Translation Repository
The WordPress Localization Repository at i18n.svn.wordpress.org is a Subversion repository where official WordPress translations are maintained. The repository is used to store the source strings of WordPress core and the translations of plugins, themes and WordPress core. Some locales are also using it to customize WordPress core like adding a translated readme file or a…
-
Working with WordPress Core
In the Polyglots Contributor Training course, there are related content and quizzes. This page will discuss some of the basics of working with WordPress core, including references back to the Core Contributor Handbook, and information on working with comments, placeholders, and other things that are specific to localizing WordPress. Using Localizations One of the first things you should know…
-
General Expectations for Translators
As a translator, you want to make sure the language of the localized project is well-polished. Establishing and following translation rules might seem like a lot of extra work if you are just starting out. In fact, it helps cut the translation team’s workload by reducing the need for correction and clarification. Below are some…
-
Glossary & Style Guide
Keeping a consistent tone throughout your translation is important. We highly recommend that locale managers create both a glossary and style guide for their language. These needn’t be large or complex, but it’s important to cover the edge cases specific to your language. Glossary A glossary for translators is a list of terms with translations.…
-
Translator’s Handbook
Welcome to the Translator’s Handbook! The translator’s handbook will teach you everything you need to know about the Polyglots team and how we translate WordPress into different languages. This Handbook is organized according to the different roles that exist in the Polyglots community. For new translators, we recommend starting here before moving on to the…
-
Inactive Translations
There are two types of inactive translations: inactive locales and inactive translation editors. Inactive locales If a locale 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 Rosetta will note this. The local sites for these…
-
Current Translation Teams
Team Structure The Polyglots team is organized into translation teams focused on specific languages. Each team has three roles: General Translation Editors who are responsible for all projects in a locale. Project Translation Editors who are responsible for one or more projects in a locale Translation Contributors who can suggest, but not approve, strings in…
-
How We Work
The Polyglots team is organized into translation teams (locales) focused on specific languages, in addition to the global Polyglots team which organizes translation efforts more generally. Each locale has its own team leads and team reps to oversee and help with the day-to-day work. For more information on the roles within the Polyglots team, see…