Integrating with Weblate¶
Bases de Weblate¶
Structure du projet et des composants¶
Dans Weblate, les traductions sont organisées en projets et composants. Chaque projet peut contenir un certain nombre de composants et ceux-ci contiennent des traductions dans des langues individuelles. Le composant correspond à un fichier traduisible (par exemple GNU gettext PO (Portable Object) ou Ressources de chaînes Android). Les projets sont là pour vous aider à organiser les composants en ensembles logiques (par exemple pour regrouper toutes les traductions utilisées dans une application).
Additionally, components within projects can be structured using categories. Components can belong to a category, and categories can be nested.
En interne, chaque projet dispose par défaut de traductions de chaînes communes qui se propagent à travers les autres composants du projet. Cela allège le fardeau de la traduction répétitive et multiversion. La propagation de la traduction peut être désactivée par Configuration des composants en utilisant Permettre la propagation de la traduction au cas où les traductions devraient diverger.
Repository integration¶
Weblate is built to integrate with upstream version control repository, Traduction en continu describes building blocks and how the changes flow between them.
Voir aussi
Architecture overview describes how Weblate works internally.
User attribution¶
Weblate keeps the translations properly authored by translators in the version control repository by using name and e-mail. Having a real e-mail attached to the commit follows the distributed version control spirits and allows services like GitHub to associate your contributions done in Weblate with your GitHub profile.
This feature also brings in risk of misusing e-mail published in the version control commits. Moreover, once such a commit is published on public hosting (such as GitHub), there is effectively no way to redact it. Weblate allows choosing a private commit e-mail in Compte to avoid this.
Therefore, admins should consider this while configuring Weblate:
Such a usage of e-mail should be clearly described in service terms in case such document is needed. Mentions légales can help with that.
PRIVATE_COMMIT_EMAIL_OPT_INcan make e-mails private by default.
Importing a localization project into 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 Weblate components.
Alternatively, you can let Weblate set up a local-only repository containing all the translations without integration.
Récupérer les traductions mises à jour depuis Weblate¶
Weblate stores updated strings in a database and commits them to a local version-control repository. You can add a Weblate repository (when Exportateur Git is turned on) as an additional remote repository and fetch translation updates from it.
Prior to this, you might want to commit any pending local changes made in Weblate (see Archivages lazy). This can be done from the user interface (in the Repository maintenance), or from the command-line using Client Weblate.
Pushing changes can be automated if you grant Weblate push access to your repository and configure URL pour l’envoi du dépôt in the Configuration des composants, see Pushing changes from Weblate.
Alternatively, use API REST de Weblate to update translations so that they match the latest version from the upstream in your remote VCS repository.
Récupérer les modifications distantes dans Weblate¶
To fetch any strings recently updated in your remote VCS repository into Weblate, allow Weblate to pull from the upstream repository. This can be achieved in the user interface (in the Repository maintenance), or from the command-line using Client Weblate.
This can be automated by setting a webhook in your repository to trigger Weblate whenever there is a new commit. See Mise à jour des dépôts for more details.
If not using VCS integration, you can use the UI or API REST de Weblate to update the translations so that they match your codebase.
Voir aussi
Ajout de nouvelles chaînes¶
If your translation files are stored in a remote 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 Passerelle pour la qualité des chaînes sources to avoid introducing errors.
When translation files are separated from the code, the following ways can introduce new strings into Weblate.
Manually, using Add new translation string from Tools menu in the source language. You can choose between the radio buttons Singular and Plural inside the form. Select the appropriate form of the new translation string to be added.
Par programmation, en utilisant API
POST /api/translations/(string:project)/(string:component)/(string:language)/units/.By uploading source file as Replace existing translation file (this overwrites existing strings, so please ensure the file includes both old and new strings) or Add new strings, see Méthodes d’importation.
Note
The ability to add strings in Weblate requires Gérer les chaînes.
Mise à jour des fichiers de langue cible¶
For monolingual files (see Localization file formats), Weblate might add new translation strings present in the Fichier de langue de base mono-langue, and not in actual translations. It does not however perform any automatic cleanup of stale strings, as that might have unexpected results. If you still want to do this, please install the Nettoyer les fichiers de traduction add-on, which handles cleanup according to your requirements.
Weblate will also not try to update bilingual files when the source changes,
so if you need po files to be updated from pot, do it yourself by
using Update source strings Méthodes d’importation, or by using
the Mettre à jour les fichiers PO afin qu’ils correspondent au POT (msgmerge) add-on.
Indication
Source string extraction tools, such as xgettext or lupdate, need to be executed outside of Weblate.
Introducing new strings¶
You can add new strings in Weblate with Gérer les chaînes turned on, but it is usually better to introduce new strings together with the code changes that introduced them.
Monolingual formats need to be configured so that new strings are added to Fichier de langue de base mono-langue. This is typically done by developers, as they write the code. You might want to use a review process of those strings using Passerelle pour la qualité des chaînes sources.
Bilingual formats typically extract strings from the source code using some tooling (like xgettext or intltool-update). 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 Mise à jour des fichiers de langue cible.
Indication
Automating string extraction is presently out of scope for Weblate. It typically involves executing untrusted code what makes it more suitable for a generic continuous integration than localization-specific platform.
You might want to integrate this into your continuous integration pipelines to make new strings automatically appear for translation. Such pipeline should also cover Avoiding merge conflicts.
Gestion du dépôt du VCS local¶
Weblate stores all translations in its underlying version control repository. It is suggested to be connected to a remote one, but internal-only setup is also possible. The Repository maintenance allows controlling this repository.
Indication
With Traduction en continu, any changes are automatically pushed from the repository, so there is usually no need to manage it manually.
