WordPress.org

Making WordPress.org

Opened 3 years ago

Closed 2 years ago

Last modified 2 years ago

#1793 closed enhancement (fixed)

Display available plugin translations on plugin listing

Reported by: hlashbrooke Owned by:
Milestone: Priority: normal
Component: Plugin Directory Keywords:
Cc:

Description

As part of the redesign, the available translations of the plugin are no longer shown on the plugin listing. This was a really handy feature in the old directory and it would be great if we could keep it in for the redesign. Slipping it in under the 'support' widget in the sidebar would be fine I would think.

Is this possible and warranted, or has this decision already been made?

Attachments (1)

Screen Shot 2016-07-01 at 9.42.59 AM.png (36.3 KB) - added by hlashbrooke 3 years ago.
The list of translations in the old directory (for reference)

Download all attachments as: .zip

Change History (12)

@hlashbrooke
3 years ago

The list of translations in the old directory (for reference)

#1 @casiepa
3 years ago

The top bar on a xx.wordpress.org site where no translation package is found for the plugin is a great improvement, but once a package exists, there are no further links to translations and that is a big step backwards. See also https://make.wordpress.org/meta/2016/05/20/plugin-directory-prototypes-single-view/#comment-8363
Pascal.

#2 follow-up: @hlashbrooke
3 years ago

Just saw Sam's comment on that thread:

Unlike in the old directory, there won’t be a list of translations in the sidebar. However, in the new directory, there will be a green bar, front-and-center, on all plugin directory pages if the plugin directory is available in your language. Once there, the text of the green bar will update if the current plugin is not available in your language, as a prompt to encourage new translators. You can test this now, though we’re still working on the final pieces of it.

I get that we can push people to the locale directory for a plugin (which is great of course), but in many cases the plugin is localised, but the readme is not. In those cases there wouldn't be a locale directory page, but the plugin would still be available in the language needed and there would be no way for the user to know that unless they manage to get to the GlotPress project page for the plugin, which most users won't be able to find.

Listing the languages in which the plugin is available would be a great way to combat this and we have plenty of space in the sidebar for a widget like that, so it wouldn't be a huge stretch to add it in.

#3 in reply to: ↑ 2 @samuelsidler
3 years ago

See also #1259.

I don't think we should display all translations in the sidebar. Instead, we should do two things:

  1. Show the green bar with the relevant languages for each user, as we're already doing.
  2. Show a list of all available translations in the Contributors & Developers section.

Replying to hlashbrooke:

I get that we can push people to the locale directory for a plugin (which is great of course), but in many cases the plugin is localised, but the readme is not. In those cases there wouldn't be a locale directory page, but the plugin would still be available in the language needed and there would be no way for the user to know that unless they manage to get to the GlotPress project page for the plugin, which most users won't be able to find.

I'm hopeful that this case is rarer and rare as more translations come through for readmes, and the community grows. But, either way, the green banner shows on the plugin page when the plugin is available in a specific language, regardless of readme translation.

Listing the languages in which the plugin is available would be a great way to combat this and we have plenty of space in the sidebar for a widget like that, so it wouldn't be a huge stretch to add it in.

Just because there's whitespace doesn't mean we need to fill it. :)

I find it much more valuable to send users to the relevant locale site, even if the readme isn't translated, so they can decide for themselves.

Have you seen what we do when a plugin isn't translated into the locale of the site you're on?

#4 @hlashbrooke
3 years ago

@samuelsidler: That sounds reasonable then. Especially if we do this:

Show a list of all available translations in the Contributors & Developers section.

I didn't mean we had to use the sidebar - that just seemed like a logical place to me, but the Contributors & Developers section probably makes more sense I think :)

This ticket was mentioned in Slack in #polyglots by coachbirgit. View the logs.


3 years ago

This ticket was mentioned in Slack in #meta-i18n by netweb. View the logs.


3 years ago

#7 @Presskopp
3 years ago

Despite on what's coming regarding where and how:

Shouldn't the link on wordpress.org/plugins-wp/pluginname/ under Contributors & Developers Read more Translation Contributors go to translate.wordpress.org/projects/wp-plugins/pluginname/contributors
If not, it should better be called differently, like "Translations"?

And / or a prominent "Translate this plugin"-Button would be nice.

Version 0, edited 3 years ago by Presskopp (next)

This ticket was mentioned in Slack in #meta-i18n by sergey. View the logs.


2 years ago

#9 @Ipstenu
2 years ago

  • Keywords close added; needs-patch removed

We've done this, so it can be closed :)

#10 @SergeyBiryukov
2 years ago

  • Keywords close removed
  • Resolution set to fixed
  • Status changed from new to closed

Closing as fixed in [5218].

The section should list the user's preferred languages first, created #2689 for that.

#11 @SergeyBiryukov
2 years ago

The section could also use a header to be more prominent, see #2685.

Note: See TracTickets for help on using tickets.