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!
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!
Skeleton for the locale-based PTE Onboarding process
Alert: This is a skeleton for local sites. 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/ manager can use and adjust it for their locale team guidelines. Please replace [YOUR LOCALE] with your locale. Example: How the German community handles 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. requests.
How the [YOUR LOCALE] community handles PTE requests
Following the path of some other locales, here are the guidelines for all WordPress Translators who wish to have their favorite products (themes, plugins) localized in [YOUR LOCALE], to give it a wider chance to be adopted by [YOUR LOCALE] users.
In order to assure the best possible quality for all translations (and therefore for the products you so dearly worked on to translate), we have established a few rules to grant you PTE (Project Translator Editor) status for the project(s) that interest you:
We will accept your request only if you write and speak [YOUR LANGUAGE] fluently.
We expect you to follow these steps:
Join the [YOUR LOCALE] Slack community. (If you have a separate Slack team for your locale, link to the instructions on how to join.)
Translate as a Contributor(Any person logged in at WordPress.org can contribute suggested translations. If you make an error, you may reject your own translation and submit a new one.)
Inform the translation team about your translation and ask them to review your contribution.
A PTE or a GTE (General Translator Editor) will review your translations and give you the feedback;
If the quality of your translation is up to the standards the communities try to follow, you will be granted PTE permissions.
Now that you have been granted PTE permissions, you can approve, reject or edit translations. You can also mark translations as “fuzzy”.
WHY WE FOLLOW THESE GUIDELINES
We strive for excellence: We aim to create the best possible localization for all products in the WordPress ecosystem. Since localization can determine a product’s user experience in a given language, all translations should be done in the best possible way.
It helps us create a community of translators for our locale that knows each other and can support each other when needed.
We think globally.
We aim at consistency.
It streamlines and optimizes the process, reducing the amount of “improper” translations and the time spent on rejecting and revising translations (thus allowing more time to be devoted to the actual localizing)
Our process for accepting a new editor is somewhat similar to how the code is submitted on GitHub, where access is not given directly to original code, but allowed through Forks and Pull Requests.
These rules are meant to give you the best possible localization for your product(s) and to contribute to enhanced user experience, a stronger platform, and a healthier ecosystem to work on for the whole WordPress community.
If you have any questions, we invite you to join the #Polyglots channel on the global WordPress Slack team (instructions for joining are found at https://make.wordpress.org/chat/ ) and find us in the #polyglots channel for further discussion.