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.
GlotPress is a web-based translation management system (TMS) designed for translating software, such as WordPress themes and plugins. It is currently being used at https://translate.wordpress.org/ to translate:
WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
Plugins.
Themes.
Patterns.
MetaMetaMeta 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..
Apps.
Over the last few years, the documentation community has discussed and requested a platform to be able to translate the documentation. Some interesting posts:
With this first implementation, we are creating a tool using GlotPressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. as the backend to translate WordPress pages inline. The workflow is as follows:
Import the page content to GlotPress.
Start working on the translations in GlotPress.
Export the current translations to the translated page.
However, if the user prefers (and it is the recommended approach), they can do all the translations inline, without using the GlotPress interface, thanks to the inline functionality we added to GlotPress. The workflow for this method will be:
Import the page content to GlotPress.
Export the new page with contents in the original language and ready for translation.
Start translating inline.
Below are some screenshots that demonstrate the current functionality. Be aware that this is a demonstration of the feasibility of the “data flow”, not the final “user flow.” See the last section for what such a flow could look like.
Screenshots
Button to Import Page Content to GlotPress
The first action the user needs to perform is to import the page content. This action will create a new project in GlotPress.
Project in GlotPress
The previous action created a project inside GlotPress for the imported page, under the “Pages” project. Each page will have its own GlotPress project.
Imported stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings.
The user can see the imported strings without any translation. While the user can start translating strings here, the recommended approach is to use the inline translation feature.
DeployingDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. a translated page
Before starting the inline translation, the user needs to deployDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. the new page with the translations (or the originals if translations are not available for the current 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/).
Pages
Once you deploy the translated page, you are going to view both pages in the “Pages” section. In the next iteration, we need to add a “language mark” so the end-user will see this is the translated page (or the strings in the original language if they have not been translated).
Inline translation
Now, the user can go to the newly created page and start translating inline. These translations will be stored in the GlotPress tables, so the user won’t need to access the GlotPress frontend if they don’t want to.
If the user double-clicks on a red element, they will see a pop-up where they can add the translation or change any existing translation.
As the user translates the content, the background will change from red to green.
A Potential HelpHub Translation Flow
Based on the discoveries so far, we could see the following scenario in place. Note that the wp-admin screens from above will not be part of the workflow because these items are automated like shown below:
HelpHub would have its own GlotPress install residing in a subdirectory. 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. status would be reused from translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins., further PTEs can be appointed.
Updates to the English Documentation would lead to automatic updates of the GlotPress projects, making it thus easier to spot outdated documentation.
GlotPress and Inline Translation will be available for everyone with the known workflow where someone without enough permissions would submit a translation as waiting. Inline Translation will happen on a page which a post status set to private so that only logged-in users can see it.
Inline Translation will preview your own translations, even if they are not approved. Thus, you can translate a whole page and ensure that it reads well without having to wait for a review.
Translations would be automatically deployedDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. (= set to publish) at a certain translation threshold.
Further Notes:
If the English text is updated, a translated old version will remain and show a note at the top. When a translator starts inline translating for this new page, a mixed-English-translated text will be written and the translator can translate it inline. When finished, the translated page will be deployed automatically.
The translator can see the amount of work necessary by looking in the language overview. See this mockup:
Currently, there is 94 items in this both sections. In my case I just need 3-5 other languages and other localesLocaleLocale = 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/ to reference. I think “Less is better than more” in there. People can quickly find what they need.
I am wondering if we can add some customize settings here? Let the translator select the languages and locales which they really need to reference instead let them get lost in too much information.
To subscribe to our newsletter and receive updates in your inbox, you cansign up here.
Welcome to the February 2023 edition of the Polyglots monthly newsletter, the monthly news roundup from the WordPress Polyglots teamPolyglots TeamPolyglots 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/.!
🗣 It’s WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. time!
In this edition of the newsletter, we have plenty of news to share from WordCamps around the globe. If you want to feature your WordCamp in a future edition of the newsletter, send us a message in polyglots or polyglots-events, and we’d be happy to share your event with the community!
First, this week we have WordCamp Asia! The first flagship WordCamp in Asia is starting on February 17th, 2023. Are you going? Don’t forget to stop by the Polyglots table during Contributor Day on February 17 and share your highlights in the polyglots channel. Can’t join in person? Don’t worry, you can attend virtually via the WordCamp Asia livestream.
If you’re a translation editorTranslation 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 and can do so, please keep an extra eye on the polyglots channel in SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. during Contributor Day, 9:00 to 17:00 UTC+7 on February 17th, 2023. This can be helpful if a new contributor is suggesting stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. and needs some quick feedback, or even wants to become 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.. Plus, it’s always much nicer when you, as a new participant, can see that your contribution makes a difference!
Since 2023 is just getting started, don’t forget to start planning your trip to WordCamp Europe. The European WordPress Community will come together in Athens, Greece, from June 8th to June 10th. You can get your tickets and all the information related to the event here.
Lastly, WordCamp Torino (April 14 to 15) has opened the calls for Sponsors, Volunteers, and Speakers. You can apply for them, and check the rest of the details of the event here. We hope to see you at one of these events!
🌐 Using GlotPressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. as a local translation pluginPluginA 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
Have you heard? Polyglots have been hard at work improving GlotPress’s functionality! Recent improvements to translate.wordpress.org include:
There is a new proposal to build on GlotPress functionality that would enable WordPress users to use GlotPress on their own WordPress installations. This would allow users to translate their whole system and share these translations as suggestions with the community. If you’d like to read more about the idea and leave feedback, thoughts, and questions, you can do so in the proposal.
☕ Next Polyglots Coffee Break: February 23, 2023 @ 22:00 UTC
The Polyglots Coffee Break is an hour-long casual video call to meet other Polyglots contributors around the world virtually. On February 23, 2023 at 22:00 UTC, join us for a casual discussion! Find the video link in the polyglots channel at 22:00 UTC.
📈Latest stats
The latest statistics are from January 13 to February 15, 2023. You can view the monthly difference in the number between the parentheses.
Releases
208 (±1) 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/, 69 (+2) up to date, 0 (±0) behind by minor versions.
55.8% (-0.1%) of WordPress sites are running a translated WordPress site.
📰 More news and resources
Handbook update: A new Handbook page has been published, How to Translate. This page combines the information previously in two separate Handbook pages, First Steps and After Your Contribution.
The Polyglots Outreach Effort post for February has been published and includes fifteen new locale teams for outreach. Additionally, you can find the first version of the Translation Events Kit in the post, which includes various materials for organizing a local translation event.
Get a preview of what’s coming in WordPress 6.2 with the Roadmap to 6.2 published on the Make/CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. team blog.
The Training Team has launched a new onboarding program. It has a path specifically for contributors interested in translating content on learn.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/. Learn more in the announcement post!
Did you know…? In honor of the upcoming WordCamp Asia, let’s revisit some WordCamp history. Wapuu, a beloved character in the WordPress community, has roots in the Polyglots team! Launched in 2011 at WordCamp Fukuoka, Wapuu was created by and for the Japanese WordPress community, by Kaneuku Kazuko. Since then, Wapuu has gone global and is often represented wearing local dress or participating in other local customs for WordCamps around the world.
🏆 Get Involved
Are you looking for more ways to get started? If you’re translating or want to translate WordPress and any related projects into a specific language, there are some helpful resources.
Help subtitle or edit a WordPress Translation Day video to help encourage the polyglots community and highlight the opportunities for new contributors. If you can join the efforts in this area, message @abhanonstopnewsuk and @meher in the polyglots-events channel on the Make WordPress Slack.
Does your language still not have its own support forumSupport ForumWordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations.? We can help you get started on Make/Polyglots or in the polyglots channel.
If you need any help, ask in the polyglots channel in the Make WordPress Slack at any time. We’re a global team, so there’s almost always someone around!
Over the past months, we(1) have been working to improve some elements in the GlotPressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org.pluginPluginA 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 and in the translate.wordpress.org platform:
Feedback and discussions.
New “changes requested” status.
New tabs in the right 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..
Now, we want to further improve the GlotPress functionality, enabling the users to use this plugin in their own installations to translate their whole system and to exchange these translations with the community. You can see the main workflow for the proposed functionality in the image below:
What do we propose?
We want to add functionality to the GlotPress plugin to:
Translate the WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., the plugins and the themes to the user’s language in the user’s installation.
DeployDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. these translations on the fly in the user’s installation, generating the .mo filesMO filesMO, 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/ with one click (and/or automatically with each translating). Empower users to translate their WordPress UIUIUI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. without having to go through translate.wordpress.org.
In the midterm, we want to add in-line translation, so you can translate the stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. in the same user interface where they are shown, like we can with the WordPress.com Community Translator.
These new functionalities should be optional, so you should be able to disable them with a click in the backend, because you could be using GlotPress to translate elements not related with WordPress.
Benefits of a Local GlotPress
These are the main benefits we want to achieve with this new functionality:
Discoverability → Onboard new community members
For us as the WordPress community, it would be interesting to expose the surface of translation to wp-admin users since it will be discoverable on the sidebar:
We’re hoping to reach new audiences by not requiring people to come to translate.wordpress.org to do their first contribution.
Translating the plugins you are using → Better quality
On translate.wordpress.org there often is a disconnect between what you translate and what you use. On your local installLocal InstallA local install of WordPress is a way to create a staging environment by installing a LAMP or LEMP stack on your local computer. you will only translate local plugins and themes, thus you know how they work and what is important to translate: seeing translations in context locally and adding inline translation will improve their quality.
Use your own translation right away, don’t have to wait for language packs → Instant translations
Related to the previous point, since you can verify the translation on your own install right away, you can know that it works for you.
When translating on translate.wordpress.org, you can only easily use your translations as soon as you have reached the translation threshold (of I believe 90%) before the translations will be delivered to your own installation.
Safe Space / You don’t have to be part of the community
Some people don’t want to get exposed to a community or work in isolation. The plugin allows this and there could be the possibility to contribute your translations anonymously to translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins..
Also, people can explore translation in a safe local space, on translate.wordpress.org they need to create an account and anything they do is public.
Enables “Hyperlocal Translation”
If you don’t need or want to share all of your translations, you can use local slang or very regional language that would not be accepted on translate.wordpress.org but would be able to be used for your instance of WordPress.
Private Plugin and Theme translation
On translate.wordpress.org you can only translate what’s in the plugin directory. This would open translation to private plugins. We need to explore if and how those translations could be leveraged, but it would be an exciting possibility.
Translate the high impact strings first
When there is a lot to be translated, it can be hard to know which translations are most important to translate. When translating locally (possibly using inline translation), you can immediately spot the most important strings because they are right in front of you.
Some Ideas around the Implementation
The screenshots below are mockups. The local content translation starts in the backend. When you install or update GlotPress, you will have a new menu on the sidebar. You can see all the plugins and themes that you have installed and with a click, you can start translating the core, a plugin or a theme.
When you click in one of these links, you will start or continue translating this element into your language. The original strings, from the .po file, will be imported and/or updated into the GlotPress tables in this step.
If you access to the GlotPress’ main page, you will see different projects:
Usual projects, as you currently use into GlotPress.
Local project, with an icon and without the edit button. You only can delete the project into GlotPress.
In a future iteration, we want to add inline translation, so you can translate the local elements into your native language without leaving the page, as we have in the WordPress.com Community Translator.
Eventually, in the dashboard, you will have a button to share your translations with the translate.wordpress.org community. This will require another screen that will show you what exactly you’d be sending, so this is still a little further away.
Feedback, please
We share our vision with the community to get feedback from the real users, so, please, give us your feedback in the comments, so we can develop the best tool that all the community need.
As announced last week, GlotPress 3.0 is finally coming. On translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins. we already had a pre-version of 3.0 running but today it was updated to the release candidateRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. of GlotPressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. 3.0. There are a few changes I’d like to highlight:
Updated layout and design
GlotPress now provides an improved default set of styles for typography, tables, buttons, form elements, and links. This allowed us to remove some custom styles we had, making it easier to maintain the platform in the future. The colors are mostly the same as before though, matching the overall design on 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/.
I took this opportunity to slightly increase the default width of the content wrapper to improve readability and also extensibility for upcoming changes.
Simplified status filters
Previously you could only select from a pre-defined list of combined status filters. Now you can select any combination you want.
Each status can be selected.
The case-sensitive option is now close to the search term input. There’s now also a sort option for modified date of translation.
Glossary updates
You can now select ‘abbreviation’ as a part of speech value.
Stricter validation of new entries to ensure term have the correct format when importing.
Terms with multiple words are now matched again in translations. Props @pedromendonca!
Adding identical terms for different parts of speech is now possible again too.
If you notice any issue please leave a comment here or in the Meta Trac ticket. (Please make sure the issue is reproducible with any browser extensions disabled.)
The call for early testers is closed for now, but anyone can follow the test instruction and share feedback. For anyone joining the testing, please keep an eye on the #polyglotsSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel and future posts for updates.
A new way to give feedback in translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins. is being developed. A few weeks ago, @amieiroshared some screenshots of what this new feedback functionality might look like. Now, it’s ready for early testing.
Currently, this feature is being developed in a separate plugin. The goal is to potentially include some of these features in the GlotPress plugin itself, or as customizations specific to translate.wordpress.org. To help make sure that the tool works well, and fits the needs of Polyglots, we need to test it!
What’s the feedback feature?
In short, this feedback functionality allows 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 to review and comment on suggested translations within GlotPressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org.. Instead of manually sharing feedback with translators via Slack, on the 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/ blog, or on the Make/Polyglots blog, translation editors can give feedback directly in GlotPress via a discussion thread linked to the related stringStringA string is a translatable part of the software. A translation consists of a multitude of localized strings..
Benefits of the feature
Translation contributors are only required to have a 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 to receive translation feedback.
This means there will always be a straightforward way to contact the translator or editor.
Editors can stay on translate.wordpress.org to share feedback, making it easier to leave a comment.
It’s discouraging for both editors and translators when a translation is rejected without feedback about why or how to improve it.
PluginPluginA 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 developers will be able to receive feedback on original stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings..
Translators and editors will be able to share feedback on spelling or grammatical errors and request additional context for a string, making it easier to translate.
How can I help?
Test it out! Because this is such a new tool with so many considerations – especially for integration into translate.wordpress.org – the goal is to gather a small group of early testers for initial feedback. That will include:
PTEs
GTEs
Locale Managers
Plugin developers*
For anyone who signs up to help with early testing, you will need to:
Alternatively, you can use a standard WordPress install with both GlotPress and GP Translation Helpers active (Edit 02-24-2022: you can only test functionalities through this method. UIUIUI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. will look different). More info here.
Test it in as many ways as you can think!
Share feedback in GitHub, the comments of this post, or in the glotpress or polyglots channels in the Making WordPress Slack
(Optional) Join a Slack-based meeting to discuss the feedback
* The feature will include an option to give feedback on the original string. You do not need to be a Polyglot to help test feedback and notifications for plugin developers!
Expect to spend a minimum of three to five hours total on testing and sharing feedback. If you have more time, even better! Once you have the local environment set up and the related plugin installed, you are welcome to start testing as soon as possible. Need some help getting set up? Here’s a video tutorial from @amieiroon how to get started.
As development continues for this feature, there will be additional updates shared on this post and in Slack, including more information, how you can test, and opportunities for more people to get involved.
Please feel free to share this with your locale and/or with any plugin developers you might know, as well.
Thank you @nao and @amieiro for helping to write and review this post!
In the last months, there has not been a meeting to talk about GlotPressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org..
In August, I have started working at Automattic to improve internationalizationInternationalizationInternationalization (sometimes shortened to I18N , meaning “I - eighteen letters -N”) is the process of planning and implementing products and services so that they can easily be adapted to specific local languages and cultures, a process called localization. This is the process of making software translatable. Information about Internationalization for developers can be found in the Developer’s handbooks., localizationLocalizationLocalization (sometimes shortened to "l10n") is the process of adapting a product or service to a particular language, culture, and desired local "look-and-feel.", and GlotPress functionalities at translate.wordpress.org, in order to have the WordPress ecosystem translated into more languages, with more translated elements, and with better quality.
And, in order to improve, the best thing I can do is to talk with the members of the translation community, so that we can discuss the needs the translation community has and prioritize their development.
I’m interested in contributing to the localizationLocalizationLocalization (sometimes shortened to "l10n") is the process of adapting a product or service to a particular language, culture, and desired local "look-and-feel." of WP coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., themes and plugins.
I’m a web developer from Algeria, with quite good translation skills around these languages : English, French and Arabic. I’m quite familiar with collaborative translation projects (worked on Yoast SEO pluginPluginA 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 and OwnCloud platform years ago) and I’ve used WPML content/stringStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. translation on various occasions.
If I am attributed the role of a 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. for #arabic, I’m wiliing to :
1. Enrich the #arabic glossary with missing terms, and discuss with the community to tackle any ambiguity issues between similar terms,
2. Try to put together a style guide for arabic 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/ contributors,
3. Suggest modifications (ncessary ones) to the core of the #ar#locale itself (in #GlotPress),
4. Share the load of the other GTEs and s in both string translation and reviewing.
I am keen to help provide an exhaustive and consistent high quality #ar localization for the popular / most used plugins and themes, but also some of the plugins/themes that target mainly arabic language users.
For that, we can put some milestones to prioritize our work :
1. Hit the 100% for the WP core localization.
2. Target the most used plugins/themes first (10 – 20 -50 – 100 most used) and make it above the 95% threshold for them to be integrated in current and future releases.
3. Gradually clean the crowded plugins/themes of any warnings/fuzzy stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. (one at a time).
For the time being, I can dedicate at least one hour of reviewing and 2 hours of translation on a weekly basis..
I hope I can get along with you guys and learn from your experience within this community 🙂
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/ stats
Below stats are dated 2017-01-18 compared to 2017-01-11 (differences between brackets)
Releases: 164 (±0) locale, 65 (-3) up to date, 3 (+3) behind by minor versions, 12 (±0) behind by one major version, 17 (±0) behind more than one major version, 58 (±0) have site but never released, 9 (±0) have no site. Translations: 164 (±0) total, 64 (-1) at 100%, 4 (+1) over 95%, 3 (±0) over 90%, 31 (±0) over 50%, 55 (±0) below 50%, 87 (±0) have a language pack generated, 7 (±0) have no project.
Requests: There are 15 unresolved editor requests out of 585 (+8) total and 9 unresolved locale requests out of 41 (+1) total.
Translators: There are 483 (±0) 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., 1 251 (+18) 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. and 12 295 (+62) translation contributors.
(A 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 could have multiple roles over different locale)
Site language: 51,762% (+0,010%) of the WordPress sites are running in en_US (English (US)).
Armenian (#hy), Persian (#fa_IR) and Welsh (#cy) seem to still be at 4.7 . @luisrull will contact them to see if they need help with the release
Tech update
GlotpressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. 2.3.0 is in BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. ! A great job from and enormous thanks to @ocean90 and the team. The release notes are on https://glotpress.blog/2017/01/17/glotpress-2-3-0-beta/
The weekly chat meetings about GlotPress are on Tuesdays @ 17:00 UTC in channel #glotpress
Outreach Campaign on RosettaRosettaThe 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. sites
@petya proposes a review of the Rosetta sites for the released/active localesLocaleLocale = 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/ and reaching out to communities in different countries on the possible use of Rosetta because some might not be aware that they are welcome to use their Rosetta sites to announce events and discuss local community topics. So to focus on working with the community team and make Rosetta sites more useful.
Volunteers are needed to help make this happen. The job is mostly talking to people here 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/..
Actions would consist of:
Review all Rosetta sites and see who are not updated regularly
Check if there are meetups/WordCamps in the location the site is built for
Reach out to those organisers and ask them if they’d be ok with announcing the events on the Rosetta site as well
Communities that seem to be really using Rosetta already are Romania, Italy and Bulgaria
Contents that can go on Rosetta:
Translations of the release posts
Announcements for events
Local contributor updates starting with a page on how to join the translation team
Some pluginPluginA 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 authors from the top plugin list were contacted and informed how easy it was to get on translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins..
@juhise is looking for volunteers to help with #hi_IN translation
@petya would like to have a page on Rosetta displaying all local users and their roles. @tobifjellner was proposing to maybe also add an opt-out.
@petya : chat to the community team about making organisers aware of the Rosetta review
@luisrull : contact the 3 locales to see if they need help with releasing (@casiepa)
@casiepa : Propose spreadsheet for the Rosetta review
@casiepa : Check for volunteers and lead of the Rosetta review during next meeting (@casiepa)
@casiepa : Check for existing tracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets about a Rosetta page displaying local users and roles
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/ stats after the 4.5.2 maintenance release
Releases: 162 localesLocaleLocale = 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/. 58 locales up to date. 3 locales behind by minor versions. 15 locales behind by one major version. 16 locales behind more than one major version. 61 locales have a site but never released. 9 locales don’t have a site.
Translations: 162 locales. 61 locales at 100%. 3 locales have more than 95%. 5 locales have more than 90%. 22 locales have more than 50%. 61 locales have less than 50%. 10 locales don’t have a WP project.
Next short term goal is getting to 75 locales up to date before 4.6
Technical update
TracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Ticket #r37361-coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.: In WordPress 4.6 Open Sans is removed and will be replaced with system fonts. Polyglots are asked to test in their locale whether the display of the back end works with system fonts in their native language/characters.
In the #glotpress meeting was discussed if a “Master Glossary” should be tied to a project. Related pull request is https://github.com/GlotPress/GlotPress-WP/pull/435
It was widely agreed, that we aren’t a fan of using a (random) project for the master glossary. The team prefers a detached master glossary. More feedback can be left as a comment on the issue or the pull request.
The other technical update is about loading text domains/languages in core for plugins and themes, which will be changed in WordPress 4.6. Previously, if a pluginPluginA 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 shipped a translation and a language pack (from translate.w.org) existed, WordPress loaded the one from the plugin. In WordPress 4.6 the translation from translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins. will be loaded instead.
Second change is that plugins and themes which have translations on translate.w.org are no longer required to call load_plugin_textdomain() or load_theme_textdomain(). Therefore a number of rules that used to blockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. an import to translate.wordpress.org can be removed.
WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe contributor dayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.
We will have an unprecedented number of contributors and many polyglots. It would nice to work out some tasks for Contributor Day and polyglots are asked for ideas either in the comments below or in the next meeting.
At GWTD I have done a super easy fast session about how a browser extension can change your translation workflow on glotpressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org., in this case on translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins..
Link for the live session about this extension for the new users: https://www.crowdcast.io/e/wptranslationday/18
So what is the new features of this awesome super cool extension?
Fix for terms detection near () symbols
Fix alignment of toolbar for 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.
Enhancement: New UIUIUI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. on first use
Enhancement: No default language on first use
Feature: Shortcut on Ctrl+Enter to click “Suggest new translation” or “Add translation”
Feature: Shortcut on Page Down to open the previous stringStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. to translate
Feature: Shortcut on Page Up to open the next string to translate
Enhancement: New glossaries: he_IL, ro_RO, th, en_AU, en_CA
New icon by Crowdedtent
Actually the languages supported are 18!
How to add a new 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/? see the video!
The interesting part of this version are the hotkeys to speed up the translations!
With ctrl+enter (ctrl not command for the OSX users) the string that your are translating is saved (you don’t need to click with mouse, is automatically done by GlotDict) and with Page Up and Page Down you can switch between the stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. (on the switch they are not saved).
For issues: https://github.com/Mte90/GlotDict
Changelog: https://github.com/Mte90/GlotDict/blob/master/CHANGELOG.md
First of all thanks everyone for all the job that you done for translate the WordPress world.
I’m Daniele Scasciafratte a Mozilla volunteer and also a WordPress Italian contributor so when in the Italian community @Xtraboy ask about someone that can develop a browser extension for the community itself I jump that opportunity to help.
This browser extension fix an annoying problem for the non-english translators that use a custom glossary for their languages and need that information on https://translate.wordpress.org/ on terms (the terms with a dotted bottom border).
Actually GlotPressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. have only one glossary that contain English information and not for specific localesLocaleLocale = 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/ so this extension fix that problem.
This extension support different glossaries (actually only the Italian is available) to add the same look and feel and experience of the native English terms.
GitHubGitHubGitHub 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/: github.com/Mte90/GlotDict
How use it
After the installation you get on https://translate.wordpress.org/ the dropdown menu on the right “Pick the glossary” to choose the glossary (that information is required only the first time, it’s saved in the browser for the future).
After the installation and this step you can use the glossary automatically!
As you can see in the screenshot the username term get the dotted bottom border and a tooltip with the Italian terms information.
Developer zone
How works
The code is very simple, the core part is loaded on every https://translate.wordpress.org/ page of the JSON that contain the glossary: the terms to highlight, comment, pos and translation. Here you can find the Italian JSONJSONJSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. that actually is the only one available but I wait for your pull request to add new glossaries.
Generate the glossary
The Italian community maintain a glossary on Google Drive so for a developer like me was not a big problem to create a script that generate the JSON automatically for the extension.
This python script use the Google APIs to parse that document and save a compatible JSON for the extension and can be an useful start point for the other communities.
The next steps
New glossaries for many languages
Improve the UIUIUI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing./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. of the extension (if there are suggestions)
New icon (actually is the glotpress icon)
Better readme (I am a developer but the target of that extension is also for non-developers so need to be more simple)
Thanks to the Italian community for their work not only on translation but also for support and promotion!
The last couple of weeks I have translated several of my favorite plugins into my native language and run into an issue.
I was not able to find an answer at glotpressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. site: Editing a string
So I posted my question at WP forum a week ago:
https://wordpress.org/support/topic/special-characters-in-glotpress-translation
Unfortunately no response so far, can anybody here take a look?
I was asked to fill a survey about our team’s work in 2015, so I’m sharing what I said in this post. As always, please add your comments and anything important you feel we need to add to our goals for 2016 below this post.
Did the team set any specific goals for 2015?
We did. A lot of those don’t depend on the translation teams but more on the MetaMetaMeta 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. team as it’s tools to help translators. Here are the goals as mentioned in this post.
Aim to have 70 very active, very updated localesLocaleLocale = 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/ by the end of 2015.
Focus on bringing in and mentoring new validators. Everyone’s help here will be invaluable – talk to people about your Polyglots work, find and inspire new translators to join.
Get Involved page linked from your local site’s primary menu.
Speaking and encouraging people to join the team at meetups
Translation sprints! Amazing idea, read more in @nao‘s post and please share your thoughts!
Last year at the community summit, a lot of people didn’t know what Polyglots did. We should try and do something about it this year. Suggestions include talking about it at local meetups and WordCamps.
Aim to have 50% locales up to date, currently, it’s just ~35% – this would mean cleaning inactive locales or trying to find validators for them
RosettaRosettaThe 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. sites to be integrated with local communities and to start getting fresh content about meetups and WordCamps
Finish the Handbook.
Team P2s
An update on the Rosetta theme and a new bbPressbbPressFree, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. theme (hopefully)
Polyglots badges.
What were the major accomplishments of the team in 2015?
We have 69 active running locales, 57 are released for 4.4
There are 79 locales translated 80% and more, 54 of those are translated 100%
We added 20 new locales and localizationLocalizationLocalization (sometimes shortened to "l10n") is the process of adapting a product or service to a particular language, culture, and desired local "look-and-feel." teams to the project in 2015, WordPress now has 158 locales
WordPress is now 100% translated in Hindi, one of the top 10 world languages that we were missing before – there are many locales who started at 0 and were completely translated in 2015.
We automated Polyglots badges
We improved the team documentation and streamlined the processes for requesting a new 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/, requesting to join a team, and requesting 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 for specific plugins
We have a team. There are several people dedicated to the Polyglots teamPolyglots TeamPolyglots 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/. and we’re growing the base of contributors involved with helping other contributors (some small equivalent of the WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. deputy program)
We have regular meetings and communication going in and out of the team
We have an active SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel where people get help almost 24/7
Were there any particular challenges to the team achieving its goals?
Lack of tools and improvements of the translation management system (GlotPressGlotPressGlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org.). The tools the team needs are still in development and we’ve been waiting for some of them for a long time. The meta team is helping us as much as they can, but they have a very long list of tasks. With the increased demand for translations (of the 30k plugins in the repositoryWordPress Localization RepositoryThe WordPress Localization Repository at https://i18n.svn.wordpress.org/ is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details.), the demand for better tools from members of the translation teams increases too.
Lack of team P2s which were supposed to be in a year ago makes it hard for translation teams to communicate internally – it’s next to impossible to get in touch with the active translators unless they’re not all in w.org slack (most aren’t), so we’ve been looking for workarounds to help Translation editors talk to their contributors.
There are three particular GlotPress features we’re waiting for:
Reject strings with feedback for the contributor (https://glotpress.trac.wordpress.org/ticket/335)
Notification center for translation editors and translation contributors on waiting strings, new strings and overall activity in the projects they’re involved with (https://glotpress.trac.wordpress.org/ticket/100)
Global glossaries across projects – a feature that would help translation teams keep just one glossary up to date and all projects for the specific locale inherit that glossary.
Has the team set any goals for 2016?
Work with local teams to improve local getting started guides for new contributors
100 released locales for the last WordPress release for 2016
Top 100 plugins and themes in the repository translated at more than 50% for the 50 most active locales
Improve translation management and communication tools (P2s, the three GlotPress features mentioned)
Improve the visibility of the Polyglots team across the WordPress ecosystem and get team recognition for releases
Increase the number of active translation editors per locale to meet the demand for translations of plugins and teams and keep the quality of the translations high
Expand the leadership team to the Asia/Pacific region and have a functioning operation to support contributors in non-European timezones.
Is there anything that would make your work on this team easier in 2016?
More development time focused on translation tools
Better tools to communicate with translation editors and translation contributors (right now to notify them about an upcoming release we use posts where we @mention them to get their attention – that’s a manual process that takes a lot of time)
Rethinking of the processes of freezing stringsStringA string is a translatable part of the software. A translation consists of a multitude of localized strings. before a release with the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. team so that translators have enough time to properly prepare the locales before the release date. I’m already working on this with Drew and the core team.
Recognition for translators. If someone can get props for a release for fixing a typo, translation editors who spend hours working to bring that release to more people, should get a mention in the release post. A general mention of the translation efforts would be enough – just let the world know that that release is available in more than 50 languages thanks to the efforts of the translation teams.
Looking forward to your comments and working with all of you in 2016.
