Suplimente

Add-ons provide ways to customize and automate the translation workflow. Admins can add and manage add-ons from the Operations ↓ Add-ons menu of each respective translation project or component. Add-ons can be also installed site-wide in Interfața de gestionare.

Sugestie

You can also configure add-ons using API, DEFAULT_ADDONS, or install_addon.

Add-ons that opt in to manual triggering can be run from add-on management or using the API. Results are recorded in the add-on activity log.

Add-ons that expose a component API show its base URL on the add-on’s API tab, alongside a link to the API root.

Add-ons can show Integration instructions above their settings. These explain how to connect your application or service to the add-on. Add-ons without configurable settings, such as Translation files CDN, show instructions without a settings form. Generated URLs and integration snippets are available after installation.

Add-ons are persistent administrative configuration. They run with their service identity in the scope where they are installed, rather than repeatedly using the permissions of the administrator who configured them. This ensures that equally authorized administrators see and save the same configuration, and that saving an unrelated change does not silently alter the add-on’s input scope. Removing or disabling the configuring administrator does not disable the add-on.

Project and category add-ons therefore include compatible restricted components in that scope. A component add-on can use inputs outside its destination component when documented by that add-on. Automatic translation determines its source components as follows:

• Direct automatic-translation actions use the acting user’s component access.

• A saved automatic-translation add-on uses its persistent administrative scope. Compatible components in the target project are eligible, including restricted components.

• Components in another project are eligible when that project contributes to shared translation memory. This includes restricted components even though they do not create shared translation-memory entries; the add-on reads the explicitly selected component as an administrative input instead.

Restricted components remain filtered from ordinary listings and direct access for users without an explicit grant or Edit project settings permission. Grant add-on management permissions only to users trusted with the add-on’s complete input and effect scope. See Domeniul de utilizare al echipelor and Acces restricționat.

Repository add-ons, including Descoperire componente, can be installed only on the component that owns the repository. Linked components show installed repository add-ons as inherited. Their available add-on list links to the owning component’s add-ons when you can manage it; otherwise the entry is unavailable.

Events that trigger add-ons

Add-on installation

Triggered when add-on is being installed.

Component update

Triggered whenever a change happens in a component such as:

• Strings are changed in the repository.

• A string is added.

• A new translation is added.

Daily

Triggered daily, but add-ons usually split the daily load between components depending on BACKGROUND_TASKS.

Event change

Triggered after a Change event is created.

Manual trigger

Triggered when an add-on is run manually from add-on management or the API.

Repository post-add

Triggered just after the new translation is added and committed.

Repository post-commit

Triggered just after the changes are committed.

Repository post-push

Triggered just after the repository is pushed upstream.

Repository post-remove

Triggered just after a translation is removed.

Repository post-update

Triggered whenever new changes are pulled from the upstream repository.

Repository pre-commit

Triggered just before the changes are committed.

Repository pre-push

Triggered just before the repository is pushed upstream.

Repository pre-update

Triggered just before the repository update is attempted.

Unit post-save

Triggered just after the string is saved.

Unit post-sync

Triggered after the string is synchronized with the VCS.

Unit pre-create

Triggered just after the newly created string is saved.

Addon-uri încorporate

AI quality evaluation

ID add-on:

weblate.ai.quality

Configurație:

service	Evaluation service	Alegerile disponibile: anthropic Anthropic openai OpenAI mistral Mistral ollama Ollama azure-openai Azure OpenAI
q	Înterogare
interval	Evaluation frequency	Alegerile disponibile: disabled Disabled daily Daily weekly Weekly monthly Lunar
on_change	Evaluate translation changes
on_update	Evaluate repository updates

Declanșări:

Add-on installation, Component update, Daily, Event change, Manual trigger

Evaluates existing translations using an LLM and records quality checks.

This add-on evaluates existing translations using an LLM service configured under Sugestii automate. It does not generate suggestions or change translations. Choose an Evaluation service from the configured LLM services; credentials and project overrides are reused.

The Query selects strings using the normal search syntax. By default, translated strings are selected. Source strings, read-only strings, and glossary entries are excluded. Each request includes all translation plural forms, source text, language information, string context, glossary terms, placeholders, and configured translation instructions. This data is sent to the selected provider.

Requests group strings from the same translation in file order, using the service’s automatic translation batch size (currently 20 strings for built-in LLM services). All plural forms of a string stay together. Related strings share context, allowing the evaluator to check meaning and terminology across the batch. Batching reduces the number of provider requests for scheduled, manual, and change-triggered runs; it does not skip unchanged strings.

Evaluation frequency defaults to weekly. Daily and monthly schedules are also available; disabled turns off scheduled evaluation. Background processing must be enabled. A successful full run starts the next interval. Manual runs bypass the interval. Enable Evaluate translation changes or Evaluate repository updates to additionally evaluate after those events. Installation does not immediately contact the provider. Each run can incur provider costs, including reevaluation of unchanged translations.

Evaluation runs in background tasks, with results and failure counts recorded in the existing add-on activity log. Failed requests retain existing valid findings and are tried again only by a subsequent run. Evaluation shares the service’s automatic translation cooldown: rate-limit responses activate it, and batches are skipped while it is active. More specific installations take precedence: component, nearest category, project, then site-wide.

Findings appear as standard checks for accuracy, fluency, terminology, style, and formatting. Each finding includes a minor, major, or critical severity and an explanation. Multiple findings in one category share a check, so ignoring that check ignores the whole category for the string. Existing search filters and API search work, for example check:ai_accuracy. Translation flags such as ignore-ai-accuracy disable a category; ignore-all-checks disables all checks.

Changing the source or translation removes outdated findings. Results received after any source or translation in their batch changes are discarded for the whole batch. A failed or malformed response also leaves existing findings for the whole batch unchanged; other batches can still complete. Incomplete runs do not advance the scheduled evaluation date. Reevaluation of unchanged content preserves ignored categories, and a successful evaluation removes categories that no longer have findings. Removing or reconfiguring the add-on clears its findings. Evaluator metadata is internal and cannot be edited through the API; the add-on configuration uses the existing Suplimente permissions and validation.

Automation

Added in version 2026.10.

ID add-on:

weblate.automation.automation

Configurație:

workflow

Flux de lucru

Enter an automation definition as YAML or JSON.

Declanșări:

Component update, Daily, Event change, Manual trigger, Repository post-commit, Repository post-push, Repository post-update

Runs ordered translation operations with conditions and branches.

Install this add-on on a component, category, project, or site. Inherited instances run separately for each component. Multiple instances can be installed. Configuring, previewing, and running an automation requires the usual add-on management permission. Saving its configuration does not execute it.

Enter YAML or JSON in Workflow. Use Preview without changes to validate it and inspect planned actions, then Run now for real execution. Results appear in the add-on activity log.

Vezi și

• Workflow definition for the script definition and reference.

• Cookbook for complete examples.

• Apply translation memory before machine translation for translation memory before machine translation.

Traducere automată

ID add-on:

weblate.autotranslate.autotranslate

Configurație:

mode	Mod traducere automată	Alegerile disponibile: suggest Adaugă ca sugestie translate Adaugă ca traducere fuzzy Adaugă ca „Necesită editare” approved Adaugă ca traducere aprobată
q	Înterogare	Te rugăm să reții că traducerea tuturor șirurilor va elimina toate traducerile existente.
auto_source	Sursa traducerilor automate	Alegerile disponibile: others Alte componente de traducere mt Traducere automată
component	Componentă	Enter a source component ID. With 30 or more eligible source components, a project/component path is also accepted. In that case, component and project operations also accept a component slug from the target project. Leave blank to use eligible components from each target component’s project.
engines	Translation services	Translation services
threshold	Prag de punctaj

Declanșări:

Add-on installation, Component update, Daily, Event change

Tradu automat șirurile cu ajutorul traducerii automate sau al altor componente.

To control translation order, use the Automation add-on with a separate action for each pass. Follow the Apply translation memory before machine translation cookbook example to apply local translation memory first and send only the remaining strings to a machine translation service. Selecting multiple engines here uses Priority of machine translation and translation memory services; installation order of separate add-ons does not define an execution sequence.

Vezi și

• Traducere automată

• Păstrarea traducerilor la fel în toate componentele

• Priority of machine translation and translation memory services

• Searching for strings

CDN de localizare JavaScript

Added in version 4.2.

ID add-on:

weblate.cdn.cdnjs

Configurație:

threshold	Prag de traducere	The percentage of translated strings that must be present for translation to be included.
css_selector	Selector CSS	Selector CSS pentru detectarea elementelor traductibile.
cookie_name	Nume cookie de limbă	Nume cookie care stochează preferințe lingvistice.
files	Extrage șiruri din fișiere HTML	Listă de nume de fișiere din depozitarul curent sau de adrese URL la distanță care trebuie interpretate pentru șiruri traductibile.

Declanșări:

Add-on installation, Daily, Repository post-commit, Repository post-remove, Repository post-update

Publică traducerile în rețeaua de livrare de conținut pentru a fi utilizate în localizarea JavaScript sau HTML.

Poate fi utilizat pentru a localiza pagini HTML statice sau pentru a încărca localizarea în codul JavaScript.

Generates a unique URL for your component you can include in HTML pages to localize them. See Traducerea HTML și JavaScript folosind Weblate CDN for more details. Available languages and translation files are listed in the CDN manifest.

Notă

This add-on requires additional configuration on the Weblate server. LOCALIZE_CDN_PATH configures where generated files will be written (on a filesystem), and LOCALIZE_CDN_URL defines where they will be served (URL). Serving of the files is not done by Weblate and has to be set up externally (typically using a CDN service).

This add-on is configured on Hosted Weblate and serves the files via https://weblate-cdn.com/.

Vezi și

• Configurarea add-onului Weblate CDN

• Traducerea HTML și JavaScript folosind Weblate CDN

• Localizare CDN

• Extragerea șirurilor pentru Weblate CDN

• Localizarea HTML folosind Weblate CDN

Translation files CDN

Added in version 2026.5.

ID add-on:

weblate.cdn.files

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Add-on installation, Component update, Repository post-commit, Repository post-remove, Repository post-update

Publishes translation files into a content delivery network.

Publishes translation files without converting them to another format. Files are written below the add-on specific CDN directory and served from LOCALIZE_CDN_URL/<add-on UUID>/. Single-file translations use the language code and original file extension, for example cs.json or de.po. Multi-file translations are served below the language code using paths relative to the translation directory. Monolingual components include the source language file, while bilingual components publish only target-language files. See Localizare CDN for secure serving guidance. Available languages and translation files are listed in the CDN manifest.

