Making WordPress.org

Opened 18 months ago

Last modified 18 months ago

#6485 new feature request

Allow GTE's to manually release language pack for project

Reported by: fierevere's profile fierevere Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords:
Cc:

Description

Currently language packs are released dependent on amount of translated strings when they reach threshold (i.e. for plugins and themes its 90%),
once created language pack will be updated everytime despite amount of translated strings (it can fall below threshold).

Here are different scenarios for using it, notably this case:
https://make.wordpress.org/polyglots/2022/09/12/translating-for-the-user-isnt-it/
plugin or theme may have enormous count of promotional, advertising and even strings indendent for PRO version use.
Discussed in Slack meeting:
https://wordpress.slack.com/archives/C02RP50LK/p1663163184676919
Up and somewhat below.

This button shall IMO be available for GTE's only, so PTE's are still encouraged to get their project translated without asking for an exception.

Change History (3)

#1 follow-up: @NekoJonez
18 months ago

I thought about this after our meeting and I thought of this.

EG: I'm a GTE for nl_BE so, if this feature is implemented, I could do this for nl_BE. But, I'm PTE for all theme's & plugins in nl_NL and I think GTE's should be able to grant this permission as well to those kind of translators.

Also, thinking out loud... Doesn't this also involve a risk that a project never gets fully translated?

But all for the idea. It's one of the main reasons why I have this plugin installed on almost all the websites I work on: https://wordpress.org/plugins/force-update-translations/ So, I can have the language pack already.

#2 in reply to: ↑ 1 @fierevere
18 months ago

Replying to NekoJonez:

I thought about this after our meeting and I thought of this.

EG: I'm a GTE for nl_BE so, if this feature is implemented, I could do this for nl_BE. But, I'm PTE for all theme's & plugins in nl_NL and I think GTE's should be able to grant this permission as well to those kind of translators.

Also, thinking out loud... Doesn't this also involve a risk that a project never gets fully translated?

But all for the idea. It's one of the main reasons why I have this plugin installed on almost all the websites I work on: https://wordpress.org/plugins/force-update-translations/ So, I can have the language pack already.

Not all projects deserve full translation or even threshold translation, yes its an exceptional case and should be used by an expert before firing, a GTE. It is team collaboration after all.

force-update-translation is a great tool, but its for us , translators to check how things will look live

#3 @tobifjellner
18 months ago

If that would be easier to implement, we could for a starter limit access to the few people with global access. That would allow us to somewhat measure the need and it would also make sure that the tool isn't used to much, and that if there's a problem with the i18n structure of a plugin that we would also inform the relevant developers about the problem.

Note: See TracTickets for help on using tickets.