Descargar y cargar traducciones#

You can export files from a translation, make changes, and import them again. This allows working offline, and then merging changes back into the existing translation. This works even if it has been changed in the meantime.

Nota

Available options might be limited by access control settings.

Descargar traducciones#

From the project or component dashboard, translatable files can be downloaded in the Files menu.

The first option is to download the file in the original format as it is stored in the repository. In this case, any pending changes in the translation are getting committed and the up-to-date file is yield without any conversions.

You can also download the translation converted into one of the widely used localization formats. The converted files will be enriched with data provided in Weblate; such as additional context, comments or flags. Several file formats are available via the FilesCustomize download menu:

  • gettext PO (po)

  • XLIFF 1.1 with gettext extensions (xliff)

  • XLIFF 1.1 (xliff11)

  • TermBase eXchange (tbx)

  • Translation Memory eXchange (tmx)

  • gettext MO (only available when translation is using gettext PO) (mo)

  • CSV (csv)

  • Excel Open XML (xlsx)

  • JSON (only available for monolingual translations) (json)

  • JSON nested structure file (only available for monolingual translations) (json-nested)

  • Android String Resource (only available for monolingual translations) (aresource)

  • iOS strings (only available for monolingual translations) (strings)

Consejo

The content available in the converted files differs based on file format features, you can find overview in Translation types capabilities.

../_images/file-download.webp

Downloading components, categories or projects#

Translation files for a component, category or project can be downloaded at once via the Files menu. The download is always served as a ZIP file, and you can choose original or converted formats similarly as in Descargar traducciones.

Cargar traducciones#

Cuando haya efectuado sus cambios, utilice Cargar traducción en el menú Archivos.

../_images/file-upload.webp

Formatos de archivo admitidos#

Es posible cargar archivos en cualquier formato compatible, pero aun así se recomienda utilizar el mismo formato de archivo que el utilizado para la traducción; de lo contrario, algunas funciones podrían no convertirse apropiadamente.

Métodos de importación#

Estas son las elecciones presentadas al cargar archivos de traducción:

Añadir como traducción (translate)

Imported strings are added as translations to existing strings. This is the most common usecase, and the default behavior.

Only translations are used from the uploaded file and no additional content.

Añadir como sugerencia (suggest)

Imported strings are added as suggestions, do this when you want to have your uploaded strings reviewed.

Only translations are used from the uploaded file and no additional content.

Añadir como traducción que requiere edición (fuzzy)

Imported strings are added as translations needing edit. This can be useful when you want translations to be used, but also reviewed.

Only translations are used from the uploaded file and no additional content.

Reemplazar archivo de traducción existente (replace)

Existing file is replaced with new content. This can lead to loss of existing translations, use with caution.

Actualizar cadenas de origen (source)

Updates source strings in bilingual translation file. This is similar to what Actualizar archivos PO para que coincidan con POT (msgmerge) does.

Solo determinados formatos de archivo admiten esta opción.

Añadir cadenas nuevas (add)

Adds new strings to the translation. It skips the one which already exist.

In case you want to both add new strings and update existing translations, upload the file second time with Add as translation.

Esta opción está disponible solo cuando se activa Gestionar cadenas.

Only source, translation and key (context) are used from the uploaded file.

Conflicts handling#

Defines how to deal with uploaded strings which are already translated:

Change only untranslated strings (ignore)

Ignore uploaded translations which are already translated.

Change translated strings (replace-translated)

Replace existing translations with uploaded ones, but keep approved ones.

Change translated and approved strings (replace-approved)

Replace existing translations with uploaded ones, including approved ones.

Strings needing edit#

There is also an option for how to handle strings needing edit in the imported file. Such strings can be handle in one of the three following ways: «Do not import», «Import as string needing edit», or «Import as translated».

Overriding authorship#

With admin permissions, you can also specify authorship of uploaded file. This can be useful in case you’ve received the file in another way and want to merge it into existing translations while properly crediting the actual author.