[wp-hackers] Separating translations from plugin updates

Dion Hulse (dd32) wordpress at dd32.id.au
Tue Sep 25 08:25:50 UTC 2012

One of these days we'll get Language Packs into core:
(Although that tickets slated for 3.5 consideration, and the patch for core
is there, the rest of the infrastructure to support it just isn't quite yet

On 25 September 2012 18:10, John Blackbourn <johnbillion+wp at gmail.com>wrote:

> A plugin of mine in the WordPress.org plugin directory has been
> translated into several other languages by some generous people. When
> I'm sent a new translation I add it to the plugin, bump the version
> number, and commit it.
> This means I'm unnecessarily pushing out a plugin update for all those
> users who have no need for the new translation. I wonder whether a
> better translation deployment method could be introduced.
> My idea is that the plugin update API could be split into two, one for
> normal plugin updates as they are and one for translations. For
> example, if you have a Polish language pack installed on your site
> then when the plugin update check is performed it will alert you that
> a new or updated Polish translation is available in a similar manner
> to how plugin update notifications are displayed on the Plugins screen
> and the Updates screen.
> Just an idea. Thoughts?
> John
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list