Kotlin SDK CDN

Added in version 2026.10.

ID add-on:

weblate.cdn.kotlin

Configurație:

maximum_age	Maximum build age (days)	Retires builds this many days after their first registration. Re-registering a build does not extend its age.
maximum_versions	Maximum retained versions	Limits retained builds across all package names. A build is retired when either this limit or the maximum age is reached.

Declanșări:

Add-on installation, Component update, Daily, Repository post-commit, Repository post-remove, Repository post-update

Publishes Android string and plural resources for registered Kotlin SDK builds.

Atenționare

The Kotlin SDK is available as an alpha release. No compatibility is guaranteed until the final Kotlin SDK is released. Endpoints, build metadata, CDN manifests, and generated resource formats may change without backward compatibility.

Install Kotlin SDK CDN on an Android string-resource component to publish translations for builds registered by the Kotlin SDK. Configure LOCALIZE_CDN_URL and LOCALIZE_CDN_PATH first. CDN output is public, including translations from private components. Manifests expose the application package name and version code. ARSC files expose published resource names and their submitted IDs alongside translated text. Do not treat the uploaded resource mapping as confidential; enable publication only when this disclosure is intended. Registration and status API access remains permission-controlled.

Installation offers to install Translation files CDN by default so the SDK can also consume the original Android XML files. Existing Translation files CDN installations are reused. For existing Kotlin SDK installations, use Install Translation files CDN on the configuration page, then return to copy the updated Gradle configuration. Original files are also published publicly, including those from private components.

Copy the Gradle plugin configuration from the add-on configuration page. It includes the Weblate server URL, separate translationFiles and kotlinSdk public CDN URLs, project slug, and component path (with any category path URL-encoded). Replace the placeholder with a project-scoped API token whose permissions allow editing the component. Project administrators can create one in the project’s API access tab; see Per-project access tokens. Keep that token in the build environment, not in the application. The add-on’s API tab shows the API base URL; submit build metadata to its builds/ endpoint. See Kotlin SDK builds for the request and response format.

For Gradle plugin and library setup, see Kotlin SDK for Android.

The add-on matches resource names and types from registered builds to current component translations. Strings, plurals, and Android styled text are supported. String arrays and resource references are not generated. Untranslated entries, read-only entries, and incomplete plural resources are omitted; applications retain their bundled values. Unsupported styling fails publication; the previous successful publication remains available.

Resource IDs must describe the final installed build. Uploading an identical mapping again is harmless; a different mapping for the same package and version is rejected. Old builds receive current translations by name, including after source text or formatting arguments change. Maintainers are responsible for compatibility with older application code.

Lifecycle settings

• Maximum build age (days) defaults to 365 and accepts 1 through 730, measured from the first registration. Repeated uploads do not extend it.

• Maximum retained versions defaults to 20 and accepts 1 through 100, counted across all package names. One additional unpublished replacement is allowed. New registrations can retire older unpublished replacements. Published builds are retired for this limit only after a replacement is published. Failed replacements preserve existing publications; maximum-age expiry still applies independently.

Either limit retires a build and immediately clears its metadata. Lightweight retired records are deleted on cleanup after 24 hours and successful manifest removal; their package/version identifiers can then be registered again. Failed or interrupted manifest removals are retried hourly. Until removal succeeds, the registration and its referenced artifacts are retained, and the files may remain publicly accessible. Resource mappings are immutable only while their registration records remain.

Each add-on permits at most 1000 registration records, including retired records. New registrations exceeding this limit return HTTP 409 until cleanup frees capacity; identical retries remain accepted. Metadata is bounded by the 5 MiB upload limit and maximum retained version count plus one replacement, without a separate byte quota. Limits are enforced during registration and scheduled cleanup.

Superseded artifacts are deleted on cleanup after a fixed 24-hour window. All artifact files, including superseded files and incomplete publication output, count towards hard limits of 5 GiB and 10000 files per add-on. The larger artifact allowance accommodates translated text and multiple locales; it does not guarantee capacity for every locale or build combination. Shared artifacts count only once. Publications exceeding either limit fail before writing new artifacts and preserve the previous manifest. Neither the window nor these limits are configurable. Limit manifest caching as described below.

Compilation stages one locale at a time on disk. A per-locale conservative encoded text and styling estimate exceeding 64 MiB fails publication.

Preparation additionally requires up to 5 GiB of temporary disk space per publication job, separate from the published artifact allowance. Temporary files contain staged ARSC output, shared by versions with identical resource mappings. They are stored below LOCALIZE_CDN_PATH. Configure the server to deny access to .kotlin-sdk-staging as described in Localizare CDN before enabling this add-on.

Manifest replacement follows the database commit. Failed or interrupted writes are retried by subsequent publication jobs, with artifacts for both the old and pending manifest protected until replacement succeeds.

Uninstalling the add-on attempts to remove its published files from the CDN origin immediately. Failed or interrupted removals are retried hourly; files may remain publicly accessible until cleanup succeeds. Removal does not revoke copies already cached or downloaded by clients.

Publication and cleanup run asynchronously after build registration, component updates, translation commits and removals, and during daily add-on processing. Failures appear in the add-on activity log and registration status. Previous successful publications remain available when replacement generation fails. If the component stops using the Android resource format, hourly maintenance retires its publications. The normal artifact retention window still applies.

CDN client contract

Each build has a stable manifest at <CDN base>/<packageName>/<versionCode>/manifest.json. The version 1 manifest contains schemaVersion, packageName, versionCode, and locales. Locale keys are Weblate language codes. Each locale contains a relative url, sha256, and byte size for its ARSC artifact. Resolve relative URLs against the manifest URL. Artifact contents do not change after publication. The manifest has a JSON Schema.

Configure the CDN origin to cache manifests for at most one hour (for example, Cache-Control: public, max-age=3600), and artifact files with Cache-Control: public, max-age=31536000, immutable. Artifact files may use application/octet-stream. Configure these headers on the CDN server. Translation updates and retirements can take up to one hour to reach clients. Use Cache-Control: no-cache when immediate revalidation is preferred. The fixed 24-hour artifact retention window exceeds the manifest cache lifetime.

The Kotlin SDK should validate artifact length and hash, cache successful downloads locally, and load them with Android’s resources-loader API on API 30 or newer. A missing manifest, missing locale, or download failure must preserve bundled resources. Retired manifests return 404 at the origin; cached copies can remain usable until they expire. Hashes detect corrupted or mismatched content; authentication relies on HTTPS and the configured CDN.

Elimină șiruri goale

Added in version 4.4.

ID add-on:

weblate.cleanup.blank

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Add-on installation, Repository post-commit, Repository post-update

Elimină șirurile fără traducere din fișierele de traducere.

Utilizați această opțiune pentru a nu avea șiruri goale în fișierele de traducere (de exemplu, dacă biblioteca de localizare le afișează ca fiind lipsă în loc să revină la șirul sursă).

Vezi și

Weblate actualizează fișierele de traducere în afară de traduceri?

Curăță fișierele de traducere

ID add-on:

weblate.cleanup.generic

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Add-on installation, Repository post-update, Repository pre-commit

Actualizează toate fișierele de traducere pentru a se potrivi cu fișierul de bază monolingv. Pentru majoritatea formatelor de fișiere, aceasta înseamnă eliminarea cheilor de traducere învechite care nu mai sunt prezente în fișierul de bază.

For formats containing additional content besides translation strings (such as Fișiere HTML, Fișiere Windows RC, or Formatul OpenDocument) this also brings the translation file in sync with the base file.

For a one-time cleanup of a single translation file, use Cleanup unused in Întreținere depozitar on that translation instead of installing the add-on.

Vezi și

Weblate actualizează fișierele de traducere în afară de traduceri?

Adaugă limbi lipsă

ID add-on:

weblate.consistency.languages

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Add-on installation, Daily, Repository post-add

Asigură utilizarea unui set coerent de limbi pentru toate componentele unui proiect.

Notă

The components shared from other projects are not considered in this.

Limbile lipsă sunt verificate o dată la 24 de ore și atunci când sunt adăugate noi limbi în Weblate.

Spre deosebire de majoritatea celorlalte, acest add-on afectează întregul proiect.

Sugestie

Traduceți automat șirurile nou adăugate cu Traducere automată.

Descoperire componente

ID add-on:

weblate.discovery.discovery

Configurație:

File matching
match	Expresie regulată pentru a potrivi fișierele de traducere	The regular expression must define a named group for component. Also define a named group for language when matching translation files. When the file mask is set, omit language and match the monolingual base or new base file instead.
file_format	Format fișier	Format fișier
language_regex	Filtru limbă	Expresie regulată pentru filtrarea fișierelor de traducere la scanarea pentru masca de fișiere.
Component naming and file templates
name_template	Personalizează numele componentei	Use Django template syntax. This template must include {{ component }}.
base_file_template	Definește numele fișierului de bază monolingv	Leave empty for bilingual translation files. When set, this template must include {{ component }}.
new_base_template	Definește fișierul de bază pentru traduceri noi	Filename of file used for creating new translations. For gettext choose .pot file. This template must include {{ component }}.
intermediate_template	Fișier de limbă intermediar	Filename of intermediate translation file. In most cases this is a translation file provided by developers and is used when creating actual source strings. This template must include {{ component }}.
filemask_template	Define the file mask	Leave empty to match translation files directly. When set, discovery matches the monolingual base or new base file and uses this template as the file mask. Include a language wildcard and {{ component }}, for example locale//{{ component }}.po or docs/{{ component }}_.md.
Component lifecycle
copy_addons	Clonare suplimente din componenta principală în cele nou create
remove	Elimină componente pentru fișiere inexistente

Declanșări:

Add-on installation, Repository post-update

Adaugă sau elimină automat componente ale proiectului pe baza modificărilor de fișiere din sistemul de control al versiunilor.

The matching is done using regular expressions enabling complex configuration, but some knowledge is required to do so. Usually the regular expression to match translation files has to contain two named groups to match component and language. When creating components from a monolingual base or new base file, omit the language group and match that source file instead. All named groups in the regular expression can be used as variables in the template fields.

Discovery requirements

To discover a component successfully, the configuration has to do all of the following:

• The regular expression must define a component named group. Matching translation files also requires a language named group.

• Template fields used to name or locate per-component files must include {{ component }}, so the rendered value actually changes for each discovered component.

