Internal Weblate

Catatan

Bab ini akan memberi Anda ikhtisar dasar tentang internal Weblate.

Weblate memperoleh sebagian besar struktur kodenya dari, dan didasarkan pada Django.

Struktur direktori

Ikhtisar cepat struktur direktori repositori utama Weblate:

docs

Kode sumber untuk dokumentasi ini, yang dapat dibangun menggunakan Sphinx.

dev-docker

Kode Docker untuk menjalankan server pengembangan, lihat Menjalankan Weblate secara lokal di Docker.

weblate

Kode sumber Weblate sebagai aplikasi Django, lihat Internal Weblate.

weblate/static

Berkas klien (CSS, Javascript dan gambar), lihat Frontend Weblate.

Modul

Weblate terdiri dari beberapa aplikasi Django (beberapa opsional, lihat Modul Weblate opsional):

accounts

Akun pengguna, profil dan notifikasi.

addons

Pengaya untuk mengubah perilaku Weblate, lihat Pengaya.

api

API berdasarkan kerangka Django REST.

auth

Autentikasi dan izin.

billing

Modul Penagihan opsional.

checks

String terjemahan modul Pemeriksaan kualitas.

fonts

Modul pemeriksaan rendering huruf.

formats

Lapisan abstraksi format berkas berdasarkan translate-toolkit.

gitexport

Modul Eksportir Git opsional.

lang

Modul yang mendefinisikan bahasa dan model jamak.

legal

Modul Modul hukum opsional.

machinery

Integrasi layanan terjemahan mesin.

memory

Memori terjemahan bawaan, lihat Memori Terjemahan.

screenshots

Pengelolaan tangkapan layar dan modul OCR.

trans

Modul utama yang menangani terjemahan.

utils

Berbagai utilitas pembantu.

vcs

Abstraksi sistem kontrol versi.

wladmin

Penyesuaian antarmuka admin Django.

Translation sources

A unit has a canonical file source and may have a translation from another language as its effective source. Keep Unit.source and Unit.source_unit canonical: repository synchronization and file formats depend on this. Use effective_source and its language and plural accessors for content shown to translators. Do not replace source on a copied unit to simulate an effective source; other fields and related objects still describe the canonical source.

Use Unit.source_snapshot when an operation needs to preserve the source text, language, plural rules, and terminology metadata together. Its identity defines source changes for dependency reconciliation, editor conflict detection, and AI diagnostics. For historical rendering and reports, read the snapshot recorded on the change, rather than reconstructing it from the current unit.

A missing configured parent remains a custom source: its text is empty, its language is retained, and its child is blocked. effective_source_unit is then None. Only removing the workflow or selecting the canonical language restores the canonical source.

Text-only accessors do not load language or plural metadata. For batch consumers that need the complete effective source, use UnitQuerySet.prefetch_translation_parent() alongside their existing unit prefetches. prefetch_source() already includes this. Ordinary searches keep the canonical query path and ordinary units retain their existing content hashes.

Source-dependent writes enter source_operation() before locking unit rows. The outer operation takes a shared project gate and reads its workflow mapping in one database round trip, including for projects without custom workflows. Workflow changes take source_project_gate(..., exclusive=True) before validation or persistence. Configuration changes affecting several projects acquire their gates in ascending project ID order. Never upgrade a shared gate to an exclusive one inside an operation.

The database gate function locks first and reads workflows in a separate statement, so a waiter sees configuration committed while it waited. Write paths use this transaction-scoped view rather than cached model settings. Nested operations reuse it; rolled-back savepoints discard their dependency work. Queued dependencies are reconciled before commit and external memory updates are scheduled after commit. Source-change history is written in bulk, preserving individual records while batching their notification dispatch.

Acquire any required repository locks before project gates, then component and unit row locks. Reconciliation itself only changes database state and does not acquire repository locks. Apply this boundary to bulk imports, automatic translation, file-save failures, deletion, and restoration as well as editor writes. Language and plural-rule changes require exclusive gates before their updates. Historical migrations use historical models without these runtime helpers.

Machinery source selection happens before mapping language codes to a provider. Use get_unit_source_language() for translation and uses_custom_source() for workflow-specific glossary handling. Provider codes can merge distinct language variants, so code equality cannot determine whether a workflow source was selected. Explicit component or secondary source selection takes precedence over the workflow source.

Tugas latar belakang internal

Petunjuk

Bagian ini menjelaskan internal tugas Celery. Tugas latar belakang menggunakan Celery menjelaskan cara mengkonfigurasikan Celery untuk menjalankan tugas.

Weblate menggunakan Celery untuk menjalankan tugas di latar belakang. Beberapa tugas dipicu oleh peristiwa, dan beberapa tugas dipicu oleh jadwal.

Celery Beat digunakan untuk menjadwalkan tugas, dan django-celery-beat digunakan untuk menyimpan jadwal tugas berkala dalam basis data. Jadwal tugas dikonfigurasikan dalam tasks.py di setiap aplikasi Django.

Tugas tersebut diproses menggunakan beberapa antrean; peruteannya dikonfigurasi di settings.py. Antrian dirancang untuk memisahkan berbagai jenis beban kerja:

celery

Antrian bawaan tempat tugas latar belakang diproses.

notify

Mengirimkan surel notifikasi, baik untuk peristiwa di Weblate maupun untuk autentikasi atau pendaftaran. Ini adalah antrian terpisah untuk memperlancar pengiriman surel meskipun ada tugas lain yang tertunda.

memory

Memperbarui entri memori terjemahan. Antrian pembaruan bisa panjang saat mengimpor string baru, dan pemrosesan yang lama tidak terlalu berpengaruh di sini, sehingga memiliki antrian terpisah menghindari pemblokiran tugas lain.

backup

Tugas pencadangan tidak dapat dijalankan secara paralel, dan satu pekerja khusus akan mempermudahnya.

translate

Tugas terjemahan otomatis diketahui memakan waktu lama karena melibatkan layanan eksternal.