Welcome to the official blog of the translator 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ād love for you to help out!
Translate WordPress
You can help translate WordPress to your language byĀ logging in to the translation platform with your WordPress.orgWordPress.orgThe 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/ accountĀ and suggesting translations (more details).
We have meetings every week on 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). You are also welcome to ask questions on the same channel at any time!
Posting here
In order to post to this site, you will need toĀ log in with your wordpress.org account. Your first post may take a while to show up, as it is moderated. Please follow ourĀ tag policyĀ when posting.
Until now, a validatorValidatorSee translation editor. could not request changes from a translator. Since we have added the feedback tool, a validator can do this, so instead of rejecting a stringStringA string is a translatable part of the software. A translation consists of a multitude of localized strings., when a validator gives feedback to a translator, the status changes from ārejectedā to āchanges requestedā, so the translator can update the translation and then the validator can recheck it, to approve it.
When a validator (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., PTEProject Translation EditorA 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. or CLPTECross-locale Project Translation EditorAĀ Cross-LocaleĀ Project TranslationĀ Editor is an account owned by a plugin or theme author (or the authoring organization), which uses professional translators to localize 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.) is reviewing a suggested translation, she can approve, reject or mark as fuzzy the current translation, as we have been doing so far. But we have added a new element, the āGive feedbackā tool.
If you click on the text marked on the next image:
You will see some checkboxes where you can select a feedback type and a comment. Both fields are optional, so you can approve, reject or mark as fuzzy the current translation without adding feedback to this action.
If you select one checkbox and/or write some comment, you will see how the āRejectā button will change to āRequest changesā, because if you click in this new button:
The translator will receive a notification with the feedback.
The translation will be in a new status: āChanges requestedā.
Once you click on this button, you will see the translation with this new status (changes requested), and you can see thisĀ filterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. 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.Ā in the top bar.
You can also see this new status in the advanced filter:
This new status has its own color: light blue. You can see it in the next image, in a āchanges requestedā row and in the legend, at the bottom.
You can add feedback when you approve or mark as fuzzy one string.
As validator, you can also give feedback in a bulk rejection. To do this, you have to:
Select the translations to which you want to give feedback.
Select the āRejectā status.
Click on the āApplyā button.
Once you click on this button, you will see a new form, similar to the one you have in the single feedback tool. If you click on the āRejectā button, you will reject bothĀ stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings., as usual.
But if you select some reason and/or you made some comment, the āRejectā button will change to āRequest changesā.
Once you click on the āRequest changesā button, you can see these 2 strings in āchanges requestedā status.
You canāt add feedback when you bulk approve or mark as fuzzy some strings.