WordPress.org

Making WordPress.org

Opened 4 months ago

Last modified 10 days ago

#4525 reviewing enhancement

Add insights to the plugin language packs page

Reported by: ramiy Owned by: tellyworth
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords: 2nd-opinion has-patch
Cc:

Description

This ticket is about the Plugin language packs page.

https://wordpress.org/plugins/site-health-manager/ (Main plugin page)
https://translate.wordpress.org/projects/wp-plugins/site-health-manager/
https://translate.wordpress.org/projects/wp-plugins/site-health-manager/contributors/
https://translate.wordpress.org/projects/wp-plugins/site-health-manager/language-packs/ (This page)


The main plugin page displays the number of languages the plugin has ( on the sidebar - Languages: See all 9 ).

The problem is that the number of languages is not the same as the number of updated languages. It only represents the total language packs created.

I would like to see in the plugin language packs page more data, not only a dumb list. I would like to see insights and maybe a graph like the one we currently have in the contributors page.

Extra data to display:

  • Total number of language packs
  • Current plugin version
  • The number of packs for the current version
  • The number of packs for older version.
  • Pie Chart displaying languages packs by version.

The chart can show plugin developers if the languages packs are mainly for obsolete versions or for the latest version. This single chart is much more useful than the list of languages.

Attachments (2)

4525.png (177.3 KB) - added by ramiy 4 months ago.
4525.patch (1.8 KB) - added by ramiy 4 months ago.
initial patch (not tested)

Download all attachments as: .zip

Change History (9)

#1 @tobifjellner
4 months ago

Almost only the plugin developer himself/herself may know how big differences there are in the strings between various versions.
This can still be a good piece of information to add.

But perhaps even better might be some graphics/diagram based on "How many percent of the strings in current stable version are translated in the latest available language pack". However – this metric can be demanding to create: If a plugin previously was translated to, say, 98% then a language pack got created, since the threshold of 95% was met. If later new strings were added, the translated percentage may have dropped to 50%. Even if someone after that again translated 40% and brought the translation to 90%, the latest language pack still matches only 50% of the strings.

@ramiy
4 months ago

@ramiy
4 months ago

initial patch (not tested)

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.


4 months ago

#3 @tellyworth
4 months ago

What is the problem that this is intended to solve? How would a plugin author make use of this data? What would it enable them to do?

#4 @ramiy
4 months ago

  • Keywords has-patch added; needs-patch removed

@tellyworth Good questions! here are the answers:

What is the problem that this is intended to solve?

Currently a plugin author doesn't really know how many of his language packs are updated to the latest plugin version. Unless he manually extracts the data from the language packs list - counting them one by one.

How would a plugin author make use of this data?

With this data, plugin authors can decide whether to focus resources on translations. For example if over 95% of my language packs are updated to the latest plugin version I will do nothing, but if only 40% of the language packs are updated to the latest version I will spend time translating my plugin or hire someone to do that.

What would it enable them to do?

Insights is the first step for better decision making. I'm sorry to say, but the language pack list is a useless list of raw data. A single pie chart provides a better visual representation of the data.

If you want to allow the plugin author do something on the page, we can replace the list with a table containing sortable columns. It will be much easier to detect language packs for older plugin version.

Last edited 3 months ago by ramiy (previous) (diff)

This ticket was mentioned in Slack in #meta by ramiy. View the logs.


4 months ago

#6 @tellyworth
2 months ago

  • Owner set to tellyworth
  • Status changed from new to reviewing

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.


10 days ago

Note: See TracTickets for help on using tickets.