WordPress.org

Making WordPress.org

Opened 20 months ago

Closed 20 months ago

Last modified 7 weeks ago

#5081 closed enhancement (wontfix)

Delete project's language pack when below specific percentage

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

Description

Currently, a language pack is created when more than 95% of the project is translated. If new strings are created, the same pack is still available, but it's just updated when it gets to 95% again.

That makes some projects that are not actively being translated still having the language pack even if they have a small percentage of translated strings for the language.

I suggest that we delete automatically a language pack when they have a representation of less than 85% of strings translated. In this case, a project language pack will be generated when 95% is translated and would be available as long as it represents more than 85%.

Change History (7)

#1 @felipeloureirosantos
20 months ago

  • Keywords needs-patch dev-feedback added

#2 follow-up: @ocean90
20 months ago

  • Keywords needs-patch dev-feedback removed
  • Resolution set to wontfix
  • Status changed from new to closed

Even if the existing language pack doesn’t contain all translations it’s still better than nothing and may motivate new contributors to make the translation complete.

#3 in reply to: ↑ 2 @knutsp
20 months ago

  • Keywords 2nd-opinion added
  • Resolution wontfix deleted
  • Status changed from closed to reopened

Replying to ocean90:

Even if the existing language pack doesn’t contain all translations it’s still better than nothing and may motivate new contributors to make the translation complete.

Agree, until it becomes very low, like below 50%. And then the threshold for creating a language pack should be very low or jut above 50%.

Point is, if we accept this logic as guidance: when there is a high limit for creating it there must be a similar, almost as high limit for removing it. No limit for when to remove creates strange things:

Project A version 1.0 starts with 20 strings and soon gets 19 accepted translations. Some versions later it has 200 strings, but still only 19 translated (9.5%). Language pack remains.

Project B version 1.0 starts with 200 strings and gets 188 accepted translations. Some versions later the situation is the same (94%). No language pack.

#4 follow-up: @ocean90
20 months ago

  • Keywords 2nd-opinion removed
  • Resolution set to wontfix
  • Status changed from reopened to closed

I'm open to re-evaluate the current thresholds, but not on Trac. Can you start a post on https://make.wordpress.org/polyglots/ so this can be discussed during our next weekly chat?

Last edited 20 months ago by ocean90 (previous) (diff)

#5 in reply to: ↑ 4 @felipeloureirosantos
20 months ago

Hey there,

Thank you for the feedback @ocean90 and @knutsp!

Replying to ocean90:

I'm open to re-evaluate the current thresholds, but not on Trac. Can you start a post on https://make.wordpress.org/polyglots/ so this can be discussed during our next weekly chat?

The idea was to share this ticket on the next meeting's open floor, but it really makes more sense creating a post on p2 first. I'll do it as soon as possible, thank you for the guidance.

#7 @Otshelnik-Fm
5 months ago

See the screenshot: https://yadi.sk/i/e1kRInMcS0XLNQ or plugin link https://wordpress.org/plugins/wp-user-avatar/#developers
23 locales, 24 languages (so where is the truth?) But there is no truth!
Plugin translated into 1 language only - https://translate.wordpress.org/projects/wp-plugins/wp-user-avatar/

It turns out that the service is lying. And misleads the potential user of the plugin.
And this confusion threatens with a rating of 1 star for the author of the plugin.

Something definitely needs to be done about it

Note: See TracTickets for help on using tickets.