• For monolingual formats, the component must contain a file matching base_file_template and at least one translation file matching match, unless you set the file mask (see below).

Discovering components without translation files

Set Define the file mask to discover components from a monolingual base or new base file alone, even when no translation files exist yet. In that mode:

• Configure Regular expression to match translation files against to match the monolingual base or new base file, and omit the language group. Keep full control over the component capture, for example locale/(?P<component>[^/]+)\.pot or docs/(?P<component>[^/_]+)\.md.

• Fill Define the file mask with a path that includes both a language wildcard and {{ component }}, for example locale/*/{{ component }}.po or docs/{{ component }}_*.md.

• Keep using the other filename templates with any named groups from the match expression.

Worked example: news_<lang>.md

This is a common filename-based language variant layout:

• docs/news_en.md

• docs/news_cs.md

• docs/guide_en.md

Use the Filename-based language variants preset for a starting point, then choose the matching file format and review the populated values.

Regular expression:

(?:(?P<path>.*/))?(?P<component>.+?)_(?P<language>[A-Za-z]{2,3}(?:[_-][A-Za-z0-9]+)*)\.(?P<extension>[^/.]+)

Component name:

{{ component }}

Discovered file masks:

• docs/news_*.md

• docs/guide_*.md

In this example, {{ component }} resolves to the basename before the language suffix, so docs/news_en.md, docs/news_pt_BR.md, and docs/news_pt-BR.md all become the news component.

You can use Django template markup in all filename fields, for example:

{{ component }}

Component name parsed from the component match group

{{ component|title }}

Nume de fișier al componentei cu prima literă majusculă

{{ path }}: {{ component }}

Custom match group from the regular expression

După ce apăsați pe Save, va fi prezentată o previzualizare a componentelor corespunzătoare, de unde puteți verifica dacă configurația se potrivește cu nevoile dumneavoastră:

Component discovery examples

The worked example above covers the most common filename-based variant layout. The following examples show other repository structures you can match.

One folder per language

Un dosar pentru fiecare limbă care conține fișiere de traducere pentru componente.

Regular expression:

(?P<language>[^/.]*)/(?P<component>[^/]*)\.po

Matching files:

• cs/application.po

• cs/website.po

• de/application.po

• de/website.po

Gettext locales layout

Structura obișnuită pentru stocarea fișierelor gettext PO.

Regular expression:

locale/(?P<language>[^/.]*)/LC_MESSAGES/(?P<component>[^/]*)\.po

Matching files:

• locale/cs/LC_MESSAGES/application.po

• locale/cs/LC_MESSAGES/website.po

• locale/de/LC_MESSAGES/application.po

• locale/de/LC_MESSAGES/website.po

Complex filenames

Utilizarea atât a componentei, cât și a denumirii limbii în numele fișierului.

Regular expression:

src/locale/(?P<component>[^/]*)\.(?P<language>[^/.]*)\.po

Matching files:

• src/locale/application.cs.po

• src/locale/website.cs.po

• src/locale/application.de.po

• src/locale/website.de.po

Repeated language code

Utilizarea limbii atât în calea de acces, cât și în numele fișierului.

Regular expression:

locale/(?P<language>[^/.]*)/(?P<component>[^/]*)/(?P=language)\.po

Matching files:

• locale/cs/application/cs.po

• locale/cs/website/cs.po

• locale/de/application/de.po

• locale/de/website/de.po

Split Android strings

Șiruri de resurse Android, împărțite în mai multe fișiere.

Regular expression:

res/values-(?P<language>[^/.]*)/strings-(?P<component>[^/]*)\.xml

Matching files:

• res/values-cs/strings-about.xml

• res/values-cs/strings-help.xml

• res/values-de/strings-about.xml

• res/values-de/strings-help.xml

Matching multiple paths

Multi-module Maven project with Java properties translations.

Regular expression:

(?P<originalHierarchy>.+/)(?P<component>[^/]*)/src/main/resources/ApplicationResources_(?P<language>[^/.]*)\.properties

Component name:

{{ originalHierarchy }}: {{ component }}

Matching files:

• parent/module1/submodule/src/main/resources/ApplicationResources_fr.properties

• parent/module1/submodule/src/main/resources/ApplicationResource_es.properties

• parent/module2/src/main/resources/ApplicationResource_de.properties

• parent/module2/src/main/resources/ApplicationResource_ro.properties

Sugestie

Component discovery add-on uses URL-uri interne Weblate. It’s a convenient way to share VCS setup between multiple components. Linked components use the local repository of the main component set up by filling weblate://project/main-component into the Depozitar cod sursă field (in Operations ↓ Settings ↓ Version control system) of each respective component. This saves time with configuration and system resources too.

Sugestie

Ensure the new component contains the full set of translatable languages with Adaugă limbi lipsă.

Vezi și

• Marcarea șablonului

• import_project

Fedora Messaging

Added in version 5.15.

ID add-on:

weblate.fedora_messaging.publish

Configurație:

Broker connection
amqp_url	AMQP broker URL	The AMQP broker URL to connect to.
topic_prefix	Topic prefix	Optional prefix to prepend to generated message topics.
Timeouts and retries
publish_timeout	Publish timeout	How many seconds to wait for the broker delivery acknowledgement.
connection_attempts	Connection attempts	How many times to try connecting to the broker.
retry_delay	Retry delay	How many seconds to wait between connection attempts.
TLS credentials
ca_cert	CA certificate bundle (PEM)	Paste only PEM certificate blocks, each starting with „—–BEGIN CERTIFICATE—–” and ending with „—–END CERTIFICATE—–„.
client_key	Client private key (PEM)	Paste a single unencrypted PEM private key block. Encrypted private keys are not supported.
client_cert	Client certificate (PEM)	Paste only the PEM certificate block starting with „—–BEGIN CERTIFICATE—–”; do not paste the output from „openssl x509 -text”.
Event selection
event_filter	Change events to trigger	Choose which change events should trigger this add-on. Change events to trigger
events	Selected change events	Selected change events

Declanșări:

Event change

Sends notifications to a Fedora Messaging compatible AMQP exchange.

Fedora Messaging este un editor bazat pe AMQP pentru toate modificările care se produc în Weblate. Puteți agăța servicii suplimentare pe modificările care se produc în Weblate folosind acest lucru.

Configure the broker with a plain amqp:// or amqps:// URL, including its virtual host. URL query strings and fragments are not supported. Use the add-on’s connection attempts, retry delay, and publish timeout fields instead. The publish timeout covers connection attempts, retry delays, and broker confirmation. Publishing resolves DNS when opening a connection and reuses the existing connection without further DNS lookups. Resolved addresses and the connected peer are checked against the configured private-network restrictions. Synchronous DNS resolution cannot be interrupted by the publish timeout and can exceed it when the system resolver is slow or unavailable. Rejected messages are not retried.

Weblate reuses a publisher connection in each worker process, with AMQP heartbeats disabled. Failed connections are discarded and recreated on the next attempt. A lost broker confirmation can cause duplicate delivery; consumers can identify retries by their unchanged message ID.

Message topic

All messages have topic weblate.<action>.<project>.<category...>.<component>.<translation>. When configured, topic_prefix is prepended to this topic using a single dot separator, for example org.fedoraproject.weblate.project_backed_up.website. The action is lowercase textual representation of action with underscores instead of space, for example resource_updated; see Selected change events for all action identifiers. The remaining parts match Weblate object path segments.

For example, a project backup event for the website project uses weblate.project_backed_up.website. A translation change in the website project, frontend component, and Czech translation uses weblate.translation_changed.website.frontend.cs. The same change in the frontend component inside the parent and child categories uses weblate.translation_changed.website.parent.child.frontend.cs.

Message body

The body consists of following fields (given that they are available for the event):

change_id

Numerical ID of change

action

Verbose name of the change.

timestamp

ISO formatted timestamp

target

New value of the change (eg. new translation of the string)

old

Old value of the change (eg. previous translation of the string)

source

Source string.

url

Absolute URL to view the related object.

author

Author username (this can be different from user for example when accepting suggestions)

user

Acting username

project

Limbajul proiectului

component

Componenta slug

translation

Codul limbii de traducere

Message headers

There are additional headers which you might utilize for routing as well:

action

Verbose name of the change.

project

Limbajul proiectului

component

Componenta slug

Example messages

Repository merge event:

{
  "id": 1,
  "action": "Merged repository",
  "timestamp": "2017-06-15T11:30:47.325000+00:00",
  "url": "http://example.com/projects/test/test/",
  "component": "test"
}

New source string event:

{
  "id": 2,
  "action": "New source string",
  "timestamp": "2017-06-15T11:30:47.372000+00:00",
  "url": "http://example.com/translate/test/test/cs/?checksum=6412684aaf018e8e",
  "component": "test",
  "translation": "cs",
  "source": ["Hello, world!\n"]
}

Resource update event:

{
  "id": 6,
  "action": "Resource update",
  "timestamp": "2017-06-15T11:30:47.410000+00:00",
  "url": "http://example.com/projects/test/test/cs/",
  "project": "test",
  "component": "test",
  "translation": "cs"
}
{
  "id": 7,
  "action": "Resource update",
  "timestamp": "2017-06-15T11:30:47.510000+00:00",
  "url": "http://example.com/projects/test/test/de/",
  "project": "test",
  "component": "test",
  "translation": "de"
}
{
  "id": 8,
  "action": "Resource update",
  "timestamp": "2017-06-15T11:30:47.595000+00:00",
  "url": "http://example.com/projects/test/test/it/",
  "project": "test",
  "component": "test",
  "translation": "it"
}

Project removal event:

{
  "id": 9,
  "action": "Removed project",
  "timestamp": "2019-10-17T15:57:08.559420+00:00",
  "target": "test",
  "user": "testuser"
}

New contributor event:

{
  "id": 11,
  "action": "New contributor",
  "timestamp": "2019-10-17T15:57:08.759960+00:00",
  "url": "http://example.com/translate/test/test/cs/?checksum=6412684aaf018e8e",
  "author": "testuser",
  "user": "testuser",
  "project": "test",
  "component": "test",
  "translation": "cs",
  "source": ["Hello, world!\n"]
}

New translation event:

{
  "id": 12,
  "action": "New translation",
  "timestamp": "2019-10-17T15:57:08.772591+00:00",
  "url": "http://example.com/translate/test/test/cs/?checksum=6412684aaf018e8e",
  "target": ["Ahoj svete!\n"],
  "author": "testuser",
  "user": "testuser",
  "project": "test",
  "component": "test",
  "translation": "cs",
  "source": ["Hello, world!\n"]
}

