Quick Start
Ready to get started? Here is a summary of the steps to begin translating WordPress:
- Review your 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/’s Style Guide, Glossary, and/or any related documentation on 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, which you can find via the Teams page.
- Log in to 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/ via translate.wordpress.org.
- Find your locale and click Contribute Translation.
- Open the project you’d like to translate and begin suggesting translations.
- When finished, post a request for a review in the appropriate channel, e.g. your locale team’s local Slack or the Make/Polyglots blog.
That’s it! Welcome to the Polyglots community. We’re glad to have you help us make WordPress speak your language.
Was this information helpful? Download the Quick Start guide for easy reference!
Before you get started
Coordinating translations for a project as large as WordPress is complex. Volunteers and community leaders have put a lot of time and energy into creating documentation to help you get started as quickly and efficiently as possible. This helps maintain the best quality translation for WordPress users while also encouraging contributions from new translators, like you!
To improve the chance of having your translations approved the first time, it is recommended that you:
- Check your locale’s website for any documentation about how to translate and where to communicate. Some locale teams have specific guidelines for translators, and taking this step helps prepare you for your first contributions.
- Actively communicate with the other people in the team for your locale. This way, your translation efforts will be more efficient and have better total quality.
- Review your locale’s Style Guide or Glossary to make sure your translations help to maintain consistency across the locale.
- When translating, keep the general expectations on translations in mind.
If you are new to the Polyglots community, introduce yourself – either in your local Slack or in the global polyglots channel on the WordPress.org Slack. It is a good way to connect with other translators and get initial feedback or advice on what to do next.
Contributing your first translations
You can start suggesting translations by following these steps:
- Log in to WordPress.org or create a new account.
- Go to translate.wordpress.org.
- Find your locale and click Contribute Translation.
- Select the type of project (WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., Themes, Plugins, Patterns, 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., or Apps).
- Click the Translate Project button for one of the listed items.
- Select one of the items under Set / Sub Project (Clicking on the number under Untranslated will bring you directly to the untranslated stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings.).
- Here, you will see a list of strings. To contribute your translation, click the Details link on the stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. to translate. You can also double-click the row to open the translation editorTranslation Editor 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.
- Enter your translation, then click Suggest new translation.
Great! You made your first contribution to WordPress 🎉 What’s next?
I submitted a translation. Now what?
When a new string is submitted, or an old one updated, it must be reviewed and approved by 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.) for that locale or 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.) for that combination of the translation project and locale (for instance, Contact Form 7 in es_MX) before the translation becomes available.
You will need to contact the reviewers (Translation EditorsTranslation Editor 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 request a review because they are not automatically notified when changes are made.
To request a translation review:
- Check your locale team’s Rosetta site, e.g. br.wordpress.org, for a Handbook or Get Involved page. This is where you can often find instructions on how the team handles translations.
- Check for your local Slack instance if you cannot find any instructions. Many translation teams will have a #polyglots or #translation channel in the local SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. where you can ask for a review.
- If you cannot find any information, please make a request on the global Polyglots team blog. Be sure to add the related tag for your locale, such as #es_MX or #ja, as this will send an email notification to the translation editors for your locale.
Making a PTE request (Template)
Rather than just requesting a translation review, you may wish to become a Project Translation Editor for a specific theme or 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. This will allow you to review (approve/reject) Waiting and Fuzzy translation suggestions.
Check your locale team’s Rosetta site and documentation for specific instructions on requesting PTE status in your language. If you can’t find any specified instructions, you can also make the request on the global Polyglots teamPolyglots Team Polyglots 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/. blog by following these instructions:
- After submitting your translations, go to https://make.wordpress.org/polyglots/.
- Copy and paste the text below and modify as needed. Multiple projects can be requested in one post.
- You are welcome to ask in #polyglots if you have any follow-up questions about your request.
(Post Title) PTE Request for [PLUGIN_NAME] I’ve suggested translations for this [plugin/theme] and would like to have them reviewed. I’d also like to become a PTE. I also confirm that I've read the style guide and/or glossary for the [locale name] locale. Name: [Plugin or Theme name(s)] URL: [Plugin or Theme URL(s)] o #de_CH
In the example above, the WordPress locale code for German (Switzerland) is shown, #de_CH
. You can find your locale’s code on the Translation Teams page in the WP locale column. The locale team will be automatically notified when a correct code is added to your post.
What if no one responds to my request?
It’s possible that you will request a translation review, or even PTE status, and no one will respond to your request. Don’t worry! GTE/Locale Managers who review translations and grant permissions are volunteers. It may take some time for them to respond to your request.
Sometimes, a locale team may become inactive. If you suspect this is the case, please follow the steps in the Inactive Translations Handbook page:
- Attempt to contact your locale team via the methods described above.
- If you don’t hear back after one week, post on the global Make/Polyglots team blog and @-mention the translation editors directly in that post to ensure they receive the notification.
- If you still don’t hear back after one week, reach out to one of the Polyglots Global Mentors or Team Reps for help by commenting on your post and @-mentioning anyone listed on the Polyglots Global Team Leads and Mentors page.
At this point, one of the Polyglots team leads will attempt to reach out ot the locale team once more. If there is still no response, you will then be vetted and potentially added as a translation editor to the locale or project.
Receiving feedback
translate.wordpress.org now includes a built-in feedback tool where you can receive feedback on your suggested translations. To receive email updates for any feedback you receive, go to your Translation Settings and opt-in to I want to receive notifications of discussions:
A translation editor may provide feedback on your translation when it doesn’t meet certain guidelines set by the locale team. These may include:
- Not following the style guide or glossary
- A typo
- Grammatical errors
If a translation editor notices any of these issues, they may either reject the string or send you feedback, changing the string’s status to “Changed Requested.” You can reply with any questions or concerns within the discussion thread for that string, accessible via the hamburger menu.
If one of your suggested translations has changes requested, you can follow the same process to submit a new translation and request another review from the translation editor.
Please note that all discussions on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. are public.
When will I see my translations?
Once your translations are approved, they will be available as soon as a language pack is generated for the project. Each project type has a different threshold to trigger a language pack. Below, you can find some general information.
Once you have a string approved on translate.wordpress.org, the Translation ContributorTranslation Contributor Translation Contributors (formerly known as Translators) are volunteers that focus on translating projects into their language. They contribute to improving their language either in a small way, like fixing a typo, or a large way, likes translating entire projects. badge will appear on your WordPress.org profile.
Plugins, Themes, and Meta Projects
The first language pack for the plugin and themes will be generated when 90% of the Stable (latest release) sub-project strings have been approved.
The threshold at 90% does not apply if a corresponding language pack exists before – any string changes will trigger the creation of an updated language pack, even if the number of translated strings in the plugin or theme has fallen below the threshold since the initial language pack was created.
Plugin readme translations are updated string-by-string after they are approved, without any specific thresholds. Translations for “meta” projects are deployedDeploy Launching code from a local development environment to the production web server, so that it’s available to visitors. at various intervals.
WordPress Core
For a new language pack to be generated for each version of the WordPress core translation project, the translation of the front-end project needs to be at 90% and 75% for the Administration project. For more information about core language pack generation, read Releasing WordPress Packages.
For more details of the package creation timing, check this FAQ answer.
Mobile Apps
A new version of the app is released every two weeks, and the schedule is posted on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ (iOS/Android). You can find some more info about the release schedule/process in this post.
You must be logged in to post a comment.