What are the most painful parts of contributing translations?
Testing them in context. I was going to propose nightly builds but saw that they already exist, so perhaps mentioning this in the document related to translation is enough.
What is working well?
The whole process works very well for the Android app, the translations “automagically” appear in the next version of the app and translators can focus on translation.
Can you recommend specific features in Weblate/GitLab/gettext/etc that will improve things?
GitLab Pages (which I believe it’s whats used) accepts other static pages generators. Jekyll is generally considered slow and this causes problems to F-Droid’s website generation in several languages. Not sure if using Hugo which seems to be much faster generating the static pages is an option. I know that F-Droid has created a fork of Jekyll so this might not be super easy.
What is the best way for developers to communicate to translators?
For urgent and important things (like the heads up about this thread, thank you) I prefer a direct e-mail. For general talk I suggest a Matrix room (“F-Droid Translation” for example) or something that can be used in the computer and integrates well with a mobile phone. Weblate allows comments but they are often not seen or answered until another translator happens to be on that string, a GitLab issue might not be appropriate, the IRC channel used by devs already has an specific use case, and the forum generates lots of e-mails that I honestly don’t read.
Anything else we should know?
Weblate allows to include a component in your language without annoying anyone else, but it’s not obvious to me how to remove it or if it’s even possible. The old document about translation said that the component called “Website Docs” was a requirement for a language to be included in the website, it’s not and the document has been updated, I’d like to remove that project from our language.
Related to this, translators that start a new language might not have a clear picture about which components are the most important ones, where to start. This might be solved with documentation too (Transifex has an option to set priorities but I haven’t seen this in Weblate).