I wrote a simple system to simplify translation process by introducing a graphical interface and automation of some tasks. It was created mostly for Polish language package, but it should also scale for other languages too.

It stores configuration and all translations in separate repository and works in this way:

It reads sources for translations from configured plugins.
It saves source strings in sources directory and generates translation files for all configured languages.
Updated repository is fetched by Weblate (this is my private instance of this system, but it should be able to host Flarum translation). Weblate is an open source system which provides a graphical interface for translations and many cool features - it should make translations much simpler and more efficient.
Every translation done in Weblate should be committed to main repository with translations. So all translations data is always in https://github.com/rob006-software/flarum-translations.
Translations could be exported to separate repository - I'm already using this to generate translations for https://github.com/rob006-software/flarum-lang-polish. The English language is used as a fallback to bypass this bug.

This may look complicated, but everything except adding new extension/language and actual translation (using Weblate) could be automated. From extension maintainer perspective the only thing that he needs to do is to add his plugin to configuration - the plugin strings will be automatically fetched to all language packs and at worst case extension strings will not be translated (English strings will be used as a fallback). Language pack maintainer will no longer need to track all extensions - all new string will appear automatically in Weblate, and (with some config) all translations will be exported to his language pack extension.

The question is: are there any language packs maintainers who wants to work in this way? Any feedback about this approach?