Çeviri iş akışları

Using Weblate is a process that brings your users closer to you, by bringing you closer to your translators. It is up to you to decide how many of its 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 most usual examples listed here.

Translation access

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.

Çeviri durumları

Each translated string can be in one of following states:

Çevrilmemiş

Translation is empty, it might or not be stored in the file, depending on the file format.

Düzenlenmesi gerekli

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).

Onaylanmayı bekliyor

Translation is made, but not reviewed. It is stored in the file as a valid translation.

Onaylanmış

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.

Öneriler

Suggestions are stored in Weblate only and not in the translation file.

The states are represented in the translation files when possible.

İpucu

In case file format you use does not support storing states, you might want to use Değiştirilmemiş çevirileri “Düzenlenmesi gerekli” olarak imleme add-on to flag unchanged strings as needing editing.

Direct translation

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.

Setting

Değer

Not

Onaylama kullanılsın

kapalı

Configured at project level.

Öneriler kullanılsın

açık

It is useful for users to be able to suggest when they are not sure.

Öneri oylaması

kapalı

Öneriler kendiliğinden kabul edilsin

0

Translators group

Kullanıcılar

Or Translate with per-project access control.

Onaylayıcılar grubu

Kullanılamaz

Kullanılmıyor.

Akran değerlendirmesi

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.

  • Suggestions become translations when given a predetermined number of votes.

Setting

Değer

Not

Onaylama kullanılsın

kapalı

Configured at project level.

Öneriler kullanılsın

açık

Öneri oylaması

kapalı

Öneriler kendiliğinden kabul edilsin

1

You can set higher value to require more peer reviews.

Translators group

Kullanıcılar

Or Translate with per-project access control.

Onaylayıcılar grubu

Kullanılamaz

Not used, all translators review.

Dedicated reviewers

2.18 sürümünde geldi: 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.

  • Onaylayan dizgeleri onaylayabilir ve onayı kaldırabilir.

  • Reviewer can edit all translations (including approved ones).

  • Suggestions can also be used to suggest changes for approved strings.

Setting

Değer

Not

Onaylama kullanılsın

açık

Configured at project level.

Öneriler kullanılsın

kapalı

It is useful for users to be able to suggest when they are not sure.

Öneri oylaması

kapalı

Öneriler kendiliğinden kabul edilsin

0

Translators group

Kullanıcılar

Or Translate with per-project access control.

Onaylayıcılar grubu

Onaylayanlar

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 ManageSettings menu):

_images/project-workflow.png

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 Ara dil dosyası, 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.

digraph translations { graph [fontname = "sans-serif", fontsize=10]; node [fontname = "sans-serif", fontsize=10, margin=0.1, height=0, style=filled, fillcolor=white, shape=note]; edge [fontname = "sans-serif", fontsize=10]; subgraph cluster_dev { style=filled; color=lightgrey; label = "Development process"; "Developers" [shape=box, fillcolor="#144d3f", fontcolor=white]; "Developers" -> "Intermediate file"; } subgraph cluster_l10n { style=filled; color=lightgrey; label = "Localization process"; "Translators" [shape=box, fillcolor="#144d3f", fontcolor=white]; "Editors" [shape=box, fillcolor="#144d3f", fontcolor=white]; "Editors" -> "Monolingual base language file"; "Translators" -> "Translation language file"; } "Intermediate file" -> "Monolingual base language file" [constraint=false]; "Monolingual base language file" -> "Translation language file" [constraint=false]; }

Kaynak dizge onayları

With Kaynak onaylama kullanılsın 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.