Qiaeru I would agree for open-source extensions, but since this is a closed source extension most translators will likely not have access to, I see more downsides managing translations publicly versus doing it manually. If I'm going to review every new translation anyway, it's much simpler for me to do it at the same time as the English text while working on the extension locally.
My 2 main concerns are incorrect translations due to lack of context, and the inability to control the release. I run this extension in production for myself and clients in French and there are times where I need an update to be shipped quickly including new French translations. Admittedly this hasn't happened in a while, but it's an ability I want to continue guaranteeing.
With the current set of tools I have a hard time believing a complex private extension with hundreds of translation strings can be reliably community-translated. There needs to be additional hints and comments in the source code made available for translators, and while I'm sure this could be achieved with Weblate I don't think we have anything close to this yet? If there's a way to add this to the extension source code I would definitely consider it and maybe it would allow to move French to the same level as other languages I don't speak.
As for the standardization of terms, luckily most terms are unique to the extension so there's no conflict with Flarum itself. Only exception is tags. I don't really like its French translation, hence why it's not used in my extension 🙉
rob006 I could exclude French translations for this extension on Weblate
I think that would be best for the time being.
I remember we discussed this for other of my extensions in the past. I thought we had talked about this one already, but that wasn't the case.
