Radni tokovi za prevođenje¶

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.

Prilagođavanje radnog toka¶

In addition to configuration at Konfiguracija projekta and Konfiguracija komponente (as Aktiviraj preglede, Omogući prijedloge, Glasanje za prijedlog, and Automatski prihvati prijedloge), the translation workflow can be customized per language.

Site-wide workflow customization can be done while Mijenjanje definicija jezika.

Per-project customization can be done on each language page of the project.

All workflow settings can be overridden, the only limitation is that Aktiviraj preglede needs to be turned on and can only be disabled in the per-language customization.

Primjenjuje se prva postojeća postavka:

Prilagodba jezika projekta
Prilagodba jezika
Postavke projekta/komponente

Napomena

Please be careful when using site-wide override as that applies to all projects (unless they have own overrides for a given language).

Limiting translation languages¶

Several settings can limit translation languages. They address different stages of the translation lifecycle and can be combined:

Control requests for languages that do not exist yet

Configure Dodavanje novog prijevoda at workspace, project, or component level. Components can inherit this setting. You can let users contact maintainers, point them to translation instructions, create the language file automatically, or disable adding new translations.

Project admins can still add a translation when Weblate can create its file. For components that do not inherit the project setting, change Dodavanje novog prijevoda individually or automate the changes using PATCH /api/components/(string:project)/(string:component)/.

Limit which translation files Weblate discovers

Configure Filtar jezika on each component. For example, ^(de|en|fr)$ limits the component to translation files whose language code is de, en, or fr. The filter applies while scanning the component file mask; it does not change permissions for translations that are already present.

Grant translation access only for selected languages

Use language-scoped teams when different users should be able to translate different languages. A team can only grant permissions, so remove any broader translation permission that would otherwise apply to the same users.

Restrict direct editing of an existing language

Open the language settings in the project, enable Customize translation workflow for this language in this project, and turn on Restrict direct editing.

Users with the Edit string when suggestions are enforced permission can continue editing directly. Other users can add suggestions when Turn on suggestions is enabled. Turn off suggestions as well to make the language editable only by privileged users.

The restriction can also be configured site-wide while Mijenjanje definicija jezika. A project-language customization takes precedence over the site-wide language setting.

Use suggestion voting

Turn on Suggestion voting to let users vote on suggestions. Voting alone does not restrict direct editing. A positive Automatically accept suggestions threshold also requires users without the Edit string when suggestions are enforced permission to submit suggestions. Use Restrict direct editing when this restriction should not depend on automatic acceptance.

Više informacija

Pristup prijevodu¶

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.

Translation states¶

Each translated string can be in one of the following states:

Neprevedeno

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

Treba urediti

Translation needs editing, this is usually the result of fuzzy matching or translator action. Depending on the file format it might be marked as needing edit (for example as it gets a fuzzy flag in the gettext file).

Treba prepraviti

Translation needs to be rewritten because of a source string change.

Treba provjeriti

State used for source/template strings that need developer review. It is typically set for new source strings imported from the VCS when the Source edit addon is enabled, or when a source string is reported for checking.

Translated / Waiting for review

Translation is made. The translated state is shown as „Waiting for review” if reviews are enabled.

Odobreno

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.

Samo-za-čitanje

String is read-only as a result of having read-only flag, being a non-editable source string, or marked such in the translation file.

Prijedlozi

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

The states are represented in the translation files when possible.

Savjet

If the file format you use does not support storing states, you might want to use the Označi nepromijenjene prijevode s oznakom „Treba preraditi” add-on to flag unchanged strings as needing rewriting.

Napomena

The Filtar za kvalitetu prijevoda determines which translation states are stored in the file.

Više informacija

Izravni prijevod¶

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.

Postavka	Vrijednost	Napomena
Aktiviraj preglede	isključeno	Konfigurirano na razini projekta.
Omogući prijedloge	uključeno	Korisno za korisnike kako bi mogli predložiti kada nisu sigurni.
Glasanje za prijedlog	isključeno
Automatski prihvati prijedloge	0
Grupa prevoditelja	Korisnici	Ili`Prevedi` s per-project access control.
Grupa pregledatelja	Bez podataka	Ne koristi se.

