Kakifrucht Sorry for the late reply, as @rob006 said, it's a fact that the Spanish formal registry is behind, the maintenance is much more tedious (especially after getting used to Weblate...) and is done as we all did before using Weblate, file by file, personally with some vscode extensions to facilitate especially the tasks of comparison with the informal registry to find updates or additions of new strings.
Regarding conflicts with the bot, I have not had any problems, when changes are made to the formal registry, it is done directly in locale/en-ES-formal, so I doubt the bot knows about the existence of this file.
Going back to managing a formal registry, I have to say it's not optimal and I've been looking for a long time for a better solution to handle this and improve maintenance/quality as it takes an awful long time to check everything.
Kakifrucht The optimal implementation would probably be to have a formal repository that only contains/outputs files/strings that contain translations. Then in this method we modify it to check whether formal is enabled in settings, and if so we override the formal translations over the informal ones, since they are mostly the same anyway.
This sounds really great, even if it would require manual maintenance, it would be a lot less work as it would only focus on the strings that need to be changed and their maintenance instead of everything, plus it would prevent the registry from falling behind as has happened many times with the Spanish formal one, better to use informal translations for the time being than nothing at all.
