Integración con Weblate#

Fundamentos de Weblate#

Estructura de los proyectos y los componentes#

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 PO (Portable Object) or Recursos de cadenas de Android). 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 Configuración de componentes using Permitir propagación de traducciones in case the translations should diverge.

Repository integration#

Weblate is built to integrate with upstream version control repository, Localización continua describes building blocks and how the changes flow between them.

Ver también

Architecture overview describes how Weblate works internally.

Atribución al usuario#

Weblate mantiene las traducciones correctamente realizadas por los traductores en el repositorio de control de las versiones utilizando el nombre y el correo electrónico. Tener un correo electrónico real adjunto al commit sigue el control de las versiones y permite a servicios como GitHub asociar tus contribuciones hechas en Weblate con tu perfil de GitHub.

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 Cuenta to avoid this.

Therefore, admins should consider this while configuring Weblate:

Importing 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 components.

Alternatively, you can use Weblate to set up a local repository containing all the translations without integration.

Recuperar traducciones actualizadas desde Weblate#

Weblate stores updated strings in a database and commits them to a local version control repository. You can add Weblate repository (when Git exporter is turned on) as additional remote and fetch translations update from it.

Prior to this, you might want to commit any pending changes (see Consignas diferidas). You can do so in the user interface (in the Repository maintenance) or from the command-line using Cliente de Weblate.

Pushing changes can be automated if you grant Weblate push access to your repository and configure URL de envío al repositorio in the Configuración de componentes, see Enviar cambios efectuados en Weblate.

Alternatively, you can use API REST de Weblate to update translations to match their latest version.

Recuperar cambios remotos hacia 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 Cliente de Weblate.

This can be automated by setting a webhook in your repository to trigger Weblate whenever there is a new commit, see Updating repositories for more details.

Si no utiliza una integración con un sistema de control de versiones, puede servirse de la interfaz de usuario o la API REST de Weblate para actualizar las traducciones para que se ajusten a su base de código fuente.

Añadir cadenas nuevas#

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 Quality gateway for the source strings to avoid introducing errors.

When translation files are separated from the code, the following ways can introduce new strings into Weblate.


The ability to add strings in Weblate requires Gestionar cadenas.

Updating target language files#

For monolingual files (see Formatos de archivo admitidos) Weblate might add new translation strings not present in the Archivo de base monolingüe, 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 Limpieza de archivos de traducción 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 Métodos de importación or using Actualizar archivos PO para que coincidan con POT (msgmerge) add-on.

Introducing new strings#

You can add new strings in Weblate with Gestionar cadenas 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 Archivo de base monolingüe. 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 (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 Updating target language files.


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 Evitar conflictos de fusión.

Managing version control repository#

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 Localización continua the repository is automatically pushed whenever there are changes and there is usually no need to manually manipulate with it.