Weblate

Weblate can handle translations semi-automatically if you give it push access to your repository. Set up notification hooks, configure the push URL in your Component settings, and enable 'Push on commit' to automate the process.

Merge conflicts occur when translation files are changed in both Weblate and the upstream repository. To resolve them, commit all pending translations in Weblate, merge the repository, and fix conflicts locally. Weblate uses shallow clones by default, so ensure your upstream repository is up-to-date.

Use Git submodules to separate translations from source code. Create a repository for your translation files, add it as a submodule to your code, and link Weblate to this repository instead of the main one.

Weblate offers several review workflows. You can subscribe to notifications for changes, use the review tool in the translation view to browse recent contributions, or check others' translations since a specific date.

Use the Comments tab under the translation context to provide feedback or discuss source strings with other translators.

Weblate uses shared translation memory. You can import existing translation memory files into Weblate and use the import functionality to load them as translations, suggestions, or translations needing review.

Weblate supports pushing translation changes within one Project configuration. If enabled (default), changes made in one component are automatically propagated to others, keeping translations synchronized even across diverged branches.

The Weblate repository is stored under the DATA_DIR directory as vcs/ / /. For direct access, use SSH. For anonymous access, run a Git server or use Weblate's built-in Git exporter.