Flux de travail de traduction
L’utilisation de Weblate est un processus qui rapproche vos utilisateurs de vous, en vous rapprochant de vos traducteurs. C’est à vous de décider du nombre de fonctionnalités que vous souhaitez utiliser.
The following is not a complete list of ways to configure Weblate. You can base other workflows on the most usual examples listed here.
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 that has a Translate permission for the project.
États de traduction
Chaque chaîne traduite peut être dans l’un des états suivants :
- 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
In case file format you use does not support storing states, you might want to use Marquer les traductions inchangées comme « À vérifier » add-on to flag unchanged strings as needing editing.
Traduction directe
This is most usual setup for smaller teams, anybody can directly translate. 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 |
Il est utile que les utilisateurs puissent suggérer quand ils ne sont pas sûrs. |
Vote pour la suggestion |
inactif |
|
Accepter automatiquement les 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 suggestions, and need 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 |
|
Accepter automatiquement les 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
Nouveau dans la version 2.18: The proper review workflow is supported since Weblate 2.18.
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 |
Il est utile que les utilisateurs puissent suggérer quand ils ne sont pas sûrs. |
Vote pour la suggestion |
inactif |
|
Accepter automatiquement les 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 a native speakers in the source language and do not provide desired quality of the source strings. The intermediate translation can help you in addressing this - there is additional quality gateway for the strings between developers and translators and users.
By setting Fichier de langue intermédiaire, this file will be used as source for the strings, but it will be edited to source language to polish it. Once the string is ready in the source language, it will be also available for translators to translate into additional languages.
Relectures des chaînes sources
With Activer la révision des chaînes sources enabled, the review process can be applied on the source strings. Once enabled, users can report issues in the source strings. The actual process depends on whether you use bilingual or monolingual formats.
For monolingual formats, the source string review behaves similarly as with Dedicated reviewers - once issue is reported on the source string, it is marked as Needs editing.
The bilingual formats do not allow direct editing of the source strings (these are typically extracted directly from the source code). In this case Source needs review label is attached to strings reported by translators. You should review such strings and either edit them in the source or remove the label.