[wp-meta] [Making WordPress.org] #4171: Ability to temporarily block translation editors & show a warning

Making WordPress.org noreply at wordpress.org
Mon Feb 11 13:41:03 UTC 2019


#4171: Ability to temporarily block translation editors & show a warning
--------------------------------------+--------------------
 Reporter:  eclare                    |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+--------------------
 I’m not sure if this is the case only for my locale, but lately there’s
 been more & more submissions that are obviously just imported *.po files,
 which were translated using Google Translate and with no further
 inspection.

 The plugin / theme authors think that someone did a great job and ask for
 PTE rights for such a person.

 As most strings are short, about 50% of such translations are correct,
 while the rest is garbage – totally wrong even for really easy & obvious
 strings (example: “Dashboard” was translated to “Dashboard of a car” in my
 language). That aside, no PHP context is considered for such translations.

 This means that reviewing such submissions requires literally making the
 translation from the start, reviewing the context, fixing the lost letter
 capitalization, correcting inconsistencies. A GTE would therefore do the
 translation as if there was none. This does not help, it actually takes up
 the GTE’s and project author’s time. This is the opposite of what helping
 in translation is.

 If such garbage is submitted and it’s obvious that it’s an automatic
 translation (not just a case of not sticking to the conventions), I myself
 reject all Waiting strings submitted by such a user for that project.

 **Here are my requests:**
 1. Easy: somewhere near the *.po import buttons, place a warning saying
 “If you submit a translation which was done automatically (like using
 Google Translate) and isn’t manually corrected, ALL the strings will be
 rejected, even if a lot of them came out correctly. If you did the whole
 translation manually, you don’t need to worry.”. Maybe even warn: “You
 will be blocked from further submission to all projects for 2 weeks.”.
 2. Enable the GTEs to actually block translation submission from such
 accounts, for 2 weeks seems fine.
 3. Enable GTEs to bulk-remove all non-accepted translations made by a user
 for all projects at once.

 Discussion: [https://make.wordpress.org/polyglots/2019/02/09/ability-to-
 temporary-block-translators-who-submit-garbage/]

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4171>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list