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!
Something I’ve been thinking about for some time is a tour for translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins..
Product tours can be a very helpful way to introduce new users to a piece of software. In this case, a product tour for translate.wordpress.org can be an excellent way to guide new contributors on translation best practices, even before receiving feedback from translation editorsTranslation EditorTranslation 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.
In the Polyglots outreach effort, a need to better educate new translators frequently emerged in the survey responses. While there are visible links to Glossaries and the Polyglots Handbook on project pages, it’s hard to know if translators visit them before contributing their first suggestions.
While the GlotPressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org.discussion tool allows translation editors to share feedback more easily, there is also an opportunity to proactively teach translators before their first translation. Relatedly, the Learn WordPress Polyglots Training was partially written with this in mind but is slightly more technical and exists outside translate.wordpress.org.
An idea: a guided tour
To help improve translation quality from the first suggested translation, I’d like to share the idea of adding a guided tour to translate.wordpress.org, specifically for new translators to learn more about best practices.
What does this mean? When someone logs into translate.wordpress.org for the first time, or after a long time (e.g. > 12 months), a few interactive pointers guide the person through the translation process and the translate.wordpress.org interface.
Example using WordPress pointers.
The goal would be to encourage translation best practices for new or returning translators. Including key steps—like “Check your 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/’s style guide before submitting your suggestion” or “Have you requested feedback from your translation editors on Make/Polyglots?”—encourages new contributors to follow guidelines set by their locale teams.
When new contributors are familiar with resources like the local Style Guide, Glossary, or review process, it can help improve translation quality. Better quality equally means fewer corrections from translation editors. It can also mean encouraging people to opt into the discussion tool, making sharing feedback easier and seeing their translations accepted more quickly.
There are infinite ways to implement something like this. Taking inspiration from other 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. communities, Pontoon—the translation tool for Mozilla—has a standalone walk-through that allows translators to test the tool before they start translating. WordPress, as another example, offers pointers in the Dashboard.
What do you think? In particular, I would love to hear:
Do you think this would help with translation quality in your locale team?
What are the most common errors you see from new contributors?
When should the tour happen? For example, in translate.wordpress.org, while someone suggests their first translations or in a separate, interactive site, like this example?
One of the biggest challenges would be keeping the tour updated over time, and it’s not helpful to anyone—translators or developers—to create something that quickly becomes obsolete. For anyone with a design background, I’d be particularly interested in getting your opinion on UXUXUX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. best practices and maintenance.
This is a rough idea! I very much welcome all of your thoughts and perspectives to explore this proposal.