Vezi și

• Configuring Fedora Messaging

• Weblate Messaging

Editare în masă

ID add-on:

weblate.flags.bulk

Configurație:

q	Înterogare
search_type	Search type	Alegerile disponibile: text Text regex Expresie regulată
search	Șir de căutare	Case-sensitive text or regular expression to replace in matching strings. Leave empty to disable replacement.
replacement	Șir de înlocuire	Leave empty to remove matching text. In regular expression mode, use 1 for the first captured group. Named group references are also supported.
state	Stare de setat	Alegerile disponibile: -1 Nu modifica 0 Gol 10 Necesită editare 11 Needs editing (Needs rewriting) 12 Needs editing (Needs checking) 20 Tradus 30 Aprobat
Source flags Flags are set on the source strings corresponding to your filter results and apply to their translations in every language.
add_flags	Add flags
remove_flags	Remove flags
Translation flags Flags apply only to translations matching your filter. Source strings are excluded.
add_translation_flags	Add flags
remove_translation_flags	Remove flags	Only flags set directly on these translations are removed. Inherited flags remain in effect.
Labels Labels apply to the source strings corresponding to your filter results and are shared across all languages.
add_labels	Add labels
remove_labels	Remove labels

Declanșări:

Add-on installation, Component update

Bulk edit text, flags, labels, or states of strings.

Uses the operations described in Editare în masă, including literal or regular expression replacement and clearing translations. Runs process all eligible matching strings without interactive preview. See Bulk editing for replacement syntax and string state values.

Exemple:

Etichetarea automată a șirurilor noi

Interogare de căutare	NOT has:label
Labels: Add labels	recent

Marcarea tuturor șirurilor de modificare Fișiere de metadate magazin de aplicații changelog numai pentru citire

Interogare de căutare	language:en AND key:changelogs/
Translation flags: Add flags	read-only

Marking certain strings read-only

Interogare de căutare	source:r"^\`\`[.a-zA-Z0-9_-]*\`\`$" AND language:en
Translation flags: Add flags	read-only

Vezi și

• Editare în masă

• Personalizarea comportamentului cu ajutorul stegulețelor

• Șir de etichete

Flag unchanged translations as „Needs rewriting”

ID add-on:

weblate.flags.same_edit

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Unit pre-create

Whenever a new translatable string is imported from the VCS and it matches a source string, it is flagged as needing rewriting in Weblate. Especially useful for file formats that include source strings for untranslated strings.

Sugestie

De asemenea, este posibil să doriți să întăriți verificarea Traducere neschimbată prin adăugarea indicatorului strict-same la Indicarori traducere.

Vezi și

Statele de traducere

Flag new source strings as „Needs checking”

ID add-on:

weblate.flags.source_edit

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Unit pre-create

Whenever a new source string is imported from the VCS, it is flagged as needing checking in Weblate. This way you can easily filter and edit source strings written by the developers.

Vezi și

Statele de traducere

Flag new translations as „Needs rewriting”

ID add-on:

weblate.flags.target_edit

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Unit pre-create

Whenever a new translatable string is imported from the VCS, it is flagged as needing rewriting in Weblate. This way you can easily filter and edit translations created by the developers.

Vezi și

Statele de traducere

Flag updated translations from repository as „Needs rewriting”

ID add-on:

weblate.flags.target_repo_update

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Unit post-sync

Whenever a string translation is changed from the VCS, it is flagged as needing rewriting in Weblate. Especially useful if translation files are often updated manually or by an external service.

Vezi și

Statele de traducere

Completare șiruri doar pentru citire cu sursa

Added in version 4.18.

ID add-on:

weblate.generate.fill_read_only

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Add-on installation, Component update, Daily

Completează șirurile de traducere doar pentru citire cu șirul sursă.

Generator de statistici

ID add-on:

weblate.generate.generate

Configurație:

scope	Output scope	Alegerile disponibile: translation One file per translation component One file per component
filename	Nume fișier generat
template	Conținut fișier generat

Declanșări:

Add-on installation, Component update, Repository post-add, Repository post-remove, Repository pre-commit

Generează un fișier care conține informații detaliate despre starea traducerii.

Puteți utiliza un șablon Django atât în numele fișierului, cât și în conținut; consultați Marcarea șablonului pentru o descriere detaliată a marcajului.

De exemplu, generarea unui fișier de sinteză pentru fiecare traducere:

Nume fișier generat

locale/{{ language_code }}.json

Conținut

{
   "language": "{{ language_code }}",
   "strings": "{{ stats.all }}",
   "translated": "{{ stats.translated }}",
   "last_changed": "{{ stats.last_changed }}",
   "last_author": "{{ stats.last_author }}",
}

Component-wide output

Set Output scope to One file per component to maintain one locale list or statistics file for the entire component. The default, One file per translation, preserves existing configurations.

Component output is generated on installation and configuration changes. It is updated when translations are committed, languages are added or removed, and component files are reloaded. Language metadata changes are included on the next such update or when the add-on is reconfigured. Unchanged output does not create a new commit.

Both modes support component and project variables in filenames and content. In component mode, the content additionally receives translations, ordered by repository language code. Each item provides:

• language_code: the language code used in the repository.

• language_name: the English language name.

• language_native_name: the name translated into its own language using Weblate’s catalogs, with an English fallback when unavailable.

• language_direction: ltr or rtl.

• filename and url: the translation filename and Weblate URL.

• is_source: whether this is the component’s source translation.

• stats: the same statistics available in translation mode.

The source translation is included. Templates can exclude it using {% if not item.is_source %}. Statistics use Weblate’s completion semantics. Custom language names are retained; there is no external locale-data lookup.

For example, generate locales.json for a website:

[
{% for item in translations %}
  {
    "code": {{ item.language_code|json }},
    "file": {{ item.filename|json }},
    "name": {{ item.language_native_name|json }},
    "dir": {{ item.language_direction|json }}
  }{% if not forloop.last %},{% endif %}
{% endfor %}
]

Or generate languages.py for an application:

names = {
{% for item in translations %}
    {{ item.language_code|python }}: {{ item.language_native_name|python }},
{% endfor %}
}
completeness = {
{% for item in translations %}
    {{ item.language_code|python }}: {{ item.stats.translated_percent|python }},
{% endfor %}
}

The json and python filters serialize complete values, including string quotes and escaping. Do not add quotes around their output. They also support lists and dictionaries; {{ translations|json }} exports all available data. Dates and times are serialized as ISO-formatted strings.

Vezi și

Marcarea șablonului

Precompletare traducere cu sursa

Added in version 4.11.

ID add-on:

weblate.generate.prefill

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Add-on installation, Component update, Daily

Completează șirurile de traducere cu șirul sursă.

All untranslated strings in the component will be filled with the source string, and marked as needing edit. Use this when you can not have empty strings in the translation files. .. AUTOGENERATED START: weblate.generate.pseudolocale .. This section is automatically generated by ./manage.py list_addons. Do not edit manually.

Generare pseudolocale

Added in version 4.5.

ID add-on:

weblate.generate.pseudolocale

Configurație:

Source and target
source	Șiruri sursă
include_readonly	Include șiruri doar pentru citire
target	Traducere țintă	Toate șirurile din această traducere vor fi suprascrise
Prepended text
prefix	Prepended static text
var_prefix	Prepended variable text
Appended text
suffix	Appended static text
var_suffix	Appended variable text
Text expansion
var_multiplier	Variable text multiplier	How many times to repeat the variable text depending on the length of the source string.

Declanșări:

Add-on installation, Component update, Daily

Generează o traducere prin adăugarea automată a prefixului și sufixului la șirurile sursă.

Pseudolocalele sunt utile pentru a găsi șiruri de caractere care nu sunt pregătite pentru localizare. Acest lucru se realizează prin modificarea tuturor șirurilor sursă traductibile pentru a facilita identificarea șirurilor nealterate la rularea aplicației în limba pseudolocală.

De asemenea, este posibil să se găsească șiruri de caractere ale căror omologi localizați ar putea să nu se potrivească cu aspectul.

Using the variable parts makes it possible to look for strings which might not fit into the user interface after the localization - it extends the text based on the source string length. The variable texts are repeated by length of the text multiplied by the multiplier. For example Hello world with variable text _ and variable multiplier of 1 becomes Hello world___________ - the text is repeated once for each character in the source string.

Șirurile vor fi generate folosind următorul model:

Prepended static text Prepended variable text Source string Appended variable text Appended static text

Sugestie

Puteți folosi limbi reale pentru testare, dar există pseudolocale dedicate disponibile în Weblate - en_XA și ar_XB.

Sugestie

Puteți utiliza acest add-on pentru a începe traducerea într-o nouă locație a unei limbi existente sau a unei limbi similare. După ce adăugați traducerea la componentă, urmați la add-on. Exemplu: Dacă aveți fr și doriți să începeți traducerea fr_CA, setați pur și simplu fr ca sursă, fr_CA ca țintă și lăsați prefixul și sufixul goale.

Dezinstalați add-on-ul după ce ați completat noua traducere pentru a împiedica Weblate să modifice traducerile făcute după copiere.

Actualizarea variabilei ALL_LINGUAS în fișierul „configure”

ID add-on:

weblate.gettext.configure

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Add-on installation, Daily, Repository post-add, Repository post-remove

Updates the ALL_LINGUAS variable in „configure”, „configure.in” or „configure.ac” files, when a translation is added or removed.

Updates the ALL_LINGUAS variable in configure, configure.in or any configure.ac files, when a translation is added or removed.

Personalizare ieșire gettext

Removed in version 5.13: Replaced by File format parameters.

Update gettext template (Django)

Added in version 5.17.

ID add-on:

weblate.gettext.django

Configurație:

interval	Update frequency	How often the add-on should update the POT file when the component is refreshed. Alegerile disponibile: daily Daily weekly Weekly monthly Lunar
normalize_header	Normalize POT header	Updates gettext headers and replaces placeholder POT comments.
location_mode	Source locations	Choose how extraction writes source locations to the POT file. Use this to keep locations in the template while omitting them from translated PO files. Alegerile disponibile: file Use file format settings keep Extract locations to the POT file omit Do not extract locations

Declanșări:

Add-on installation, Manual trigger, Repository post-update

Updates the gettext template using Django’s built-in makemessages command.

