Use Transifex for continuous translation please

[p-bo]

Hello, it seems, that in past there was an attempt to use continuous localization platform:
#121

But as there is much bigger Nextcloud translators community on Transifex, 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?

Thanks :-)

[p-bo]

For instance:

• much more translators will get involved, because without it, they will newer even know about possibility to translate this app - example of benefits for project known in this manner for community of Nextcloud translators (app with recently added to this workflow, based on same request as this one): H2CK/oidc@937fc37 (se this and ongoing Nextcloud bot commits - translation of app is getting completed/improved in no time)
• also, as app is evolving, when some string(s) in app is/are changed/added, in case of continuous translation workflow translators are noticed intermediately and strings are translated before new version is released. In contrast with situation, that this change (in source strings) is only silently published in git repo and no one will (get) notice(d) till never version with untranslated strings get released (proactive vs retroactive).
• when one (of translators) will during using this app notice possibility to translate something in better manner, it is much efficient (especially for minor changes) to do this in translation tool than edit file directly in git. For example in case of one letter changes (misspelled words, etc.) has change directly in git such overhead (many steps to change just one letter), that these type of tweaks are rare due this (loss of quality for users)

To conclude: with continuous translation workflow, result is, that users of your app are getting more complete and more polished localization, so their user experience is much more pleasant.

[p-bo]

Don't worry, it is not rocket science - 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 you can ask rakekniven if something is unclear to you. Hope it helps :-)

[p-bo]

For motivation: This developer at first was not so fond of this approach, than he agreed to try and at the end, was very pleased with result! :-)

[p-bo]

Wrong repo (wrong link in Nextcloud app store because Nextcloud app metadata) - should be in https://github.com/nextcloud/jsxc.nextcloud

[comradekingu]

@p-bo The problem is what happens when you don't look at the actual translations before declaring victory.
Every single NC project on Weblate is doing better than even the central NC components.
The NC translators on TX is smaller community of users, and the tool itself facilitates drive-by translations.
Thus, size is a metric that works against arriving at quality translations on TX.

nc_money also uses erroneous locales, and if that is TX or not I don't know, but it has no way of changing it or even detecting it.