Guido 10:04 am on January 18, 2016

Hello Polyglots First I would like to say…

Hello Polyglots,

First I would like to say I fully support the language packs. Now everyone can contribute. That’s why I’ve removed all translations from my themes and plugins several months ago.

But, there should be something done regarding how long I have to wait before stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. of certain 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/ get approved.

Responses on this forum regarding this issue:

ship translation with your theme or 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 until language pack reaches 100%
because this is a new project it still has a limited number of 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
there a many strings waiting to be approved
just wait and be patient
find your own PTE for every 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/

Having a personal PTE for every locale sounds great (and I understand why), but if you don’t have a network this is a big challenge. Even more when your theme or plugin contains many locales.

I guess I’m not the only one who’s waiting for stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. approval for 1-2 months now. That’s why I would like to make a suggestion:

For now batch approve all strings with status ‘waiting’ once every month. Less work for theme author and PTE.

Any thoughts?

Guido

Wolly aka Paolo Valenti 10:08 am on January 18, 2016

Batch approve it’s not a solution.
Most of the translations are made by bot or with gtranslate.

There are thousands of plugins and themes and not enough contributors and PTEs. This is the problem.
RIBWhost 10:12 am on January 18, 2016

I am willing to help with translations, but you are Dutch like me right?
- Guido 10:17 am on January 18, 2016
  
  Yep 🙂
  And 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. for nl_NL so I can approve the myself.
  
  Guido
Wolly aka Paolo Valenti 10:14 am on January 18, 2016

@guido you can join the polyglots channel 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/..

I asked @petya to add this kind of request in a future polyglots meeting agenda so you can discuss with us on how to find a solution
Petya Raykovska 10:18 am on January 18, 2016

Hello,

We can’t batch approve stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings.. That’s neither right nor secure. If you had translations of your plugins and themes before, why don’t you work with 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/ editors to get those imported?

There are many ways to encourage your users to join the translation efforts, we encourage 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 authors to invite their users to translate, but we have teams who have worked hard to secure guidelines and processes for translating WordPress and as a part of the infrastructure now themes and plugins fall under the same guidelines.

I agree it’s not as easy as automatically shipping something, but I would encourage you to pursue the path of forming a translation community around your projects. If you had translations before, why don’t you contact your contributors and offer them to become PTEs for your project here?

Cheers,
Petya
- Guido 11:13 am on January 18, 2016
  
  Hi Petya,
  
  Thanks for your response and I understand what you mean.
  I’ve released my main 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 about 2 years ago and meanwhile I’ve lost contact with most translators. So that’s why I cannot ask them.
  But I will try to find a new 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. for every 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/. There’s no alternative unfortunately.
  Meanwhile I notice my request in another post for stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. approval has effect, 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/ have been approved, great!
  
  Guido
Stefano Aglietti 11:27 am on January 18, 2016

