Making WordPress.org

Opened 5 weeks ago

Last modified 5 weeks ago

#7995 new defect (bug)

Refactor i18n of email templates in Plugin Directory for improved translation UX

Reported by: tobifjellner's profile tobifjellner Owned by:
Milestone: Priority: high
Component: Plugin Directory Keywords:
Cc:

Description

When a user submits a plugin for the plugin directory, the results of several automated tests will generate one or more rather long messages to the submitting user.

A wonderful feature is that these messages can be translated. If you submit your plugin via a "Rosetta" version of the plugin directory, then feedback may be given in the same locale.

However, translating these long email templates is quite hard. One single string may contain quite a lot text. This makes the translation interface hard to use and navigate.

Also, translation contributors end up translating the same text chunks of texts several times:

  • Many paragraphs are identical between various email templates, but the translation memory only deals with "complete strings" as unit, so it won't kick in.
  • The "fuzzy logic" on the translation platform doesn't work well with overly long strings. If any single change is made to one of these large email templates, the translation needs to be done from scratch.

But there is a neat solution to this.

Please refactor the email templates so that each "string" for translation is one paragraph each. Where applicable, make sure to use exactly the same string every time for better reuse.

This would mainly need to be done in: https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/email/class-plugin-rejected.php

Change History (1)

#1 @dd32
5 weeks ago

Personally, I'm questioning the value of the translated emails completely.

The reviews are conducted 100% in english, and the handbooks are in english.

Having the Submission interface in a translated language doesn't that that much extra work, but the emails translations are probably never actually even used.

Since WordPress.org doesn't store locales per user, and doesn't store which locale the plugin submission came from, the emails WordPress.org sends about plugin rejections are likely in English 100% of the time.

I've raised this elsewhere, but I've also questioned if some of the emails shouldn't be shorter with a link to a handbook page (in english) that expands on items much more than is possible in the emails.

Note: See TracTickets for help on using tickets.