Welcome to the official blog of the translator team for the WordPress open sourceOpen Source Open 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.org 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/ account and suggesting translations (more details).

Want to help in managing and validating translations? Get in touch with the existing language team and follow the glossaries & style guides if the team has them.

Don’t see your language? You can request support for it.

Weekly Meetings

We have meetings every week on SlackSlack Slack 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 sidebarSidebar A 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.

#polyglots

websait 10:17 am on February 2, 2020
Tags: request ( 1,460 )

Hi, Polyglots We will also…

Hi, Polyglots
We will also ask the moderators to review @kovalets actions and remove him as a GTEGeneral Translation Editor 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. manager. Also we provide the latest translation uploaded yesterday morning for evaluation, please show where is a machine translation. We would be glad if you tell us our mistakes.
https://translate.wordpress.com/projects/wpcom/uk/default/?filters%5Btranslated%5D=yes&filters%5Bstatus%5D=waiting
Thanks

#request

Sergey Kovalets 10:42 am on February 2, 2020

🤦‍♂️
tobifjellner (Tor-Bjorn Fjellner) 6:42 pm on February 2, 2020
Hi @websaitua
I have skimmed through the discussion in the global SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Here are my comments.

I happen to know a few languages, but Ukrainian is not one of them. So I’m not going to even try and judge any of your translations. Any questions about exactly how to translate something in WordPress to Ukrainian need to be handled within the Ukrainian community.

But I do know that everything here is powered by volunteers. Just like you volunteer your translations, there are currently 80 PTEProject Translation Editor A 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.’s and 3 GTEGeneral Translation Editor 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.’s assigned for the localeLocale Locale = 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 voluntarily validate translations. We have a common responsibility that all these contributors feel welcomed and valued. If we try to force anyone anywhere, then we may very quickly reach a situation where really good contributors start leaving, just because someone “killed the fun” in it.
(This is a real problem. We have seen several localesLocale Locale = 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/ suddenly lose contributors due to internal disputes. It’s very sad. Since WordPress totally depends on volunteer resources, we really need to make sure that the “contribution climate” is nice to all people involved.)

When translating for WordPress, one needs to keep several things in mind:
- There may be agreed translations of various terms. To this end the GTE’s may maintain a glossary. https://translate.wordpress.org/locale/uk/default/glossary
- Many locales have also created their own style guide. The ones we (the global mentors team) know about are listed in https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/list-of-glossaries-per-locale/
- Most of the active teams have one or several places where they may discuss terms, styles, or other topics around the translation and/or the translation process. For Ukrainian, there is a Slack team at https://ukwp.slack.com/ for this purpose.
- We’ve also got a global handbook that may be useful to know about: https://make.wordpress.org/polyglots/handbook/
The main tasks for the GTE’s are, as I see it:
- Set and maintain a reasonable quality level of the translations.
- Help translators grow into translation editorsTranslation Editor 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:
  General Translation Editor and Project Translation Editor (mainly by giving suggestions and feedback).
- Once they see that a translator is fit for the task, enable them as PTE’s.
- Keep their eyes open for contributors that would be interested in, and have the right qualities to be added as GTE’s.
- If their available time allows it, a GTE may also spend time on general checking of translations.
But I don’t see it as a task for GTE’s to fix translations of bad quality. My reason for this is that we have 55000+ plugins and 7400+ themes in the catalog. If every pluginPlugin 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/ or can be cost-based plugin from a third-party/theme author would generate translations automatically, then the GTE’s would give up after a week under a way too big amount of work.
So:
- Nobody can demand that a GTE should check their translation before everything else. A GTE is a volunteer contributor, just like everyone else. Wherever they feel most like contributing is what they’ll be doing best.
- Nobody can demand that a GTE should spend time on fixing a bad translation. (For me personally, when I’m checking a Swedish translation, if I notice that I need to fix something in half or more of someone’s stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings., then I’ll bulk reject all of their strings, because it would actually be quicker for me to just do the translation myself, instead of trying to check what strings just happen to be OK…)
About machine translation (or near to machine translation):
We comment machine translation specifically in our global handbook: https://make.wordpress.org/polyglots/handbook/translating/expectations/#be-careful-with-machine-translation
Note: Even the translation memory (“TM”) at translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. should be used with care:
- Some languages have a lot of low quality strings in the TM.
- You always need to understand the context. “Post”, for instance, may mean “Article”, “To publish”, or “Database record”.
- Depending on usage, the style level may need to be slightly different. Is a stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. supposed to be used in front-end or back-end, is it aimed at users in general or at topic specialists, for instance.
- Sometimes a fully correct translation may not work, either due to UIUI UI 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. layout (if the translation got much longer than the original) or because a plugin developer is doing “language magics” that work well only in English, so that you have to try and “work around” their constructions.
Personal contributions:
Translations are best contributed from individual user accounts. This makes it possible for GTE’s/translation editors to give personal feedback, and also to better see who is ready to become a translation editorTranslation Editor 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:
General Translation Editor and Project Translation Editor themselves.
If translations from various sources are submitted via one and the same user, then the end result will be lower quality, less likelihood of getting assigned as PTE, and almost impossible to give constructive feedback to the translators. (By the way: If I as a GTE realize that I won’t be able to give feedback to a translator, then I’m less interested in spending time, working on their translation.

I trust that the current GTE’s for Ukrainan know the target language well. I also trust that they are trying their best to defend a decent translation quality.
I ask you to take a deep breath, take one step back, calm down. You and the #uk team really should be able to sort this out locally in your own Slack team.

If you think that I said anything wrong here, or that I missed some important thing, feel free to either comment here or reach out to me in the global Slack team. But please, let’s keep this all on a civilized level.

Best regards,
Tobi

Translate WordPress

Weekly Meetings

Posting here

Share this: