WordPress.org

Making WordPress.org

Opened 10 days ago

Last modified 9 days ago

#4171 new enhancement

Ability to temporarily block translation editors & show a warning

Reported by: eclare Owned by:
Milestone: Priority: high
Component: Translate Site & Plugins Keywords: 2nd-opinion
Cc:

Description

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/

Attachments (1)

no-machine-translation.png (88.0 KB) - added by Nao 9 days ago.
Mockup of "Don't upload machine translation" note

Download all attachments as: .zip

Change History (5)

This ticket was mentioned in Slack in #polyglots by nao. View the logs.


9 days ago

@Nao
9 days ago

Mockup of "Don't upload machine translation" note

#2 @Nao
9 days ago

I agree that this will be an improvement for improving quality & reducing reviewer work.

For request 1, I think it's good to have a short one-line message with a link to a Polyglots Handbook page explaining issues with unreviewed machine translations (to be created). I illustrated my suggestion in the attached image.

#3 @eclare
9 days ago

I think that "machine-generated" is not clear enough. An example (Google Translate) should be added. And your proposal doesn't have enough seriousness in it to really make one think about what (s)he's adding, imho. Thank you for the screenshot and proposal, Nao.

Last edited 9 days ago by eclare (previous) (diff)

#4 in reply to: ↑ description @Luciano Croce
9 days ago

  • Keywords 2nd-opinion added
  • Priority changed from normal to high

Replying to eclare:

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.

Very good, but I suggest more other steps:

  1. Banning "declared" spammers from the translation platform.
  2. Blocking (temporarily ?) contributors that make translations in languages different from the target: for example contributors that send Latin strings (or other slangs) in English UK context (or similar cases).
  3. Extend all these features to PTE's too.
  4. Notify of all corrective actions. For example: PTE's corrective actions is notified to GTE's -> GTE's corrective actions is notified to LM's -> LM's corrective actions is notified to Global Mentor's.
  5. Add the possibility to enable/disable this type of notifications (described in step 7) in personal control panel of PTE/GTE/LM.
  6. Optionally report to themes/plugins review team the author that deliberalely make readme.txt or themes/plugins file in languages different from the en_US (this case make impossibility to PTE/GTE to make propery translations/corrections).
  7. Optionally reject all Latin strings in English UK context (for example).
Last edited 9 days ago by Luciano Croce (previous) (diff)
Note: See TracTickets for help on using tickets.