In reply to @pitroig:sindominio.net

i put links to help.
In order for a new language to be added to f-droid.org, it must have:

Website component: 100% translated
Website Pages component: 100% translated
Data component: at least 10% translated
A blog post announcing support for the new language with an explanation the translation team.

https://f-droid.org/en/docs/Translation_and_Localization/

So many apps remains untranslated and many app authors simply don't know what to use.
We should create a docs page with description of current options: Crowdin, Hosted Weblate etc.

As a default option, can we make the https://toolate.othing.xyz/ as an official D-Droid Weblate instance?
The instance belongs to yzqzss and has a FAQ https://github.com/toolatebot/
Maybe map a subdomain to it like translate.f-droid.org so if that instance goes away we can migrate without changing links.

Then for each new app just register the app on the instance. The process probably can be automated.
All existing apps also needs for translations and we may not even ask their authors but the toolate can send a PR to them. This may result in unresolved conflicts when files were changed in source tree and the Weblate. So we probably should ask authors to use the Toolate themselves and have an admin right to resolve conflicts.
Some apps like Tailscacle won't accept translations for languages of countries that they don't support. This is a bad decision but their business. For them is may be configured manually.
Some apps are abandoned or their github repo is archived. I think such apps needs to be marked as outdated in the F-Droid.

This problem needs to be solved.