This add-on updates the template configured in Șablon pentru traduceri noi. It is available for gettext PO components, and the component must define a template for new translations.

The selected update frequency applies to automatic runs after repository refreshes. Installing or reconfiguring the add-on runs it immediately, and manual runs from add-on management or the API also bypass the frequency schedule. After a successful update, Weblate commits the changed template and reloads source strings.

The template update does not update translation PO files by itself. Keep Actualizare fișiere PO pentru a se potrivi cu POT (msgmerge) installed when translation files should follow template changes automatically. The install form for this add-on can install that add-on, but existing add-on settings do not show that installation option again.

Django requirements

This add-on requires xgettext and msguniq. It runs Weblate’s internal extraction wrapper for Django messages instead of invoking a project’s manage.py makemessages, so it does not load project Django settings or applications.

The template for new translations must use the django or djangojs domain. Supported template names are django.pot, djangojs.pot, django.po, and djangojs.po. Weblate infers the source directory from the template path and skips repository locale directories while extracting.

Actualizare fișier LINGUAS

ID add-on:

weblate.gettext.linguas

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Add-on installation, Daily, Repository post-add, Repository post-remove

Updates the LINGUAS file when a translation is added or removed.

Update POT file (Meson)

Added in version 5.17.

ID add-on:

weblate.gettext.meson

Configurație:

Update behavior
interval	Update frequency	How often the add-on should update the POT file when the component is refreshed. Alegerile disponibile: daily Daily weekly Weekly monthly Lunar
normalize_header	Normalize POT header	Updates gettext headers and replaces placeholder POT comments.
location_mode	Source locations	Choose how extraction writes source locations to the POT file. Use this to keep locations in the template while omitting them from translated PO files. Alegerile disponibile: file Use file format settings keep Extract locations to the POT file omit Do not extract locations
Meson preset
preset	Meson preset	Built-in xgettext argument preset matching Meson gettext integration. The GLib preset adds the keyword and format-flag options used by Meson’s gettext helper. Alegerile disponibile: glib GLib
Comment extraction
comment_mode	Code comments	Choose whether xgettext should extract no comments, all comments, or only comments marked with a specific tag. Alegerile disponibile: off Do not extract comments all Extract all comments tagged Extract comments with tag
comment_tag	Comment tag	Tag passed to xgettext for comment extraction when using tagged comment mode.
Keywords
keyword	Additional keywords	Newline-separated extra keywords passed to xgettext using –keyword.
keyword_exclusive	Use keywords exclusively	When enabled, passes --keyword without a value to xgettext before the additional keyword, disabling all default keywords so that only the keyword specified above is recognized.
Checks and ITS data
checks	xgettext checks	Additional xgettext validation checks to enable for extracted messages. Alegerile disponibile: ellipsis-unicode ellipsis-unicode space-ellipsis space-ellipsis quote-unicode quote-unicode bullet-unicode bullet-unicode
data_dirs	ITS data directories	Newline-separated repository-relative directories containing an its subdirectory, for example po for po/its. Earlier directories override later directories and bundled rules.

Declanșări:

Add-on installation, Manual trigger, Repository post-update

Updates the gettext template using Meson gettext conventions.

This add-on updates the template configured in Șablon pentru traduceri noi. It is available for gettext PO components, and the component must define a template for new translations.

The selected update frequency applies to automatic runs after repository refreshes. Installing or reconfiguring the add-on runs it immediately, and manual runs from add-on management or the API also bypass the frequency schedule. After a successful update, Weblate commits the changed template and reloads source strings.

The template update does not update translation PO files by itself. Keep Actualizare fișiere PO pentru a se potrivi cu POT (msgmerge) installed when translation files should follow template changes automatically. The install form for this add-on can install that add-on, but existing add-on settings do not show that installation option again.

Meson requirements

This add-on requires xgettext; it does not invoke Meson. It follows Meson gettext conventions by reading POTFILES or POTFILES.in from the gettext directory and passing the GLib keyword and format-flag preset to xgettext.

The gettext directory is the directory containing the template configured in Șablon pentru traduceri noi. It must contain meson.build and POTFILES or POTFILES.in. A Meson project meson.build must be present in that directory or one of its parent directories. If both POTFILES and POTFILES.in exist, POTFILES is used. An adjacent POTFILES.skip excludes listed source files from extraction.

Configure this add-on from the existing Meson gettext setup. In most Meson projects, the gettext directory is po/, the template is named after the gettext domain, and po/meson.build calls Meson’s gettext helper. Use the same template path in Șablon pentru traduceri noi, for example po/example.pot, and keep POTFILES or POTFILES.in next to that meson.build file.

Weblate does not read the source file list from meson.build. It uses POTFILES or POTFILES.in, matching Meson’s gettext convention. When the Meson project uses a non-default gettext directory or domain, mirror that layout in the component template path.

Generare fișiere MO

ID add-on:

weblate.gettext.mo

Configurație:

path	Cale către fișierul MO generat	Dacă nu este specificat, se va utiliza locația fișierului PO.
fuzzy	Include șiruri care necesită editare	Șirurile care au nevoie de editare (neclare) nu sunt de obicei pregătite pentru a fi utilizate ca traduceri.

Declanșări:

Repository pre-commit

Generează automat un fișier MO pentru fiecare fișier PO modificat.

Locația fișierului MO generat poate fi personalizată, iar câmpul pentru acesta utilizează Marcarea șablonului.

Notă

If a translation is removed, its PO file will be deleted from the repository, but the MO file generated by this add-on will not. The MO file must be removed from the upstream manually.

Actualizare fișiere PO pentru a se potrivi cu POT (msgmerge)

Schimbat în versiunea 5.13: Settings configuration has been moved to File format parameters.

ID add-on:

weblate.gettext.msgmerge

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Add-on installation, Repository post-update

Actualizează toate fișierele PO (conform configurației „Mască de fișier”) pentru a se potrivi cu fișierul POT (conform configurației „Șablon pentru traduceri noi”) utilizând msgmerge.

This add-on is essential when working with gettext PO files where the POT (template) file is updated with new strings or changes to existing strings. When the POT file is updated in the repository, this add-on automatically merges those changes into all language PO files, ensuring that:

• New translatable strings appear in all languages

• Removed strings are marked as obsolete

• Modified strings are marked as needing review (fuzzy)

Most msgmerge command-line options can be set up through file format parameters configuration. Enable the po_remove_obsolete parameter to remove obsolete #~ entries when PO files are saved.

Vezi și

• Mască de fișier

• Șablon pentru traduceri noi

• msgmerge

• Weblate actualizează fișierele de traducere în afară de traduceri?

• Updating target-language files

Update POT file (Sphinx)

Added in version 5.17.

ID add-on:

weblate.gettext.sphinx

Configurație:

interval	Update frequency	How often the add-on should update the POT file when the component is refreshed. Alegerile disponibile: daily Daily weekly Weekly monthly Lunar
normalize_header	Normalize POT header	Updates gettext headers and replaces placeholder POT comments.
location_mode	Source locations	Choose how extraction writes source locations to the POT file. Use this to keep locations in the template while omitting them from translated PO files. Alegerile disponibile: file Use file format settings keep Extract locations to the POT file omit Do not extract locations
filter_mode	Filtering	Optionally remove strings that are not useful to translate after Sphinx extraction. Alegerile disponibile: none Nici unul weblate_docs Weblate documentation

Declanșări:

Add-on installation, Manual trigger, Repository post-update

Updates the gettext template using Sphinx’s gettext builder without loading project configuration.

This add-on updates the template configured in Șablon pentru traduceri noi. It is available for gettext PO components, and the component must define a template for new translations.

The selected update frequency applies to automatic runs after repository refreshes. Installing or reconfiguring the add-on runs it immediately, and manual runs from add-on management or the API also bypass the frequency schedule. After a successful update, Weblate commits the changed template and reloads source strings.

The template update does not update translation PO files by itself. Keep Actualizare fișiere PO pentru a se potrivi cu POT (msgmerge) installed when translation files should follow template changes automatically. The install form for this add-on can install that add-on, but existing add-on settings do not show that installation option again.

Sphinx requirements

This add-on requires sphinx-build, provided by the sphinx installation extra. The template for new translations must be a .pot file below a locales directory. The directory before locales is used as the Sphinx source directory and must contain conf.py.

Extraction uses Weblate’s bundled Sphinx configuration and does not load the project configuration. Weblate runs the Sphinx gettext builder, normalizes source references to paths relative to the source directory, and copies the generated template back to the configured template path.

Update POT file (xgettext)

Added in version 5.17.

ID add-on:

weblate.gettext.xgettext

Configurație:

Update behavior
interval	Update frequency	How often the add-on should update the POT file when the component is refreshed. Alegerile disponibile: daily Daily weekly Weekly monthly Lunar
normalize_header	Normalize POT header	Updates gettext headers and replaces placeholder POT comments.
location_mode	Source locations	Choose how extraction writes source locations to the POT file. Use this to keep locations in the template while omitting them from translated PO files. Alegerile disponibile: file Use file format settings keep Extract locations to the POT file omit Do not extract locations
Input files
input_mode	Input source	Choose whether xgettext should read source files from glob patterns or from a POTFILES/POTFILES.in manifest. Alegerile disponibile: patterns Source file patterns potfiles POTFILES manifest
language	xgettext language	Programming language passed to xgettext, for example Python or C. Leave blank to let xgettext guess the language from file extensions.
source_patterns	Source file patterns	Newline-separated repository-relative glob patterns for files to extract with xgettext.
potfiles_path	POTFILES path	Repository-relative path to POTFILES or POTFILES.in. Entries are resolved relative to the repository root. If present next to the manifest, POTFILES.skip excludes listed files from extraction.
Comment extraction
comment_mode	Code comments	Choose whether xgettext should extract no comments, all comments, or only comments marked with a specific tag. Alegerile disponibile: off Do not extract comments all Extract all comments tagged Extract comments with tag
comment_tag	Comment tag	Tag passed to xgettext for comment extraction when using tagged comment mode.
Keywords
keyword	Additional keywords	Newline-separated extra keywords passed to xgettext using –keyword.
keyword_exclusive	Use keywords exclusively	When enabled, passes --keyword without a value to xgettext before the additional keyword, disabling all default keywords so that only the keyword specified above is recognized.
Checks and ITS data
checks	xgettext checks	Additional xgettext validation checks to enable for extracted messages. Alegerile disponibile: ellipsis-unicode ellipsis-unicode space-ellipsis space-ellipsis quote-unicode quote-unicode bullet-unicode bullet-unicode
data_dirs	ITS data directories	Newline-separated repository-relative directories containing an its subdirectory, for example po for po/its. Earlier directories override later directories and bundled rules.

