[wp-meta] [Making WordPress.org] #2921: Plugin Directory: No call to improve an existing translation

[Making WordPress.org]

#2921: Plugin Directory: No call to improve an existing translation
------------------------------+------------------------------------
 Reporter:  SergeyBiryukov    |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch         |
------------------------------+------------------------------------
Description changed by SergeyBiryukov:

Old description:

> Before the redesign, each plugin had a "Translations" widget in the
> sidebar with a list of languages the plugin is translated to and a nice
> green `Translate [plugin name]` button (see the screenshot).
>
> In the new design, the list of languages is hidden under "Development"
> tab. The locale banner at the top is supposed to be more prominent, but
> it doesn't cover all use cases the old widget did:
> * If the plugin doesn't have a language pack for a particular locale yet,
> a notice is displayed: `This plugin is not available in [language name]
> yet. <a href="%s">Help translate it!</a>`. So far so good.
> * If the plugin already has a language pack, there's another notice:
> `This plugin is also available in [language name].` The link leads to the
> plugin page on the corresponding Rosetta site, which might seem like a
> good idea, but there's no longer a call to improve the translation.
>
> It's still possible to go to the translation project from the plugin
> page, but the way to do that is a bit convoluted and isn't obvious for a
> translator at all:
> 1. Click "Development" tab.
> 2. Click "Read more" link.
>
> Suggestion: Add a call to improve the translation to the second notice:
> `This plugin is also available in [language name]. <a href="%s">Help
> improve the translation!</a>`.

New description:

 Before the redesign, each plugin had a "Translations" widget in the
 sidebar with a list of languages the plugin is translated to and a nice
 green `Translate [plugin name]` button (see the screenshot).

 In the new design, the list of languages is hidden under "Development"
 tab. The locale banner at the top is supposed to be more prominent, but it
 doesn't cover all use cases the old widget did:
 * If the plugin doesn't have a language pack for a particular locale yet,
 a notice is displayed: `This plugin is not available in [language name]
 yet. <a href="%s">Help translate it!</a>`. So far so good.
 * If the plugin already has a language pack, there's another notice: `This
 plugin is also available in [language name].` The link leads to the plugin
 page on the corresponding Rosetta site, which might seem like a good idea,
 but there's no longer a call to improve the translation.

 It's still possible to go to the translation project from the plugin page,
 but the way to do that is a bit convoluted and isn't obvious for a
 translator at all. There's a good chance they won't find the link unless
 they already know where to look:
 1. Click "Development" tab.
 2. Click "Read more" link.
 3. Click "Translate [plugin name] into your language."

 Suggestion: Add a call to improve the translation to the second notice:
 `This plugin is also available in [language name]. <a href="%s">Help
 improve the translation!</a>`.

--

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/2921#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org