As global 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 we are trying to have a standard quality between plugins, we always see bad or poor translation, done using google trnslate or using unconventional terms (ex in italian post in WP is tanslated as articolo so should have be in plugins and themes.

Some tean as fr_FR test the 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. ofr theyr languages before approving them, but maybe they are a large group of people, most of out team is made by few people and we do in spare time, so we can’t do all this but neither approve everything be default.

Better to have 4 translation only but with a good caring that tons of trnaslation made in a poor way.
- Guido 12:21 pm on January 18, 2016
  
  Hi Stefano,
  
  After reading your and other responses I understand the best thing to do is to create my own team of 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 for each 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/.
  
  I fully understand why (some or all) Global 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 don’t have time to approve stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. of individual themes and plugins.
  
  That’s the reason I’ve made the suggestion to batch approve. You are right, there’s a (major) change of getting crappy translations so maybe my suggestion isn’t a very good one 😉
  
  I will try to find my own PTE’s. Case closed.
  
  Guido
Angelo Mandato 8:01 pm on January 23, 2016
First I want to make this clear, though I am very critical (I am by nature, i am a developer), I support the translation efforts. I know the reaction when someone criticizes the way things are done is perceived as anti WordPress, that is not the case with me. I will call out BS, but again I’m a developer it is in my DNA. I can tell you as a project supervisor, the way this is setup currently will never scale to the 40,000+ plugins, let alone the themes.

I am glad to see for once a thread not get deleted and actually being replied to that points out some of the problems with the way things are working now. Is there now an official way how we can post these issues or is it hit or miss if they get deleted or replied to? I’ve tired to discuss them on here (they get deleted), also 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/. I was given answers (that technically did not answers my concerns) rather than have someone listen to my concerns and let me know my concerns would be considered for discussion (responsive vs considerate support).

My thoughts as a 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 developer who is not in the 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/ coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, please take my thoughts and ideas into consideration. I think ideas and critical thought from outside wordpress core is necessary from time to time, like any project or application.
- Plugin developers should be trusted with their translations. This would solve a lot of problems. Yes there will be plugin developers who just use babelfish or google to translate, but I have an answer for that at the bottom of this reply.
Note: It is common for a company to pay someone to do translation work. In this example, even though I do not speak French, I may have the translations for French that my company paid for to put into my plugin. The current procedure prevents me from doing this translation when I ask for such access simply because the polyglots moderator says I do not speak French. (who owns the plugin and its translations?)
- Let plugin developers determine if a translation can happen or not regardless of percentage completed. I know if the developer doesn’t speak that 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/ language the translations may not be “correct”, but that is how it works today when not using translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.. After all we want to provide some translation rather than none. None is way worse than 50% translated.
- Provide a simple way for plugin developers to add/remove WordPress.org users as translator editors. It should be in the same place we add additional committers to our projects. Then the current method of posting a comment in a particularly specific way can end which is very frustrating. The latest example how to post requesting translators I saw wants you to praise the team in your introduction, this seems rather self-serving to me, almost as if to reinforce the system in place now is a good one.
- Translate editors should be strict. Meaning if I don’t add translator editors to my project, no one I don’t know is approving translations for my plugin without my knowledge. Yes I know the idea is to allow global 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 can approve translations for whatever plugin, but this brings up legal issues (see my GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples. comment below). Perfect world, the plugin author could simply check a box to say “my translator editors only” or “global translators allowed” next to each locale.
REST OF MY ITEMS ARE ADVANCED ISSUES
*Let plugin developers decide if a translation can even happen. There are situations where I may not want anyone to create a translation into a particular locale. For example, lets say we were going to launch a service in England in April, we may not want a version allowed to be translated until that release.
- Let the plugin developer have the ultimate say about translations. I may have my companies lawyer tell me the translation of a word we use as a trademark in the US cannot be used in France. That that point I as the plugin author need to be able to change that translation (not the translator editor I picked) Ocean90 pointed out some code I can add in PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. to do this but it did not quite answer this specific case, only how i can target 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/.
- Ultimately, the translation is part of the plugin and thus the management should be in the control of the plugin developer. Not allowing the plugin developer to have this control means that derived works are technically branches or forks owned by someone else (other than the plugin developer). This brings up legal questions, is a translation where the plugin developer cannot modify or control the translation still part of the original plugin or is it a derived work (where other parts regarding trademarks and copyright need to be modified). With everything falling under GPL here at WordPress.org, it would mean that the inaccessible by the plugin developer translated plugin technically should use a different name and modify the copyright, and give credit to the original plugin developer to make sure not to imply the derived work was his/hers. This problem is solved simply by allowing plugin developers complete control of who can and cannot translate their plugin including themselves (see my first item above).
I believe the scale-able solution is to allow Global Translation Editors the ability to grade translations that have been approved by non global translator editors. This would be viewed as some sort of star rating or grade percentage next to the translation that then the user can decide if it is good or not. That would solve the issue about quality of the translators in a community driven organic way. Also solves the problem if only 90% of the translation is completed, automatically the grade would be at most 90%.

This is what I would like to have access to as a plugin developer. A place in the plugin’s admin page that would list all of the locales in a table form with options:

locale | translator editors | translation allowed by | translation grade | actions
en-us | user1 x, user2 x, … | () global translators () plugin translator editors () plugin author only | 85% of translations accepted by global editors | add translator editor

| – separates columns in table
() – radio button (defaults to global translators)
- – next to user name to remove translator editor
I’ve already had folks reply telling me this cannot be done for random reasons. I beg of the team to instead respond with reasons why it cannot be done, please consider discussing these ideas first.

Translate WordPress

Weekly Meetings

Posting here

Hello Polyglots First I would like to say…

Translate WordPress

Weekly Meetings

Posting here

Share this: