Move frontend translation to vue-i18n

[hackathi]

This is nothing I particularly like to do, but gettext in vue is basically unsupported.

[hackathi]

Idea on how to do this:

• Convert gettext po files to vue-i18n syntax.
• Yank out all translation from grocys php scripts. This needs some work, but is perfectly doable.
• make __t and __n functions return custom directives so that when client-side vue compiles a template it got from the server, it will do all the translation.

For the transition period, I do not think that it is a wise idea to move view-by-view but component by component, and full views whenever all (or most) components on a page have transitioned to vue. This also means that for the moment, we cannot use vue-runtime but need full vue that includes the template compiler, which makes things a bit slower. But that's okay for the moment; and most views aren't that complex anyway.

[hackathi]

On another note, grocy historically used transifex to do collaborative i18n.

I don't want to force people to create yet another account, but fortunately there is https://github.com/lokalise/i18n-ally which does the same thing all within git and github. Editing a translation would then just be sending another PR.

Unfortunately, I cannot tell how accessible that is to non-programmers.

[mohe2015]

On another note, grocy historically used transifex to do collaborative i18n.

I don't want to force people to create yet another account, but fortunately there is https://github.com/lokalise/i18n-ally which does the same thing all within git and github. Editing a translation would then just be sending another PR.

Unfortunately, I cannot tell how accessible that is to non-programmers.

Isn't it possible to keep using transifex (or weblate if transifex doesn't support that format)?
https://docs.transifex.com/formats/json/structured-json seems to look different but https://docs.weblate.org/en/latest/formats.html#json seems to look correct.

[hackathi]

Maybe it's just me, but from a privacy standpoint, all those cloud services put me off.

Self-Hosted weblate would be an option, but that would mean that I would have to run another public facing service. Not that I can't do that, but in my opinion that just adds to my workload with no real benefit – besides that potential translators don't have to install VS Code and the i18n-ally extension (and use git and github).

I value users' privacy more than keeping the accessibility bar ultra low. I'd much rather write a how-to in the docs/ folder. What I definitely do not want is to be locked into one service (which grocy seems to be) through which all translations have to be managed period (as in: you can't just add translation to the languages you know while developing a feature).

[mohe2015]

Maybe it's just me, but from a privacy standpoint, all those cloud services put me off.

I would argue that we could switch weblate to self-hosted any time so it's not really a cloud service in that sense.

Self-Hosted weblate would be an option, but that would mean that I would have to run another public facing service. Not that I can't do that, but in my opinion that just adds to my workload with no real benefit – besides that potential translators don't have to install VS Code and the i18n-ally extension (and use git and github).

I don't think we need to go selfhosted weblate as long as the official service works fine for us. But this would allow us to selfhost anytime so we don't really have a dependence on them.
I don't know who translated in the past but I could imagine that the amount of translators would be way higher if we use existing established tools that also don't need any knowledge about git and github. You could also argue that many of the translators possibly have no github account.

I value users' privacy more than keeping the accessibility bar ultra low. I'd much rather write a how-to in the docs/ folder. What I definitely do not want is to be locked into one service (which grocy seems to be) through which all translations have to be managed period (as in: you can't just add translation to the languages you know while developing a feature).

As far as I understand it (https://docs.weblate.org/en/latest/admin/continuous.html) (https://docs.weblate.org/en/latest/vcs.html) weblate is pretty cooperative with adding translation changes in the repository.

[hackathi]

I understand your point.

Let's use weblate then, if it does automatic syncing, I'm good.

[hackathi]

I also just noticed that weblate is based in the EU, so I have a lot less concerns regarding data protection and privacy.