Declanșări:

Add-on installation, Manual trigger, Repository post-update

Updates the gettext template using xgettext on selected source files.

This add-on updates the template configured in Șablon pentru traduceri noi. It is available for gettext PO components, and the component must define a template for new translations.

The selected update frequency applies to automatic runs after repository refreshes. Installing or reconfiguring the add-on runs it immediately, and manual runs from add-on management or the API also bypass the frequency schedule. After a successful update, Weblate commits the changed template and reloads source strings.

The template update does not update translation PO files by itself. Keep Actualizare fișiere PO pentru a se potrivi cu POT (msgmerge) installed when translation files should follow template changes automatically. The install form for this add-on can install that add-on, but existing add-on settings do not show that installation option again.

xgettext requirements

This add-on requires xgettext. Configure either source file patterns or a POTFILES / POTFILES.in manifest. Source file patterns are repository-relative glob patterns and only matching repository files are passed to xgettext.

Entries in POTFILES or POTFILES.in are resolved relative to the repository root. They must be relative paths, stay inside the repository, and point to existing files. Blank lines and lines starting with # are ignored. If a POTFILES.skip file exists next to the manifest, its entries are excluded from extraction.

Automatic repository refresh runs are skipped unless the changed files match the configured source patterns, match files listed in the manifest, change a watched manifest, or change the add-on configuration.

Start from the build-system extraction setup when configuring this add-on. Autotools projects usually keep gettext inputs in po/POTFILES.in and options such as the gettext domain and xgettext flags in po/Makevars or related Makefile.am files. Use manifest mode with the same POTFILES.in when its entries are plain repository-relative source paths, and copy relevant extraction behavior into the add-on settings, for example the language, comment extraction, checks, and additional keyword.

For other build systems, use the source list or extraction command they already run as the source of truth. CMake, custom Makefiles, npm scripts, or project specific extraction scripts often call xgettext directly or generate an intermediate file list. Configure source patterns for simple layouts, or use manifest mode when the project maintains a plain file list. If a build-system manifest contains transformations or prefixes that are not file paths, convert it to plain repository-relative paths before using it as POTFILES.

Mixed source formats and ITS rules

Leave xgettext language blank to extract messages from different formats into the same POT. Include all inputs in the source patterns or POTFILES, for example:

common/messages.py
qt/application.desktop
qt/application.policy
data/application.metainfo.xml

Desktop entries use the native xgettext parser. Weblate bundles ITS rules for Polkit policies, AppStream/MetaInfo, GSettings, GTK Builder, and Shared MIME Info. These rules are included in the Weblate package, including Docker installations; no additional system packages are required for these formats. The Update POT file (Meson) add-on uses the same rules.

Extraction follows upstream gettext and ITS behavior. In particular, desktop extraction includes keys such as Name, GenericName, and Comment; Polkit rules select description and message elements without filtering by gettext-domain. Use untranslated policy sources: upstream Polkit rules also select elements carrying xml:lang.

For custom XML formats or overrides, configure ITS data directories. Enter one repository-relative directory per line, in priority order. Each must contain an its/ subdirectory with .loc locating rules and .its extraction rules. For example, enter po for po/its/example.loc and po/its/example.its, or . for its/ at the repository root. In API add-on configuration, use a list: "data_dirs": ["po", "data"].

Earlier directories take precedence over later ones, followed by Weblate’s bundled rules and gettext’s system rules. The directories are passed through GETTEXTDATADIRS. Configure them explicitly even when using Meson; Weblate does not read data_dirs from meson.build or inherit an administrator’s GETTEXTDATADIRS environment variable.

Rule directories and files must stay inside the repository and must not be symbolic links. A locating rule’s target must name an existing .its file in the same directory. DTDs, entity declarations, and external rule references are not supported. Weblate validates project-local rules before extraction and reports invalid rules as add-on errors. Changes, additions, or deletions in the configured its/ directories trigger extraction even when source files have not changed.

Vezi și

GNU gettext ITS rules and locating rules.

Comasează comiteri Git

ID add-on:

weblate.git.squash

Configurație:

squash	Comitere prin comasare	Alegerile disponibile: all Toate comiterile într-una singură language Pentru fiecare limbă în parte file Pentru fiecare fișier în parte author Pentru fiecare autor în parte author-language Per author and language
append_trailers	Adăugă trailere la mesajul de comitere comasată	Liniile de trailer sunt linii care se aseamănă cu anteturile de e-mail RFC 822, la sfârșitul părții de formă liberă a unui mesaj de comitere, cum ar fi „Co-autor: …”.
commit_message	Mesaj comitere	Acest mesaj de comitere va fi utilizat în locul mesajelor de comitere combinate de la comiterile comasate.

Declanșări:

Add-on installation, Repository post-commit

Comasează comiteri Git înainte de a încărca modificările.

Sugestie

To avoid unnecessary conflicts, it is recommended to configure automatic receiving of upstream changes by webhooks or API, see Actualizarea depozitelor.

Comițările Git pot fi eliminate înainte de împingerea modificărilor în unul dintre următoarele moduri:

• Toate comiterile într-una singură

• Pentru fiecare limbă în parte

• Pentru fiecare fișier în parte

• Pentru fiecare autor în parte

• Per author and language

Mesajele de confirmare originale sunt păstrate, dar se pierde paternitatea, cu excepția cazului în care se selectează Per author sau mesajul de confirmare este personalizat pentru a o include.

Mesajele de confirmare originale pot fi opțional înlocuite cu un mesaj de confirmare personalizat.

Remetele (commit lines like Co-authored-by: …) pot fi opțional eliminate din mesajele de confirmare originale și adăugate la sfârșitul mesajului de confirmare strivit. Acest lucru generează, de asemenea, creditul corespunzător Co-authored-by: pentru fiecare traducător.

Personalizare ieșire JSON

Schimbat în versiunea 5.12: Avoid spaces after separators option added.

Removed in version 5.13: Replaced by File format parameters.

Resetează depozitarul la sursa principală

Added in version 5.17.

ID add-on:

weblate.hosted.reset

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Add-on installation, Daily

Elimină toate modificările din depozitarul Weblate în fiecare noapte.

Formatare fișier de proprietăți Java

ID add-on:

weblate.properties.sort

Configurație:

case_sensitive

Enable case-sensitive key sorting

Declanșări:

Repository pre-commit

Formatează și sortează fișierul de proprietăți Java.

• Consolidează liniile noi la cele Unix.

• Formatarea cu majuscule a secvențelor de evacuare Unicode (în cazul în care acestea sunt prezente).

• Șiruri cu observații.

• Sortează șirurile de caractere în funcție de chei.

• Renunță la șirurile duplicate.

Elimină comentariu învechit

ID add-on:

weblate.removal.comments

Configurație:

age

Zile de păstrat

Declanșări:

Add-on installation, Daily

Setare termen pentru eliminare comentarii.

Acest lucru poate fi util pentru a elimina comentariile vechi care ar putea fi depășite. Folosiți-o cu grijă, deoarece faptul că comentariile devin vechi nu înseamnă că și-au pierdut importanța.

Elimină sugestie învechită

ID add-on:

weblate.removal.suggestions

Configurație:

age	Zile de păstrat
votes	Prag de vot	Threshold for removal. Leave empty to remove suggestions regardless of votes. This field has no effect with voting turned off.

Declanșări:

Add-on installation, Daily

Setare termen pentru eliminare sugestii.

Poate fi foarte utilă în legătură cu votarea sugestiilor (see Evaluare reciprocă) pentru a elimina sugestiile care nu primesc suficiente voturi pozitive într-un anumit interval de timp.

Actualizare fișiere RESX

ID add-on:

weblate.resx.update

Configurație:

Acest add-on nu are nicio configurație.

Declanșări:

Add-on installation, Repository post-update

Actualizează toate fișierele de traducere pentru a se potrivi cu fișierul sursă monolingv din sursă principală. Șirurile neutilizate sunt eliminate, iar cele noi sunt adăugate ca copii ale șirului sursă.

Sugestie

Utilizați Curăță fișierele de traducere dacă doriți să eliminați doar cheile de traducere vechi.

Vezi și

Weblate actualizează fișierele de traducere în afară de traduceri?

Slack Webhooks

Added in version 5.12.

ID add-on:

weblate.webhook.slack

Configurație:

webhook_url	Webhook URL
event_filter	Change events to trigger	Choose which change events should trigger this add-on. Change events to trigger
events	Selected change events	Selected change events

Declanșări:

Event change

Sends notification to a Slack channel based on selected events.

Atenționare

The notification content might show HTML tags. This is a known issue that will be soon addressed; see https://github.com/WeblateOrg/weblate/issues/15056.

Sugestie

To obtain a webhook URL, follow the steps outlined in the Slack Incoming Webhooks documentation

Webhook

Added in version 5.11.

Schimbat în versiunea 5.15: Compliance of the secret length with the specification is now validated.

ID add-on:

weblate.webhook.webhook

Configurație:

webhook_url	Webhook URL
secret	Webhook secret	The Standard Webhooks secret is a base64 encoded string.
event_filter	Change events to trigger	Choose which change events should trigger this add-on. Change events to trigger
events	Selected change events	Selected change events

Declanșări:

Event change

Sends notifications to external services based on selected events, following the Standard Webhooks specification.

The request payload complies with the Weblate Messaging schema. The action field uses the action name listed in Selected change events. The OpenAPI description can also be found at /api/docs/. Sample request body:

{
   "change_id": 99,
   "action": "Translation changed",
   "timestamp": "2019-08-24T14:15:22Z",
   "target": "Nazdar svete!",
   "old": "Nazdar!",
   "source": "Hello, world",
   "url": "/translate/project-slug/component-slug/cs/?checksum=46add148a53cab6f",
   "author": "author-username",
   "user": "user-username",
   "project": "project-slug",
   "component": "component-slug",
   "translation": "cs"
}

Sample request body with categories:

{
   "change_id": 8910,
   "action": "Component renamed",
   "timestamp": "2025-06-11T07:15:09Z",
   "target": ["new-name"],
   "old": ["component-slug"],
   "url": "/projects/project-slug/parent-category/child-category/sub-category/component-slug/",
   "user": "testuser",
   "project": "project-slug",
   "component": "component-slug",
   "category": [
      "sub-category",
      "child-category",
      "parent-category"
   ]
}

