Translating lots of app "summaries"

Would be a shame for the most active languages to wait around for the more dormant ones. Instead those involved could be put to good use by fixing upstream spelling errors, which are plentiful. (Did mark a lot of them as needing review in nb_NO)


Would having linkable translations be a good feature to add to Weblate?
The list is maintained, one can see its completion, but the fields belong to their respective (Hosted Weblate) counterparts.

@linsui I just made a bunch more summaries translatable.

Would be a shame for the most active languages to wait around for the
more dormant ones. Instead those involved could be put to good use by
fixing upstream spelling errors, which are plentiful. (Did mark a lot of
them as needing review in nb_NO)

@kingu I’m not sure what you are referring to when you say that the most
active languages have to wait around for the more dormant ones.

Would having linkable translations be a good feature to add to Weblate?
The list is maintained, one can see its completion, but the fields belong to their respective (Hosted Weblate) counterparts.

Can you explain?

Well German. It is the only language having reached completion. I imagine other resources would have been translated in German too by now if they were available.

It would be interesting to have long description translations hosted by F-Droid, but then have them be easily moved within Hosted Weblate, leaving a link behind.

Ideally then F-Droid would only host a central overview.

That is the best of both worlds, within reason. Assigning moderator rights to specific strings is also possible, but would require too much faffing about.

We already have the “link” mechanism for when the upstream app developer
takes our translation files. And submitting our translations upstream
is generally pretty easy too: just copy our translation files into the
upstream app’s source repo, and make a merge request.

As for getting more things translatable, the limitation is someone
spending the time to manage things. Any fdroiddata maintainer can
include the summaries for translation by running the
./tools/make-summary-translatable.py or anyone could do that via a
merge request as well.

Then the actual sync process is documented here:

Someone could take that over from me to make it happen more often.

I synced the most recent updates from fdroiddata, so there should be
more app summaries available for translation.

@hans

This app seems not in F-Droid now.

its probably new, and not yet on the website.

its up on staging already:
https://staging.f-droid.org/packages/me.kavishhukmani.watwitchstickers/

@hans My thinking is that as some languages finish the summaries, their users are seeing untranslated strings in the interim. I don’t think too many strings can be added to summaries.

6 languages translated already https://hosted.weblate.org/projects/f-droid/fdroiddata/
In my head we have lost the ability to draw from the hard work they have put in, because the direct editing is not there. The strings are in a sorry state, either sitting unfixed or untranslated.

The limiting factor is someone doing all the required bits of work. If
we have more contributors involved in the technical side of fdroiddata,
then these things are possible.

1 Like
Mastodon