l10n: (Nextcloud integration only) use Transifex localization workflow

[p-bo]

Hello,
(only for lang files in https://github.com/the-djmaze/snappymail/tree/master/integrations/nextcloud/snappymail/l10n )
would it be possible to follow instructions on:
https://docs.nextcloud.com/server/latest/developer_manual/basics/front-end/l10n.html#adding-translations
...and gain benefits from work of whole Nextcloud translators community for users of your app please (as it was for Rainloop)?

Don't worry, it shouldn't take you much time - just open issue on https://github.com/nextcloud/docker-ci/issues/new/choose (choose Request translations). And you will get checklist as for example this: nextcloud/docker-ci#426 and that repo admin(s) are keen to help with that process.

Thanks :-)

[the-djmaze]

I've tried transifex, but it failed.
Also RainLoop added incorrect localization strings which makes it complex.
Not to mention the JSON format it is now.

However, the search for easy translating is still on my mind.

[p-bo]

Also RainLoop added incorrect localization strings which makes it complex.

This was in times, when Rainloop project was active and part of continuous translation workflow - removed then there nextcloud/docker-ci@f958786 - right? (understood in sense that Rainloop Nextcloud integration was translated this way, but there were problems you mentioned?)

Not to mention the JSON format it is now.

Must admit that don't understand - it is standard among all Nextcloud apps - for example here: https://github.com/nextcloud/server/tree/master/apps/dav/l10n

However, the search for easy translating is still on my mind.

That's great - looking for it :-)

[the-djmaze]

#1358