Add Fastlane app metadata to Weblate

[yurtpage]

The Fastlane app metadata description also needs to be translated, especially for F-Droid because it doesn't offer an auto-translation.

So please go to the https://translate.codeberg.org/projects/scee/ On left click on plus "Add new translation" component.

• Name: metadata
• Version control system: "Git"
• Source code repository: use weblate://scee/app
• Optional Key filter: ^(?!changelogs/.*$).+$ to exclude changelog from translation
• Press Continue

Once created go to the component's Settings / Version Control and change "Merge style" to "Merge"

[mnalis]

I think it would require changing how releases are done, and/or might probably delay them by several days?

Metadata is often updated just after translations are downloaded and release published just minutes after (which is obviously insufficient time for translators to be notified and allowing them to do their job).

Now, it is possible metadata/* would be updated after each PR is merged (and not just before release), so translators have some time if they check regularly, but I don't know how much it would complicate things... 🤷

[yurtpage]

The metadata is an app description for PlayStore and F-Droid. One the app is released the F-Droid itself will scan sources and update metadata and translations. It won't block anything.

[mnalis]

It won't block anything.

I'm not fully sure about F-droid procedure, but don't they pull fastlane metadata on the git-tagged release ? I.e. changes to SCEE/master after e.g. 60.3 is tagged won't be included there in F-droid 60.3 .apk release page ?

So what I meant to say, is that if SCEE tags e.g. 60.4 just now, any chance to update fastlane metadata (e.g. your translations) for SCEE 60.4 is over, and any changes to fastlane would only be included in 60.5 or whatever. If that makes sense?

[yurtpage]

Yes, people will see the translations only on the next update.

[mnalis]

Yes, people will see the translations only on the next update.

Oh, sorry; I misread you wanted to translate the fastlane changelogs too (which would be problematic). Translating just the short_description.txt + full_description.txt should be OK!

[yurtpage]

Changelogs may be translated too but most of time they look like "Bugfix, update translations". Additionally this makes a problem because translators see untranslated strings and tries to translate them without understanding if this important or not. That's why I recommended to add a key filter ^(?!changelogs/.*$).+$ to exclude changelog from translation

[yurtpage]

Friendly remind on this, this is a five minutes task

[mnalis]

@Helium314 if you wish, I can try adding it (according to instruction in original post), if you'll give me permission on codeberg translate (username is mnalis there too)? (adding me probably ain't any faster then doing it yourself, but increases the bus factor a little 😸 )

Currently clicking on + and Add new translation component. fails for me with: "You do not have permission to create components in any projects."

[mnalis]

ping @Helium314 could you add me to codeberg translate (or enable it yourself)? (Or don't you think translating fastlane description would be a good idea?)

[yurtpage]

@mnalis you may send a PR with a translation manually.