Flux de travail de traduction#
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.
Personnalisation du flux#
In addition to configuration at Configuration du projet and Configuration des composants (as Activer les révisions, Autoriser les suggestions, Vote pour la suggestion, and Automatically accept suggestions), the translation workflow can be customized per language.
Site-wide workflow customization can be done while Changing language definitions.
Per-project customization can be done on each language page of the project.
All workflow settings can be overridden, the only limitation is that Activer les révisions 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
Note
Please be careful when using site-wide override as that applies to all projects (unless they have own overrides for a given language).
Accès à la traduction#
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.
États de traduction#
Each translated string can be in one of the following states:
- Non traduit
La traduction est vide. Selon le format du fichier, elle peut être stockée ou non.
- À vérifier
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
fuzzy
flag in the gettext file).- En attente de révision
La traduction est effectuée, mais non relue. Elle est stockée dans le fichier comme une traduction valide.
- Approuvé
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.
- Suggestions
Suggestions are stored in Weblate only and not in the translation file.
The states are represented in the translation files when possible.
Indication
If the file format you use does not support storing states, you might want to use the Marquer les traductions inchangées comme « À vérifier » add-on to flag unchanged strings as needing editing.
Traduction directe#
The most common setup for smaller teams, where anybody can translate directly. This is also the default setup in Weblate.
Any user can edit translations.
Suggestions are optional ways to suggest changes, when translators are not sure about the change.
Paramètre |
Valeur |
Note |
---|---|---|
Activer les révisions |
inactif |
Configuré au niveau du projet. |
Autoriser les suggestions |
actif |
Useful for users to be able to suggest when they are not sure. |
Vote pour la suggestion |
inactif |
|
Automatically accept suggestions |
0 |
|
Groupe de traducteurs |
Utilisateurs |
Ou Traduire avec per-project access control. |
Reviewers group |
N/A |
Non utilisé. |
Peer review#
With this workflow, anybody can add a suggestion, which needs approval from additional member(s) before it is accepted as a translation.
Any user can add suggestions.
Any user can vote for suggestions.
Les suggestions deviennent des traductions lorsqu’elles reçoivent un nombre prédéterminé de votes.
Paramètre |
Valeur |
Note |
---|---|---|
Activer les révisions |
inactif |
Configuré au niveau du projet. |
Autoriser les suggestions |
actif |
|
Vote pour la suggestion |
inactif |
|
Automatically accept suggestions |
1 |
You can set higher value to require more peer reviews. |
Groupe de traducteurs |
Utilisateurs |
Ou Traduire avec per-project access control. |
Reviewers group |
N/A |
Not used, all translators review. |
Dedicated reviewers#
With dedicated reviewers you have two groups of users, one able to submit translations, and one able to review them to ensure translations are consistent and that the quality is good.
Any user can edit unapproved translations.
Le réviseur peut approuver/désapprouver des chaînes.
Reviewer can edit all translations (including approved ones).
Les suggestions permettent également de suggérer des modifications pour les chaînes approuvées.
Paramètre |
Valeur |
Note |
---|---|---|
Activer les révisions |
actif |
Configuré au niveau du projet. |
Autoriser les suggestions |
inactif |
Useful for users to be able to suggest when they are not sure. |
Vote pour la suggestion |
inactif |
|
Automatically accept suggestions |
0 |
|
Groupe de traducteurs |
Utilisateurs |
Ou Traduire avec per-project access control. |
Reviewers group |
Réviseur |
Or Review with per-project access control. |
Turning on reviews#
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 Fichier de langue intermédiaire, 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.
Relectures des chaînes sources#
With Activer la révision des chaînes sources 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 Dedicated reviewers — 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.