Ability to temporary block translators who submit garbage

I’m not sure if this is the case only for my 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/, but lately there’s been more & more submissions that are obviously just imported *.po filesPO files PO files are human readable files which contain translations we use. These files are not used by WordPress itself. Each language will have its own PO file, for example, for French there would be a fr_FR.po file, for german there would be a de_DE.po, for British English there might be en_GB.po., which were translated using Google Translate and with no further inspection.

The 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 authors think that someone did a great job and ask for 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. rights for such a person.

As most stringsString A string is a translatable part of the software. A translation consists of a multitude of localized 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 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. 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 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. 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 blockBlock Block 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. 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.