While Weblate does support translating strings given in YAML files, the prelude does not have a structure that Weblate understands. As such, this adds a script to generate translation files that are usable by Weblate from the prelude, a script to update the prelude with the contents of those translation files, and the generated translation files themselves.
When Weblate opens PRs with translation changes, we'll need to then run the import script to apply those changes to the prelude, and we'll need to run the export script whenever the prelude translations change (or new translateable strings are added).
It may be possible to automate running those scripts using GitHub Actions, but that's something to investigate once the Weblate integration is fully up and running and we've had some experience with it.
pStyl3
commented
4 months ago
While Weblate does support translating strings given in YAML files, the prelude does not have a structure that Weblate understands. As such, this adds a script to generate translation files that are usable by Weblate from the prelude, a script to update the prelude with the contents of those translation files, and the generated translation files themselves.
When Weblate opens PRs with translation changes, we'll need to then run the import script to apply those changes to the prelude, and we'll need to run the export script whenever the prelude translations change (or new translateable strings are added).
It may be possible to automate running those scripts using GitHub Actions, but that's something to investigate once the Weblate integration is fully up and running and we've had some experience with it.