Flujos de trabajo de traducción¶
Using Weblate raises quality, reduces manual work, and brings everyone involved in the localization process closer to each other. It is up to you to decide how many of Weblate features you want to make use of.
The following is not a complete list of ways to configure Weblate. You can base other workflows on the examples listed here.
Personalización del flujo de trabajo¶
In addition to configuration at Configuración de proyectos and Configuración de componentes (as Activar revisiones, Activar sugerencias, Votar sugerencias, and Aceptar sugerencias automáticamente), the translation workflow can be customized per language.
Site-wide workflow customization can be done while Cambiar las definiciones de idioma.
Per-project customization can be done on each language page of the project.
All workflow settings can be overridden, the only limitation is that Activar revisiones needs to be turned on and can only be disabled in customization.
The first existing setting applies:
Project-language customization
Language customization
The project/component settings
Nota
Please be careful when using site-wide override as that applies to all projects (unless they have own overrides for a given language).
Acceso de traducción¶
The access control is not discussed in detail as a whole in the workflows, as most of its options can be applied to any workflow. Please consult the respective documentation on how to manage access to translations.
In the following chapters, any user means a user who has access to the translation. It can be any authenticated user if the project is public, or a user with Translate permission to the project.
Estados de traducción¶
Each translated string can be in one of the following states:
- No traducidas
Translation is empty, it might or not be stored in the file, depending on the file format.
- Necesita edición
Translation needs editing, this is usually the result of a source string change, fuzzy matching or translator action. The translation is stored in the file, depending on the file format it might be marked as needing edit (for example as it gets a
fuzzyflag in the gettext file).- Revisión pendiente
La traducción se ha efectuado pero no se ha revisado. Está almacenada en el archivo y es válida.
- Aprobadas
Translation has been approved in the review. It can no longer be changed by translators, but only by reviewers. Translators can only add suggestions to it.
This state is only available when reviews are enabled.
- Sugerencias
Las sugerencias se almacenan solo en Weblate, no en el archivo de traducción.
Los estados se señalan en los archivos de traducción siempre que es posible.
Consejo
If the file format you use does not support storing states, you might want to use the Marcar traducciones sin cambios como «Necesitan edición» add-on to flag unchanged strings as needing editing.
Traducción directa¶
The most common setup for smaller teams, where anybody can translate directly. This is also the default setup in Weblate.
Cualquier usuario puede editar las traducciones.
Suggestions are optional ways to suggest changes, when translators are not sure about the change.
Configuración |
Value |
Nota |
|---|---|---|
Activar revisiones |
desactivada |
Configured at project level. |
Activar sugerencias |
activada |
Useful for users to be able to suggest when they are not sure. |
Votar sugerencias |
desactivada |
|
Aceptar sugerencias automáticamente |
0 |
|
Grupo de traductores |
Usuario/as |
O bien, traducir con control de acceso por proyecto. |
Grupo de revisores |
Sin datos |
No se utiliza. |
Revisión por pares¶
With this workflow, anybody can add a suggestion, which needs approval from additional member(s) before it is accepted as a translation.
Cualquier usuario puede añadir sugerencias.
Cualquier usuario puede votar sugerencias.
Las sugerencias se convierten en traducciones cuando reciben un número de votos determinado previamente.
Configuración |
Value |
Nota |
|---|---|---|
Activar revisiones |
desactivada |
Configured at project level. |
Activar sugerencias |
activada |
|
Votar sugerencias |
desactivada |
|
Aceptar sugerencias automáticamente |
1 |
You can set higher value to require more peer reviews. |
Grupo de traductores |
Usuario/as |
O bien, traducir con control de acceso por proyecto. |
Grupo de revisores |
Sin datos |
No se utiliza; todos los traductores revisan. |
Revisores dedicados¶
Al activar los revisores dedicados dividirá sus usuarios en dos grupos: uno será capaz de enviar traducciones, y el otro podrá revisarlas para garantizar que sean coherentes y su calidad sea buena.
Cualquier usuario puede editar traducciones no aprobadas.
Los revisores pueden aprobar o desaprobar las cadenas.
Los revisores pueden editar todas las traducciones (incluidas las aprobadas).
Es posible asimismo emplear las sugerencias para proponer modificaciones a las cadenas aprobadas.
Configuración |
Value |
Nota |
|---|---|---|
Activar revisiones |
activada |
Configured at project level. |
Activar sugerencias |
desactivada |
Useful for users to be able to suggest when they are not sure. |
Votar sugerencias |
desactivada |
|
Aceptar sugerencias automáticamente |
0 |
|
Grupo de traductores |
Usuario/as |
O bien, traducir con control de acceso por proyecto. |
Grupo de revisores |
Revisores |
Or Review with per-project access control. |
Activar las revisiones¶
Reviews can be turned on in the project configuration, from the Workflow subpage of project settings (to be found in the Manage → Settings menu):
Quality gateway for the source strings¶
In many cases the original source language strings are coming from developers, because they write the code and provide initial strings. However developers are often not native speakers in the source language and do not provide desired quality of the source strings. The intermediate translation can help you address this - there is an additional quality gateway for the strings between developers and translators.
By setting Archivo de idioma intermediario, this file is used for translating strings to the source language by translators/editors. Once this stage is done, strings are available for translations to target languages, based on what is now a polished source language.
Source strings reviews¶
With Activar revisiones de origen enabled, the review process can be applied for source strings. Once enabled, users can report issues with source strings. The actual process depends on whether bilingual or monolingual formats are in use.
For monolingual formats, source string review functions similarly to Revisores dedicados — once an issue with a source string is reported, it is marked as Needs editing.
Bilingual formats do not allow direct editing of source strings (these are typically extracted directly from the source code). In this case, a Source needs review label is attached to strings reported by translators. You should review such strings and either edit them in the source code, or remove the label.