[wp-meta] [Making WordPress.org] #5152: Put a limit on adding new translation after multiple warnings

Making WordPress.org noreply at wordpress.org
Thu Apr 16 05:53:59 UTC 2020


#5152: Put a limit on adding new translation after multiple warnings
--------------------------------------+----------------------
 Reporter:  Nao                       |      Owner:  dd32
     Type:  enhancement               |     Status:  assigned
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+----------------------
 There should be some kind of block for users to enter poor quality
 translation suggestions, including unreviewed machine-translated text.

 These are some points I tried to gather to avoid wrongly flagging novice
 translators who are just making some mistakes as they learn while giving a
 hard stop to users who try to add translations that burden locale teams.

 == Idea ==
 For both file upload (import) & manual entry, put a limit on a user after
 their translations have a certain number of warnings without correcting
 them.
 The limit can be a ban for a set period of time, or ban until mistakes are
 corrected (or both?).

 === Flag these warnings ===

 * HTML mangled: Certain patterns that are obvious signs of a machine
 translation should be rejected (e.g. space around opening/closing tags).
 But we need to be aware regular contributors can make a typo.
 * Extra HTML attribute
 * Placeholders missing or extra added

 === Ignore, or be lenient on these warnings ===

 * Different URL from the original: This is often necessary for pointing to
 localized docs.
 * Accidental newlines: should be automatically matched to the original.

 === Not sure about this ===
 * Missing/too many tags: Sometimes I explicitly do this for an `em`
 element (remove them and replace them with a different way of emphasis)
 since italic text is not common in Japanese writing. I can't think of any
 other case though, and if other locales have something like this.

 == Other considerations ==

 * Extra flag for a user submitting to multiple locales with many warnings.
 * Banned user should be visible in #polyglots-warnings or somewhere
 private for GTEs or global mentors.
 * Never ban GTEs and PTEs on projects where they have validating rights.
 * Sometimes translators keep adding several translations with warnings
 because they don't know they can reject their own translation from before.
 Should we overwrite (or ask?) when a new translation is being submitted
 for a previously translated string by the same user?

 Related: #4171

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


More information about the wp-meta mailing list