Difference between revisions of "TDE Weblate Translation Workspace"
imported>SlavekB (Initial TDE Weblate page) |
imported>SlavekB (Added section on integration with TGW) |
||
| Line 19: | Line 19: | ||
[[File:TDE_Weblate_intro.png|321px]] |
[[File:TDE_Weblate_intro.png|321px]] |
||
| + | <br/><br/> |
||
| + | |||
| + | =='''Integration with TGW'''== |
||
| + | |||
| + | TDE Weblate manages its own clone of repositories, but is very tightly integrated with TGW. |
||
| + | |||
| + | Commits to TGW automatically invokes the update repository in TDE Weblate. If the translation template is updated, TDE Weblate will automatically update the translation files and immediately push them back to TGW. The translation files are therefore primarily maintained by the TDE Weblate. |
||
| + | |||
| + | During work on translations, individual translated strings are not immediately pushed into TGW. In order for translators to have enough time to work and also to check their translations, while avoiding too many small commits to TGW, pushing translations into TGW takes place after one day delay. |
||
| + | |||
| + | Work on translations is done on the master branch – on the latest development branch. Updating translations in a stable branch is not performed automatically, but are cherry-picked to stable branch by developers who have commit access to TGW. |
||
| + | |||
| + | Therefore translators do not need to work directly with GIT repositories. |
||
Revision as of 02:38, 17 January 2019
About Weblate
Weblate is an open source web-based translation management system with tight version control integration. It provides simple and clean user interface, quality checks and automatic linking to source files.
TDE Weblate
The TDE Weblate is our own instance of Weblate designed to manage TDE translations. It is tightly integrated with TDE Gitea Workspace (TGW). It provides:
- simple and clean user interface for work on translations
- integrated quality checks of translations
- displaying referenced source files in TGW
- retrieving translations and templates from TGW
- automatic update of translations according to the templates
- automated pushing of translations into TGW
- proper crediting of translators in commits
Thanks to TDE Weblate you do not have to learn how to work with the GIT, you do not have to deal how to get translation files from GIT, how to merge it back to GIT, how to update translation files by templates,… You can focus to work on translations.
Integration with TGW
TDE Weblate manages its own clone of repositories, but is very tightly integrated with TGW.
Commits to TGW automatically invokes the update repository in TDE Weblate. If the translation template is updated, TDE Weblate will automatically update the translation files and immediately push them back to TGW. The translation files are therefore primarily maintained by the TDE Weblate.
During work on translations, individual translated strings are not immediately pushed into TGW. In order for translators to have enough time to work and also to check their translations, while avoiding too many small commits to TGW, pushing translations into TGW takes place after one day delay.
Work on translations is done on the master branch – on the latest development branch. Updating translations in a stable branch is not performed automatically, but are cherry-picked to stable branch by developers who have commit access to TGW.
Therefore translators do not need to work directly with GIT repositories.