Reconsider Language Packs

[kraftner]

I am aware of #37 and that it has been closed. But now that wp.org is moving translations out of the Plugins themselves and retrieves them via the Update API this threatens to break any site with a composer workflow that is not english-only.

Here is the make post explaining what is currently happening: Plugin Translations on WordPress.org

So I think the urgency of this issue has increased which I hope warrants a reconsideration.

koodimonni.github.io

@koodimonni has created a Composer-Dropin-Installer which seems to work around the issue of #43 cited as a reason for wontfix in #37. He created this for http://languages.koodimonni.fi/ (https://github.com/Koodimonni/koodimonni.github.io) @koodimonni even says this about his work:

I would like these to be included in Packagist or WPackagist. So use these as base for them if you want.

Maybe this is a viable approach and forces can be joined now that this is becoming a pressing issue.

[felixarntz]

+1. It would be amazing to have support for language packs, and it should be possible now that they are all provided by wordpress.org at a defined location.

Right now, I either have to make my setup's translation directory writeable or take care of all translations manually both of which are certainly not optimal solutions.

[tyrann0us]

I know I'm late to the party but there's https://github.com/inpsyde/wp-translation-downloader/ that helps you install WordPress language files with Composer.

[NoelLH]

This sounds like it would be good! There is a comment about WP core handling on #91 (see also https://github.com/outlandishideas/wpackagist/discussions/262) but it sounds like handling languages through Wpackagist ought to be possible regardless of your WP core installation method.

• Is that correct?
• Does anyone feel like taking on making a PR for this? I'm happy to get behind the idea and push for some time to be allocated to review and test.