Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Transifex for continuous translation please #6

Closed
p-bo opened this issue Sep 21, 2022 · 6 comments
Closed

Use Transifex for continuous translation please #6

p-bo opened this issue Sep 21, 2022 · 6 comments
Assignees
Labels
enhancement New feature or request resolved

Comments

@p-bo
Copy link
Contributor

p-bo commented Sep 21, 2022

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?

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.

@rotdrop rotdrop self-assigned this Sep 21, 2022
@rotdrop rotdrop added the enhancement New feature or request label Sep 21, 2022
@rotdrop rotdrop mentioned this issue Sep 21, 2022
6 tasks
@p-bo
Copy link
Contributor Author

p-bo commented Oct 6, 2022

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 you can ask rakekniven if something is unclear to you. Hope it helps :-)

@p-bo
Copy link
Contributor Author

p-bo commented Oct 12, 2022

For motivation - this developer was very impressed how much work can be done by Nextcloud translators community :-)

@rotdrop
Copy link
Owner

rotdrop commented Oct 12, 2022

There is no need to convince me. Just buy me more time ...

@p-bo
Copy link
Contributor Author

p-bo commented Oct 12, 2022

Very sorry for this, don' wanted to stress you...

@rotdrop
Copy link
Owner

rotdrop commented Nov 11, 2022

Closed as resolved.

@rotdrop rotdrop closed this as completed Nov 11, 2022
@p-bo
Copy link
Contributor Author

p-bo commented Nov 11, 2022

Many thanks for implementing this! Much better efficiency for translators will result in much better experience for users :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request resolved
Projects
None yet
Development

No branches or pull requests

2 participants