Sample request headers:

{
   "webhook-id": "7f1c5477f6275a69af7b83236c20cb1a",
   "webhook-timestamp": "1748505623.044281",
   "webhook-signature": "v1,Ceo5qEr07ixe2NLpvHk3FH9bwy/WavXrAFQ/9tdO6mc="
}

The webhook-signature is a space separated list of HMAC signatures generated using the secret string, the request payload, the webhook-timestamp, and the webhook-id. This ensures the authenticity and integrity of the webhook request.

The provided secret is a base64 encoded string between 24 bytes (192 bits) and 64 bytes (512 bits). It can be prefixed with whsec_ for easy identification.

To verify a request, you can use the Webhook.verify method from the standardwebhooks library or an implementation of the „Standard Webhooks Specification”.

Vezi și

• Standard Webhooks Specification

• Weblate Messaging

• Python library for Standard Webhooks

The Traducere automată mode Add as approved translation creates approved strings when reviews are enabled for the target language. If the project settings or a language workflow override disable reviews, it creates translated strings instead. The configured mode is preserved, including for project-wide and site-wide add-ons whose targets have different review settings. Configuring this mode requires the usual add-on management permission; it does not require the configuring user to be a reviewer.

The Translation files CDN and CDN de localizare JavaScript add-ons publish manifest.json at their CDN base URL. Clients can download it without an API token to discover available languages and translation files:

{
  "schemaVersion": 1,
  "locales": {
    "cs": [
      {
        "url": "cs.json",
        "sha256": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
        "size": 123
      }
    ]
  }
}

The locales keys are Weblate language codes. Each value lists the published files for that language, sorted by URL. The url is relative to the manifest URL, sha256 is the SHA-256 checksum of the published bytes, and size is the file size in bytes. Multi-file translations have several entries per language. The JavaScript add-on includes only languages meeting its translation threshold. Source-language inclusion follows each add-on’s existing publication rules. The JavaScript loader and the manifest itself are not listed. When no translation files are published, locales is an empty object. The root filename manifest.json is reserved for this manifest. Weblate validates each manifest against the CDN manifest before publishing it.

Translation files are written before the manifest is replaced, and stale files are removed afterwards. File URLs remain mutable, and CDN caches can refresh the manifest and translation files at different times. If a download fails or its checksum does not match, refresh the manifest and retry the download. The manifest does not provide an immutable snapshot or revoke cached copies of removed files. Existing add-on installations publish a manifest on their next successful publication.

The Kotlin SDK CDN add-on uses a separate build-specific manifest format.

The Descoperire componente add-on stops with an error if the repository scan exceeds 100,000 paths or matching translation files would require more than 1,000,000 path-to-mask comparisons. The comparison limit is checked using the number of repository paths multiplied by the number of file masks. These fixed limits bound resource consumption when repository content determines the masks. When either limit is exceeded, discovery does not create or remove components.

When configuring the add-on, Weblate also suggests presets detected from the repository. Preset detection analyzes at most 4,096 distinct results with file masks no longer than 512 characters or 16 path segments. It samples groups of more than 128 compatible results and limits itself to 8,192 comparisons, 50 presets, and eight examples per preset. If a limit omits results or comparisons, Weblate warns that suggestions might be incomplete. You can enter the configuration manually.

The Webhook and Slack Webhooks add-ons request uncompressed responses and reject responses with a Content-Encoding other than identity before reading their bodies. They limit each response body to 1 MiB and response headers to 64 KiB, including duplicate headers and separators. If a response is encoded or either fixed limit is exceeded, Weblate closes the response and records an add-on error without storing the response body or headers. The remote service might already have accepted the notification even when Weblate records this error.

Obsolete add-ons

Contribuitori în comentariu

Removed in version 2026.10: Replaced by Contributor comments.

Existing installations of weblate.gettext.authors are migrated to the gettext value of the po_contributor_comments file format parameter for each affected PO component. This includes components covered by category-, project-, and site-wide installations. New components default to disabled unless their file format parameters are copied from another component.

Remove weblate.addons.gettext.GettextAuthorComments from custom WEBLATE_ADDONS lists and weblate.gettext.authors entries from DEFAULT_ADDONS. Configure Contributor comments instead.

Personalizare ieșire XML

Added in version 4.15.

Removed in version 5.13: Replaced by File format parameters.

Personalizare ieșire YAML

Removed in version 5.13: Replaced by File format parameters.

Common add-on parameters

Translation services

Alegerile disponibile:

alibaba	Alibaba
aws	Amazon Translate
anthropic	Anthropic
apertium-apy	APy Apertium
microsoft-translator	Azure AI Translator
azure-openai	Azure OpenAI
baidu	Baidu
cyrtranslit	CyrTranslit
deepl	DeepL
glosbe	Glosbe
google-translate-api-v3	Google Cloud Translation Advanced
google-translate	Google Cloud Translation Basic
ltengine	LTEngine
libretranslate	Traducere Libre
mistral	Mistral
modernmt	ModernMT
mymemory	MyMemory
netease-sight	Vedere Netease
ollama	Ollama
openai	OpenAI
sap-translation-hub	Centrul de traduceri SAP
systran	Systran
weblate	Weblate
weblate-translation-memory	Memorie de traducere Weblate
yandex	Yandex
yandex-v2	Yandex v2
youdao-zhiyun	Youdao Zhiyun
etranslation	eTranslation
tmserver	tmserver

Format fișier

Alegerile disponibile:

apple-xliff	XLIFF 1.2 with Apple extensions
appstore	Fișiere de metadate magazin de aplicații
arb	Fișier ARB
aresource	Android String Resource
asciidoc	AsciiDoc file
ass	Fișier subtitrări Advanced SubStation Alpha
catkeys	Haiku catkeys
cmp-resource	Compose Multiplatform Resource
csv	Fișier CSV
csv-multi	Fișier CSV multivaloare
csv-simple	Fișier CSV simplu
dokuwiki	Fișier text DokuWiki
dtd	Fișier DTD
flatxml	Fișier Flat XML
fluent	Fișier Fluent
formatjs	Format.JS JSON file
go-i18n-json	Fișier JSON go-i18n v1
go-i18n-json-v2	Fișier JSON go-i18n v2
go-i18n-toml	go-i18n TOML file
gotext	Fișier JSON gotext
gwt	Proprietăți GWT
html	Fișier HTML
i18next	Fișier JSON i18next v3
i18nextv4	Fișier JSON i18next v4
idml	Fișier IDML
ini	Fișier INI
islu	Fișier Inno Setup INI
joomla	Fișier de limbă Joomla
json	Fișier JSON
json-nested	Fișier de structură imbricata JSON
laravel	Șiruri Laravel PHP
markdown	Fișier Markdown
mdx	MDX file
mediawiki	Fișier text MediaWiki
mi18n-lang	@draggable/i18n lang file
moko-resource	Mobile Kotlin Resource
nextcloud-json	Nextcloud JSON file
odf	Fișier OpenDocument
php	Șiruri PHP
po	Fișier gettext PO
po-mono	Fișier gettext PO (monolingv)
poxliff	XLIFF 1.2 cu extensii gettext
properties	Java Properties
rc	Fișier RC
resjson	RESJSON file
resourcedictionary	Fișier ResourceDictionary
resx	Fișier de resurse .NET
ruby-yaml	Fișier Ruby YAML
srt	Fișier subtitrări SubRip
ssa	Fișier subtitrări SubStation Alpha
strings	Șiruri iOS
stringsdict	Fișier Stringsdict
sub	Fișier subtitrări MicroDVD
tbx	Fișier TermBase eXchange
toml	TOML file
ts	Qt Linguist translation file (version 2)
ts1	Qt Linguist translation file (version 1)
txt	Fișier text simplu
webextension	Fișier JSON WebExtension
wxl	WixLocalization file
xliff	Fișier de traducere XLIFF 1.2
xliff2	XLIFF 2.0 translation file
xlsx	Excel Open XML
xwiki-fullpage	XWiki Full Page
xwiki-java-properties	XWiki Java Properties
xwiki-page-properties	XWiki Page Properties
yaml	Fișier YAML

Change events to trigger

Alegerile disponibile:

content	Translation content events
all	All change events
custom	Selected change events

Selected change events

The following change actions can appear in notification payloads. Fedora Messaging uses the identifier column in message topics, while webhook payloads use the name column in the action field.

Alegerile disponibile:

