There are three user roles in translate.wordpress.org: Guest, Contributor, and Translation EditorTranslation Editor<\/span> 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: \nGeneral Translation Editor<\/a> and Project Translation Editor<\/a><\/span><\/span><\/span>.<\/p>\n\n\n\n Guest<\/strong><\/p>\n\n\n\n Guests are all users who don\u2019t have any account or are not logged into their WordPress.orgWordPress.org<\/span> 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\/<\/a><\/span><\/span><\/span> account. Guests can see the projects and their translations but can\u2019t suggest translations or add them to the already translated set of stringsString<\/span> A string is a translatable part of the software. A translation consists of a multitude of localized strings.<\/span><\/span><\/span>.<\/p>\n\n\n\n Contributor<\/strong><\/p>\n\n\n\n Contributors can suggest translations and see other translations of the same strings, suggested by other users. To become a contributor, you need to register<\/a> or log in<\/a> to your WordPress.org account.<\/p>\n\n\n\n Translation Editor<\/strong><\/p>\n\n\n\n Translation EditorsTranslation Editor<\/span> 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: \nGeneral Translation Editor<\/a> and Project Translation Editor<\/a><\/span><\/span><\/span> can add translations, manage suggestions, and approve or reject suggested translations. If you\u2019d like to become a Translation Editor for a current localizationLocalization<\/span> Localization (sometimes shortened to \"l10n<\/b>\") is the process of adapting a product or service to a particular language, culture, and desired local \"look-and-feel.\"<\/span><\/span><\/span>, you\u2019ll need to contact the current General Translation Editors<\/a> requesting access. If you\u2019d like to become the General Translation EditorGeneral Translation Editor<\/span> 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.<\/strong><\/span><\/span><\/span> of a new localization of WordPress, review the \u201cRequesting a New Locale<\/a>\u201d page.<\/p>\n\n\n\n So be ready to give your first translation suggestions like a Contributor!<\/p>\n\n\n\n To contribute translations using translate.wordpress.org, simply log in<\/a> (or register an account<\/a>) to your WordPress.org account. This automatically gives you the necessary permissions to contribute to any translation projects.<\/p>\n\n\n\n Once logged in, go to https:\/\/translate.wordpress.org\/<\/a>, you\u2019ll see a list of localesLocale<\/span> Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it\u2019s used in Mexico. A list of all locales supported by WordPress in https:\/\/make.wordpress.org\/polyglots\/teams\/<\/a><\/span><\/span><\/span>. Search your localeLocale<\/span> Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it\u2019s used in Mexico. A list of all locales supported by WordPress in https:\/\/make.wordpress.org\/polyglots\/teams\/<\/a><\/span><\/span><\/span> and click on \u201cContribute Translation\u201d.<\/p>\n\n\n\n We\u2019ll use Peruvian Spanish (and some others) as an example on this page.<\/p>\n\n\n\n translate.wordpress.org organizes translations in projects and sub-projects so that you could have, for example, the \u201cWordPress\u201d project and a sub-project for every version, as seen in the example below.<\/p>\n\n\n\n If this is your first time translating for the WordPress project, we recommend you start by translating the WordPress project by clicking the \u201cWordPress\u201d tab in the darker gray navigation bar.<\/p>\n\n\n\n Search \u201cDevelopment\u201d and click the \u201cTranslate Project\u201d button. You\u2019ll see a list of components (\u201ctranslation sets\u201d).<\/p>\n\n\n\n Pick a translation set you\u2019d like to translate by clicking on its title. In the screenshots below, we\u2019ll use the \u201c5.4.x \u2013 Development\u201d set.<\/p>\n\n\n\n Before going ahead, note that at the beginning projects can be filtered by their translations status like \u201cPercent Completed (Most first)\u201d, \u201cWaiting + fuzzy (Newest first)\u201d , \u2026 from the menu \u201cFilterFilter<\/span> Filters are one of the two types of Hooks https:\/\/codex.wordpress.org\/Plugin_API\/Hooks<\/a>. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.<\/span><\/span><\/span>\u201d you see above \u201cSearch projects\u2026\u201d field. Choose one filter and click on \u201cApply filter\u201d.<\/p>\n\n\n\n For plugins and themes you can also choose from your favorite ones:<\/p>\n\n\n\n Now that you\u2019ve selected the locale and the set, you\u2019ll see a list of strings to translate. By default, high priority and untranslated strings will be shown at the top.<\/p>\n\n\n\n Across the top of that list, you will see links to the filtering (click on \u201cFilter\u201d) and sorting (click on \u201cSort\u201d) functions which will help you narrow down the strings you want to work on. And some quick filters which allow you to see All strings, only Translated strings, only Untranslated strings, only Waiting strings, only Fuzzy strings, only strings with Warnings.<\/p>\n\n\n\n If you click on \u201cFilter\u201d you can do advanced filtering based on the options that you see in the image below.<\/p>\n\n\n\n If you click on \u201cSort\u201d you can do advanced sorting based on the options that you see in the image below.<\/p>\n\n\n\n Each stringString<\/span> A string is a translatable part of the software. A translation consists of a multitude of localized strings.<\/span><\/span><\/span> has a \u201cstatus\u201d, indicated by the background color of the row.<\/p>\n\n\n\n To start translating a string, double-click on the one you want to translate (or click on \u201cDetails\u201d in the right column).<\/p>\n\n\n\n As seen below, the string\u2019s line will expand and you\u2019ll be presented with a text box where your translation can be written. In the example below you\u2019ll insert your translation where it says \u201cEnter translation here\u201d.<\/p>\n\n\n\n Let\u2019s take a tour of the box translation interface.<\/p>\n\n\n\n In the headerHeader<\/span> The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor\u2019s opinion about your content and you\/ your organization\u2019s brand. It may also look different on different screen sizes.<\/span><\/span><\/span>, the top bar has some useful information and some additional functions in the hamburger menu on its right.<\/p>\n\n\n\n From left to right we have:<\/p>\n\n\n\n Contextual links menu (hamburger menu):<\/p>\n\n\n\n In the main area of the translation there are additional information for the string, before and after the translation box itself:\u00a0<\/p>\n\n\n\n At the right of the main area of this box we have some MetaMeta<\/span> 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.<\/span><\/span><\/span> information:<\/p>\n\n\n\n In the translation box the \u201cCopy original\u201d button present in the left bottom corner will do just that \u2013 copy the source string to the text box. In some cases and languages, it\u2019s easier to translate from the original string. In both cases, don\u2019t forget to click the \u201cSuggest\u201d<\/strong> button. The \u201cShow help\u201d button in the left bottom corner shows you a help dialog with useful information on translating in translate.wordpress.org.<\/p>\n\n\n\n Type your suggestion for the translation and click the \u201cSuggest\u201d<\/strong> button.<\/p>\n\n\n\n Once your suggestion is sent, the translation area of the next string will be opened.<\/p>\n\n\n\n Suggest as many or as few strings as you want. Be aware that the same string can have any number of different suggestions, from different users. It will be up to the Translation Editors to decide which one fits best.<\/p>\n\n\n\n If you edit one of your pending suggested strings and make a new suggestion, then your previous, pending string is rejected automatically.<\/p>\n\n\n\n Some original strings will have some terms underlined by dots. If you hover on those with the mouse pointer you can get the translation suggested by your locale glossary.<\/p>\n\n\n\n In the examples above, the tooltip content is from the Spanish-Peru locale glossary<\/a>.<\/p>\n\n\n\n Some glossary entries also have notes in the Comments field that are useful to give more information or to give more translation choices, based on the context or the meaning of the original term.<\/p>\n\n\n\n Some original strings will have one or more plural forms. In this case, you have to insert all the forms by clicking on Singular and Plural tabs.<\/p>\n\n\n\n In some locales we have more than two forms, for instance in Russian:<\/p>\n\n\n\n If your locale doesn\u2019t distinguish singular and plural forms, there won\u2019t be any tabs (like in the example below). Just use the placeholder + translation to represent all forms (e.g. \u201c%s item selected\u201d \u2013 %s will display any number including 1).<\/p>\n\n\n\n In some locales we have the RTL writing mode, it could be activated by clicking the \u201cEditor LTR\u201d icon.<\/p>\n\n\n\n After a contributor suggests a string, the string gets a status of \u201csuggested\u201d (waiting). In order to transform them into \u201capproved\u201d (current) strings, which are the only ones that are used to create the language pack that will be downloaded to your WordPress website, a Translation Editor needs to approve those suggestions using the \u201cApprove\u201d button that appears in the Meta area of an Editor interface\u2019s screen. An Editor can also reject a string using the \u201cReject\u201d button. Or give it the status of Fuzzy when there are some doubts on that string.<\/p>\n\n\n\n For more information on the process after translations are suggested, check out the How to translate<\/a> page.<\/p>\n\n\n\n For more information on the process of validating suggestions as a Translation Editor and to watch a useful video about it, check out the You\u2019re an editor! Now what?<\/a> <\/strong>page.<\/p>\n\n\n\n If your language is listed in translate.wordpress.org, chances are there is a team localizing WordPress into your language. Visit the list of current localization teams<\/a> to find your local Translation Editor (then go to the Translation teams page<\/a> and click the \u201cView Team Page\u201d link of your language).<\/p>\n\n\n\n You could find how to contact translation Editors in your locale in the \u201cCurrent Translation Teams\u201d page<\/a>.<\/p>\n\n\n\n If your language is not yet listed, follow the instructions for requesting a new locale<\/a>.If your language is listed, contact your Translation Editor. <\/p>\n\n\n\n If you are unable to do it, it\u2019s possible that your translation team is currently inactive. In that case, follow the process for inactive translations<\/a>.<\/p>\n\n\n\n Any WordPress.org user can import pluginPlugin<\/span> 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\/<\/a> or can be cost-based plugin from a third-party.<\/span><\/span><\/span> and theme translation files using the \u201cImport Translations\u201d feature of GlotPressGlotPress<\/span> GlotPress is the translation management software that powers\u00a0Translate.WordPress.org<\/a>. More information is available at glotpress.org<\/a>.<\/span><\/span><\/span> (Note: only GTEs can import into projects other than plugins and themes).\u00a0<\/p>\n\n\n\n Multiple formats are allowed to be imported (including for example .po and .moMO files<\/span> MO, or Machine Object is a binary data file that contains object data referenced by a program. It is typically used to translate program code, and may be loaded or imported into the GNU gettext program. This is the format used in a WordPress install. These files are normally located inside ...\/wp-content\/languages\/<\/span><\/span><\/span> formats).<\/p>\n\n\n\n To access the import feature, scroll down on a translation page and click the \u201cImport Translations\u201d link.<\/p>\n\n\n\n GTEs and PTEs can upload translations as \u201cCurrent\u201d or \u201cWaiting\u201d status. Others can only upload as \u201cWaiting\u201d.<\/p>\n\n\n\n When you import a file, untranslated strings and translations which are different from existing translations will be saved. If the imported file contains original strings not present in the string list of translate.wordpress.org, those will be ignored.<\/p>\n\n\n\n What WordPress.org users can import:<\/p>\n\n\n\n You can download a file with all current translations or with the strings matching the filter you have set.<\/p>\n\n\n\n To access the export feature, scroll down on a translation page of a project or sub project, select which strings to download, the format and click the \u201cExport\u201d link.<\/p>\n\n\n\n Make sure to have applied a filter and to have selected \u201conly matching filter\u201d if you want strings other than currents.<\/p>\n\n\n\n If you while validating suggested strings get a warning message that says \u201cError setting status!\u201d then something is disturbing the communication between your browser and the server. In some cases this has happened if the URL of the translation project contained the word \u201cad\u201d and the user had an ad-blocker activated.<\/p>\n\n\n\n GlotPress<\/a> is the open-source engine that powers translate.wordpress.org \u2013 the translation platform of WordPress and related projects.<\/p>\n\n\n\n GlotPress is an open-source project, just like WordPress. If you\u2019d like to help improve GlotPress please visit the GlotPress blog<\/a> or the GlotPress Trac<\/a>. Contributions to GlotPress will be used by hundreds of people who translate WordPress for millions of people around the world.<\/p>\nGetting Started<\/h2>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-1-1024x787.png\"){kind=spacer}
<\/figure>\n\n\n\nChoosing a Project<\/h2>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-2-1024x787.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-3-1024x770.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-4.png\"){kind=spacer}
<\/figure>\n\n\n\nFiltering Projects by their translation status<\/h3>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-5.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-5-1.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-5-2.png\"){kind=spacer}
<\/figure>\n\n\n\nTranslating Strings<\/h2>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-6-1024x803.png\"){kind=spacer}
<\/figure>\n\n\n\nFiltering and sorting strings<\/h3>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-7.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-8.png\"){kind=spacer}
<\/figure>\n\n\n\nStrings Status<\/h3>\n\n\n\n
Strings Status Color Key<\/h3>\n\n\n\n
\n
Suggesting new translations<\/h3>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-9.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-10.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-11.png\"){kind=spacer}
<\/figure>\n\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-12.png\"){kind=spacer}
<\/figure>\n\n\n\n\n
\n
\n
Correct your own translation<\/h3>\n\n\n\n
Glossary Tooltip<\/h3>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-16.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-17.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-18.png\"){kind=spacer}
<\/figure>\n\n\n\nTranslations with plurals<\/h3>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-19.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-20.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-21.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-22.png\"){kind=spacer}
<\/figure>\n\n\n\nTranslations for RTL locales<\/h3>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-23.png\"){kind=spacer}
<\/figure>\n\n\n\nApproval of Translations (Validating)<\/h2>\n\n\n\n
Find your Local Translation Editor<\/h2>\n\n\n\n
Become a Translation Editor<\/h2>\n\n\n\n
Importing External Files<\/h2>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-24.png\"){kind=spacer}
<\/figure>\n\n\n\n![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-25.png\"){kind=spacer}
<\/figure>\n\n\n\n\n
Exporting files<\/h2>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2020\/08\/translate-wordpress-org-26.png\"){kind=spacer}
<\/figure>\n\n\n\n\u201cError setting status!\u201d<\/h2>\n\n\n\n
![\"\"](\"https:\/\/make.wordpress.org\/polyglots\/files\/2021\/12\/error-setting-status-1024x373.png\")
<\/a><\/figure>\n\n\n\nContribute to GlotPress<\/h2>\n\n\n\n