Anyone is welcome to contribute translations for Syncthing. Just sign up at Hosted Weblate and get started on any existing language. The base (source) language is English, but you can easily cross-check from other already translated languages that you know. New languages can be requested using the Start new translation button at the bottom, but need approval from a maintainer.
Note that there is no formal review process, so please get in touch directly with others working on your language if there are disagreements and try working together.
The previously used translation platform, Transifex, is currently still in use for the Android app component. We plan to migrate that as well in the coming months.
Rebasing (1/57)
dropping e48b1e85bf16d70627a988144829813130861545 Translated using Weblate (Valencian) -- patch contents already upstream
Rebasing (2/57)
dropping 27dca4c65e9e4acac0290e3de5d19b0a1b569815 Translated using Weblate (Czech) -- patch contents already upstream
Rebasing (3/57)
dropping e17517f74b2a834e42a7889d15c1ea203b522cf8 Translated using Weblate (Danish) -- patch contents already upstream
Rebasing (4/57)
error: could not apply 63960e33b... Translated using Weblate (German)
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply 63960e33b... Translated using Weblate (German)
Auto-merging gui/default/assets/lang/lang-de.json
CONFLICT (content): Merge conflict in gui/default/assets/lang/lang-de.json
(1)
So it seems the automatic retrieval and committing of changes to our main repository creates conflicts when Weblate tries to rebase its commits on top of the updated upstream branch where they are already contained. Merging works fine however, so I switched it over to try a merge instead of a rebase. That fixed the immediate error, let’s see how it behaves in the coming weeks.
.