Reconsider Language Packs

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.

No files or tests are identified. Start by reading the linked Plugin Translations on WordPress.org post and the discussions in issues #37 and #43, then review Composer-Dropin-Installer and koodimonni.github.io. Done would require a defined, agreed approach for handling WordPress language packs in Composer workflows.