WordPress.org

Making WordPress.org

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#1390 closed enhancement (fixed)

Add client-side JS warnings for submitted strings

Reported by: dd32 Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords:
Cc:

Description

Translators are required to submit their strings before they can get any feedback as to whether the string is going to trigger any GlotPress Warnings. It's a pretty bad user experience, and even worse for the approver when they're required to reject all the translation attempts.

We should add some client-side JS warnings for potential issues, looking through the #polyglots-warnings channel, the most common issues are the following:

  • Bad Placeholders or missing placeholders
  • Invalid HTML, or missing tags
  • Improper line endings (Extra trailing line, not including one, etc.)

Some of these cases should be fixed with GlotPress #511, however it's still not optimal.

Change History (3)

#1 @dd32
4 years ago

In 2066:

Translate: Add a GlotPress plugin which performs basic translation checks in Javascript and warns about potential warnings before actually submitting the string.

This allows for the submitter to correct the [potential] issue before submitting it into the approval queue. Many submitters don't reject their own incorrect suggestions after adding a replacement string.

See #1390

#2 @dd32
4 years ago

  • Resolution set to fixed
  • Status changed from new to closed

Hasn't been any reports of it breaking.. yet.

#3 @dd32
4 years ago

In 2082:

Translate: JS Warnings: Add support for the 3rd translateion UI HTML format.
The GlotPress output has nothing that links the text field to the actual original display, so we're using DOM transversal, which can be.. interesting :)

See #1390

Note: See TracTickets for help on using tickets.