Pregled suradnika¶

Ovaj radni tok omogućuje da svatko može dodati prijedlog, koji moraju odobriti dodatni članovi prije nego što se prihvati kao prijevod.

Svaki korisnik može dodati prijedloge.
Svaki korisnik može glasati za prijedloge.
Prijedlozi postaju prijevodi kada dobiju unaprijed određeni broj glasova.

Postavka	Vrijednost	Napomena
Aktiviraj preglede	isključeno	Konfigurirano na razini projekta.
Omogući prijedloge	uključeno
Glasanje za prijedlog	uključeno
Automatski prihvati prijedloge	2	Možeš postaviti višu vrijednost kako bi zahtijevao/la preglede od više suradnika.
Grupa prevoditelja	Korisnici	Ili`Prevedi` s per-project access control.
Grupa pregledatelja	Bez podataka	Ne koristi se, svi prevoditelji pregledavaju.

Određeni pregledatelji¶

S određenim pregledateljima postoje dvije grupe korisnika: jedna koja može predlagati prijevode i druga koja ih može pregledati te osigurati dosljednost i kvalitetu prijevoda.

Svaki korisnik može uređivati neodobrene prijevode.
Pregledatelj može odobriti / odbiti izraze.
Pregledatelj može uređivati sve prijevode (uključujući odobrene).
Prijedlozi se također mogu koristiti za predlaganje promjena za odobrene izraze.

Postavka	Vrijednost	Napomena
Aktiviraj preglede	uključeno	Konfigurirano na razini projekta.
Omogući prijedloge	uključeno	Korisno za korisnike kako bi mogli predložiti kada nisu sigurni.
Glasanje za prijedlog	isključeno
Automatski prihvati prijedloge	0
Grupa prevoditelja	Korisnici	Ili`Prevedi` s per-project access control.
Grupa pregledatelja	Pregledatelji	Ili Pregledaj s per-project access control.

Uključivanje pregleda¶

Pregledi se mogu uključiti u konfiguraciji projekta u podstranici Radni tok u postavkama projekta (nalazi se u izborniku Operacije → Postavke):

Per-language reviews¶

To require review only for selected languages, first turn on Aktiviraj preglede for the whole project. Then open each project language page that should use different behavior, enable Customize translation workflow for this language in this project, and turn Enable reviews off for languages that should not require review.

Reviewers also need review access for the same language. Add them to a team whose roles include Review strings, and limit that team or the user membership to the language they should review. See Upravljanje kontrole pristupa projektima and Globalna kontrola pristupa for language-scoped access setup.

If approval buttons are not visible, check both parts of the setup: reviews have to be enabled for that translation, and the signed-in user has to have review permission for that language.

Sustav za provjeru kvalitete izvornih izraza¶

The original source language strings usually come from developers, since they write the code and provide the initial strings. However, developers are often not native speakers of the source language and do not provide the 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 the Datoteka posrednog jezika, this file is used for translating strings to the source language by translators/editors while it is owned by the developers (often using arbitrary languages such as en_devel). Once this stage is done, strings are available for translations to target languages, based on what is now a polished source language stored in the Jednojezična datoteka osnovnog jezika.

Više informacija

Konsolidacija izraza pomoću sekundarnog jezika¶

When Datoteka posrednog jezika cannot be used to consolidate the strings, you can choose one of the translations to act as a secondary language. The language can be configured in a project (Sekundarni jezik) or in a component (Sekundarni jezik). It is then shown to the translators while translating (see Sekundarni jezici) and can be optionally used as a source for machine translations (see Izvorni izrazi za strojno prevođenje).

This setup can be useful with mixed language source strings and consolidating them into a single translation, which is then used as a baseline for other work.

Pregledi izvornih izraza¶

With Aktiviraj preglede izvora 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 Određeni pregledatelji — once an issue with a source string is reported, the source string 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.

Više informacija