Integracja z Weblate#
Struktura projektów i komponentów#
In Weblate translations are organized into projects and components. Each project can contain number of components and those contain translations into individual languages. The component corresponds to one translatable file (for example GNU gettext or Android string resources). The projects are there to help you organize component into logical sets (for example to group all translations used within one application).
Internally, each project has translations to common strings propagated across other components within it by default. This lightens the burden of repetitive and multi version translation. The translation propagation can be disabled per Konfiguracja komponentu using Zezwól na propagację tłumaczenia in case the translations should diverge.
Importowanie projektu lokalizacyjnego do Weblate#
Weblate has been developed with VCS integration in mind as it’s core feature, so the easiest way is to grant Weblate the access to your repository. The import process will guide you through configuring your translations into components.
Alternatively, you can use Weblate to set up a local repository containing all the translations without integration.
Pobieranie zaktualizowanych tłumaczeń z Weblate#
Weblate stores updated strings in a database and commits them to a local version control repository. You can add Weblate repository (when Eksporter Git is turned on) as additional remote and fetch translations update from it.
Prior to this, you might want to commit any pending changes (see Leniwe zatwierdzenia). You can do so in the user interface (in the Repository maintenance) or from the command-line using Klient Weblate.
Alternatively, you can use REST API Weblate to update translations to match their latest version.
Pobieranie zdalnych zmian do Weblate#
To fetch the strings newly updated in your repository into Weblate, just let it pull from the upstream repository. This can be achieved in the user interface (in the Repository maintenance), or from the command-line using Klient Weblate.
This can be automated by setting a webhook in your repository to trigger Weblate whenever there is a new commit, see Aktualizacja repozytoriów for more details.
If you’re not using a VCS integration, you can use UI or REST API Weblate to update translations to match your code base.
Dodawanie nowych ciągów#
In case your translation files are stored in a VCS together with the code, you most likely have an existing workflow for developers to introduce new strings. Any way of adding strings will be picked up, but consider using Quality gateway for the source strings to avoid introducing errors.
When the translation files are separate from the code, there are following ways to introduce new strings into Weblate.
Manually, using Add new translation string from Tools menu in the source language.
Programowo, używając API
By uploading source file as Replace existing translation file (this overwrites existing strings, so please make sure the file includes both old and new strings) or Add new strings, see Metody importu.
Availability of adding strings in Weblate depends on Zarządzaj ciągami.
Aktualizowanie plików języka docelowego#
For monolingual files (see Obsługiwane formaty plików) Weblate might add new translation strings not present in the Jednojęzyczny bazowy plik języka, and not in actual translations. It does not however perform any automatic cleanup of stale strings as that might have unexpected outcomes. If you want to do this, please install Wyczyść pliki tłumaczenia add-on which will handle the cleanup according to your requirements.
Weblate also will not try to update bilingual files in any way, so if you need
po files being updated from
pot, you need to do it yourself
using Update source strings Metody importu or using
Zaktualizuj pliki PO, aby dopasować POT (msgmerge) add-on.
Introducing new strings#
You can add new strings in Weblate with Zarządzaj ciągami turned on, but it is usually better to introduce new strings together with the code changes that introduced them.
Monolingual formats need addition of the new string to Jednojęzyczny bazowy plik języka. This is typically done by the developers during developing the code. You might want to introduce review of those strings using Quality gateway for the source strings.
Bilingual formats typically extract strings from the source code using some tooling. Follow your localization framework documentation for instructions how to do that. Once the strings are extracted, there might be an additional step needed to update existing translations, see Aktualizowanie plików języka docelowego.
You might want to integrate this into your continuous integration pipelines to make new strings automatically appear for translation. Such pipeline should also cover Unikanie konfliktów scalania.
Zarządzanie repozytorium kontroli wersji#
Weblate stores all translation the version control repository. It can be either connected to upstream one, or it can be only internal. The Repository maintenance lets you manipulate with the repository.
With Ciągła lokalizacja the repository is automatically pushed whenever there are changes and there is usually no need to manually manipulate with it.