ID	Identifier	Nume	Descriere
0	resource_updated	Resursă actualizată	A translation file was synchronized with its repository.
1	translation_completed	Traducere finalizată	A language translation became fully translated after an individual edit. Automatic translation, uploads, and bulk edits do not emit this event.
2	translation_changed	Traducere schimbată	An existing translation was edited by a user.
3	comment_added	Comentariu adăugat	A comment was added to a string.
4	suggestion_added	Sugestie adăugată	A translation suggestion was added.
5	translation_added	Traducere adăugată	A previously untranslated string was translated by a user.
6	automatically_translated	Tradus automat	A translation was added or changed by automatic translation. This is emitted instead of Translation added or Translation changed.
7	suggestion_accepted	Sugestie acceptată	A translation suggestion was accepted as the translation.
8	translation_reverted	Traducere inversată	A translation was restored to an earlier value.
9	translation_uploaded	Traducere încărcată	A translation was added or changed by a translation file upload. This is emitted instead of Translation added or Translation changed.
13	source_string_added	Șir sursă adăugat	A source string was added outside repository or upload updates.
14	component_locked	Componentă blocată	A component was locked for translation.
15	component_unlocked	Componentă deblocată	A component was unlocked for translation.
17	changes_committed	Modificări comise	Pending component changes were committed.
18	changes_pushed	Modificări încărcate	Repository changes were pushed upstream.
19	repository_reset	Depozitar resetat	A repository was reset to its upstream state.
20	repository_merged	Depozitar îmbinat	Upstream repository changes were merged.
21	repository_rebased	Depozitar rebazat	Repository changes were rebased on upstream.
22	repository_merge_failed	Eroare la îmbinarea depozitarului	Merging upstream repository changes failed.
23	repository_rebase_failed	Eroare la rebazarea depozitarului	Rebasing repository changes failed.
24	parsing_failed	Înterpretare eșuată	Weblate could not parse a translation file.
25	translation_removed	Traducere eliminată	A language translation was removed.
26	suggestion_removed	Sugestie eliminată	A translation suggestion was removed.
27	translation_replaced	Traducere înlocuită	A translation was changed by a search-and-replace operation. This is emitted instead of Translation changed.
28	repository_push_failed	Eroare la încărcarea depozitarului	Pushing repository changes upstream failed.
29	suggestion_removed_during_cleanup	Sugestie eliminată în timpul curățării	An obsolete translation suggestion was removed during cleanup.
30	source_string_changed	Șir sursă modificat	A source string was edited in Weblate.
31	string_added	Șir adăugat	A new string was added in Weblate.
32	bulk_status_changed	Schimbare stare în masă	The translation state of one or more strings was changed in bulk.
33	visibility_changed	Vizibilitate modificată	Project or component visibility was changed.
34	user_added	Utilizator adăugat	A user was granted access.
35	user_removed	Utilizator eliminat	A user’s access was removed.
36	translation_approved	Traducere aprobată	A translation was approved during review.
37	marked_for_edit	Marcată pentru editare	A translation was marked as needing editing.
38	component_removed	Componentă eliminată	A translation component was removed.
39	project_removed	Proiect eliminat	A translation project was removed.
41	project_renamed	Proiect redenumit	A translation project was renamed.
42	component_renamed	Componentă redenumită	A translation component was renamed.
43	moved_component	Componentă mutată	A component was moved within a project.
45	contributor_joined	S-a alăturat contribuitor	A user made their first contribution to a translation.
46	announcement_posted	Anunț publicat	An announcement was posted.
47	alert_triggered	Alertă declanșată	A component alert was triggered.
48	language_added	Limbă adăugată	A language translation was added.
49	language_requested	Limbă solicitată	A user requested a new language.
50	project_created	Proiect creat	A translation project was created.
51	component_created	Componentă creată	A translation component was created.
52	user_invited	Utilizator invitat	A user was invited to a project.
53	repository_notification_received	Notificare depozitar primită	Weblate received a repository notification from a code host.
54	translation_replaced_file_by_upload	Înlocuire fișier cu traduceri prin încărcare	A translation file was replaced by an uploaded file.
55	license_changed	Licență schimbată	Project or component license information changed.
56	contributor_license_agreement_changed	Contributor license agreement changed	The contributor license agreement was changed.
57	screenshot_added	Captură de ecran adăugată	A screenshot was associated with a string.
58	screenshot_uploaded	Captură de ecran încărcată	A screenshot image was uploaded.
59	string_updated_in_the_repository	Șir actualizat în depozitar	A string was changed while synchronizing from the repository.
60	add-on_installed	Supliment instalat	An add-on was installed.
61	add-on_configuration_changed	Configurație supliment modificată	An add-on’s configuration was changed.
62	add-on_uninstalled	Supliment dezinstalat	An add-on was uninstalled.
63	string_removed	Șir eliminat	A string was removed from a translation.
64	comment_removed	Comentariu eliminat	A string comment was removed.
65	comment_resolved	Comentariu rezolvat	A string comment was marked as resolved.
66	explanation_updated	Explicație actualizată	The explanation for a source string was updated.
67	category_removed	Categorie eliminată	A component category was removed.
68	category_renamed	Categorie redenumită	A component category was renamed.
69	category_moved	Categorie mutată	A component category was moved.
70	saving_string_failed	Salvare șir eșuată	Weblate could not save a changed string.
71	string_added_in_the_repository	String added in the repository	A new string was found while synchronizing from the repository.
72	string_updated_in_the_upload	String updated in the upload	A string was changed while processing an uploaded file.
73	string_added_in_the_upload	String added in the upload	A new string was found while processing an uploaded file.
74	translation_updated_by_source_upload	Translation updated by source upload	A translation was synchronized after uploading a source file.
75	component_translation_completed	Component translation completed	All language translations in a component became fully translated after an individual edit. Automatic translation, uploads, and bulk edits do not emit this event.
76	applied_enforced_check	Applied enforced check	A translation was marked as needing editing by an enforced check.
77	propagated_change	Propagated change	A translation edit was propagated to another matching string.
78	file_uploaded	File uploaded	A file was uploaded to a translation.
79	extra_flags_updated	Extra flags updated	Additional source-string flags were updated.
80	font_uploaded	Font uploaded	A font was uploaded.
81	font_changed	Font changed	An uploaded font was changed.
82	font_removed	Font removed	An uploaded font was removed.
83	forced_synchronization_of_translations	Forced synchronization of translations	Translation files were forcibly synchronized with the repository.
84	forced_rescan_of_translations	Forced rescan of translations	Translation files were forcibly rescanned for changes.
85	screenshot_removed	Screenshot removed	A screenshot was removed.
86	label_added	Label added	A label was added to a string.
87	label_removed	Label removed	A label was removed from a string.
88	repository_cleanup	Repository cleanup	The repository working tree was cleaned up.
89	source_string_added_in_the_upload	Source string added in the upload	A source string was added while processing an uploaded file.
90	source_string_added_in_the_repository	Source string added in the repository	A source string was added while synchronizing from the repository.
91	project_backed_up	Project backed up	A project backup was created.
92	project_restored	Project restored	A project was restored from a backup.
93	component_restored	Component restored	A component was restored from a backup.
94	user_edit_reverted	User edit reverted	All selected edits by a user were reverted.
95	project_setting_changed	Project setting changed	A project setting was changed.
96	component_setting_changed	Component setting changed	A component setting was changed.
97	user_access_changed	User access changed	A user’s access permissions were changed.
98	workspace_created	Workspace created	A workspace was created.
99	workspace_setting_changed	Workspace setting changed	A workspace setting was changed.
100	project_moved	Project moved	A project was moved into or out of a workspace.
101	remote_repository_updated	Remote repository updated	A remote repository update was completed.
102	remote_repository_update_failed	Remote repository update failed	Updating a remote repository failed.
103	alert_dismissed	Alert dismissed	A component alert was dismissed.
104	alert_reopened	Alert reopened	A component alert was reopened after its context changed.

Personalizarea listei de add-on-uri

Lista de add-on-uri este configurată prin WEBLATE_ADDONS. Pentru a adăuga un alt addon, este suficient să includeți numele absolut al clasei în această setare.

Add-on de scriere

Puteți să vă scrieți propriile add-on-uri, să creați o subclasă de weblate.addons.base.BaseAddon pentru a defini metadatele addon-ului și apoi să implementați un callback pentru a face procesarea.

Vezi și

Dezvoltarea de add-on-uri

Executarea scripturilor din add-on

Suplimentele pot fi utilizate și pentru a executa scripturi externe. Acest lucru era integrat în Weblate, dar acum trebuie să scrieți niște cod pentru a înfășura scriptul vostru cu un add-on.

# Copyright © Michal Čihař <michal@weblate.org>
#
# SPDX-License-Identifier: GPL-3.0-or-later

"""Example pre commit script."""

from __future__ import annotations

from typing import ClassVar

from django.utils.translation import gettext_lazy

from weblate.addons.events import AddonEvent
from weblate.addons.scripts import BaseScriptAddon


class ExamplePreAddon(BaseScriptAddon):
    # Event used to trigger the script
    events: ClassVar[set[AddonEvent]] = {
        AddonEvent.EVENT_PRE_COMMIT,
    }
    # Name of the addon, has to be unique
    name = "weblate.example.pre"
    # Verbose name and long description
    verbose = gettext_lazy("Execute script before commit")
    description = gettext_lazy("This add-on executes a script.")

    # Script to execute
    script = "/bin/true"
    # File to add in commit (for pre commit event)
    # does not have to be set
    add_file = "po/{{ language_code }}.po"

Pentru instrucțiuni de instalare, consultați Custom quality checks, add-ons, translation services and auto-fixes.

Scriptul este executat cu directorul curent setat la rădăcina depozitului VCS pentru orice componentă dată.

În plus, sunt disponibile următoarele variabile de mediu:

WL_VCS

Sistemul de control al versiunilor utilizat.

WL_REPO

URL-ul depozitului din amonte.

WL_PATH

Calea absolută către depozitul VCS.

WL_BRANCH

Ramura de depozit configurată în componenta curentă.

WL_FILEMASK

Masca de fișier pentru componenta curentă.

WL_TEMPLATE

Numele de fișier al șablonului pentru traducerile monolingve (poate fi gol).

WL_NEW_BASE

Numele de fișier al fișierului utilizat pentru crearea de noi traduceri (poate fi gol).

WL_FILE_FORMAT

Format de fișier utilizat în componenta curentă.

WL_LANGUAGE

Limba traducerii procesate în prezent (nu este disponibilă pentru cârligele la nivel de componentă).

WL_PREVIOUS_HEAD

HEAD anterior după actualizare (disponibil numai după rularea cârligului post-update).

WL_COMPONENT_SLUG

Denumirea componentei utilizată pentru a construi URL-ul.

WL_PROJECT_SLUG

Denumirea proiectului utilizată pentru a construi URL-ul.

WL_COMPONENT_NAME

Denumirea componentei.

WL_PROJECT_NAME

Numele proiectului.

WL_COMPONENT_URL

URL-ul componentei.

WL_ENGAGE_URL

URL de angajare a proiectului.

Vezi și

Configurația componentei

Prelucrarea depozitelor după actualizare

Poate fi utilizat pentru a actualiza fișierele de traducere atunci când sursa VCS din amonte se modifică. Pentru a realiza acest lucru, vă rugăm să rețineți că Weblate vede numai fișierele trimise în VCS, deci trebuie să trimiteți modificările ca parte a scriptului.

De exemplu, cu Gulp puteți face acest lucru folosind următorul cod:

#! /bin/sh
gulp --gulpfile gulp-i18n-extract.js
git commit -m 'Update source strings' src/languages/en.lang.json

Pre-angajare de procesare a traducerilor

Utilizați scriptul de trimitere pentru a modifica automat o traducere înainte de a fi trimisă în depozit.

Acesta este transmis ca un singur parametru care constă în numele de fișier al unei traduceri curente.

Add-on activity logging

Add-on activity log keeps track of the add-on execution and can be used to keep track of add-on activity.

Each entry records whether processing is pending, successful, failed, or skipped. Skipped entries include the reason the add-on did not run, such as an incompatible component, no relevant changes, or a configured schedule that is not due yet. A successful entry can still mean that the add-on checked its inputs but found nothing to change.

For scope-wide add-ons that process components independently, the activity log contains a separate entry for each component.

The logs can be pruned after a certain time interval by configuring the ADDON_ACTIVITY_LOG_EXPIRY.