Dasar Weblate¶
Struktur proyek dan komponen¶
Di Weblate, terjemahan diatur ke dalam proyek dan komponen. Setiap proyek dapat berisi sejumlah komponen, dan komponen tersebut berisi terjemahan ke dalam bahasa individual. Komponen tersebut berkaitan dengan satu berkas yang dapat diterjemahkan (misalnya GNU gettext PO (Objek Portabel) atau Sumber daya string Android). Proyek ini berfungsi untuk membantu Anda mengatur komponen ke dalam rangkaian logis (misalnya, untuk menggrupkan semua terjemahan yang digunakan dalam satu aplikasi).
Selain itu, komponen dalam proyek dapat disusun menggunakan kategori. Komponen dapat berada dalam suatu kategori, dan kategori dapat disarangkan.
Secara internal, setiap proyek memiliki terjemahan ke string umum yang disebarkan ke komponen lain di dalamnya secara bawaan. Ini meringankan beban terjemahan yang berulang dan multiversi. Propagasi terjemahan dapat dinonaktifkan per Konfigurasi komponen menggunakan Izinkan propagasi terjemahan jika terjemahannya berbeda.
Integrasi repositori¶
Weblate dibangun untuk terintegrasi dengan repositori kontrol versi hulu, Lokalisasi berkelanjutan menjelaskan blok penyusun dan bagaimana perubahan mengalir di antara blok tersebut.
Lihat juga
Ikhtisar arsitektur menjelaskan cara kerja Weblate secara internal.
Atribusi pengguna¶
Weblate menyimpan terjemahan yang ditulis dengan benar oleh penerjemah di repositori kontrol versi dengan menggunakan nama dan alamat surel. Melampirkan alamat surel asli pada komit mengikuti aturan kontrol versi terdistribusi dan memungkinkan layanan seperti GitHub untuk mengaitkan kontribusi Anda yang dibuat di Weblate dengan profil GitHub Anda.
Fitur ini juga menimbulkan risiko penyalahgunaan surel yang dipublikasikan dalam komit kontrol versi. Selain itu, setelah komit tersebut dipublikasikan di pengehosan publik (seperti GitHub), tidak ada cara untuk menyuntingnya. Weblate memungkinkan pemilihan surel komit privat di Akun untuk menghindari hal ini.
Oleh karena itu, admin harus mempertimbangkan hal ini saat mengkonfigurasikan Weblate:
Penggunaan surel seperti itu harus dijelaskan dengan jelas dalam persyaratan layanan jika dokumen tersebut diperlukan. Modul hukum dapat membantu dalam hal itu.
PRIVATE_COMMIT_EMAIL_OPT_INdapat menjadikan surel privat secara bawaan.
Make your first translation¶
You can contribute to a project using your web browser. You do not need to install Weblate or work with its source code repository.
Find your project and language¶
Follow the translation link from the project you want to help. Projects can use Hosted Weblate or their own Weblate installation; use an account on that installation. If you arrive at its dashboard, choose Projects > Browse all projects to find the project.
Sign in, or follow the site's registration instructions. Access depends on the project: you might need to request permission from its maintainers. Some projects also accept suggestions without signing in.
If you are signed in, open your user menu and choose Settings. Under Languages, select your Translated languages and, optionally, Secondary languages you understand. Secondary languages appear above the source as additional help. Save your settings. If you are contributing anonymously, skip this step and choose your language directly in the project as described below.
Read the project's translation instructions before starting. These can explain terminology, style, priorities, and how to contact the language team. If you cannot find them, ask the maintainers which component to start with.
Choose your language and a component. A component groups related strings, such as an application's interface or its documentation. Open Untranslated strings to start with empty translations, or Unfinished strings to include translations that still need work. Use All strings or Mencari to find existing translations. If your language is missing, use the option to start or request a translation when available, or contact the maintainers.
Translate a string¶
The editor shows the source text and a field for your translation. Read any explanation, screenshot, nearby strings, and glossary entries before writing. Short strings can have several meanings: ask in Komentar if the context is unclear. Other languages can help, but their translations can also contain mistakes.
Write a natural expression of the intended meaning in your language. Follow your language's typography and the project's terminology and style. Preserve technical markers such as placeholders and markup; see Translating special text safely. When Weblate displays several plural fields, complete each one according to its label; see Jamak.
Use explanations, screenshots, and glossary terms to choose the right wording.
Quality checks highlight problems such as the missing %(days)s placeholder
in this draft. The translator can edit, save, or suggest a translation.¶
Choose the action that fits your contribution:
Save and continue saves your translation and opens the next string. Use Save and stay to remain on the current string.
Mark Needs editing when saving a translation that still needs work. Clear it after you have resolved the outstanding issues.
Suggest proposes a translation for someone to accept. Use this when you want another translator to consider your wording, or when the project only allows you to suggest changes. A suggestion does not replace the current translation until it is accepted.
Skip moves on without saving your edits. You can return later.
The available actions depend on your permissions and the project's workflow. For example, an approved translation might only allow you to suggest a change. Saving in Weblate does not mean the translation is immediately published in the application: review, repository synchronization, and releases depend on the project. See Status terjemahan and Alur kerja terjemahan.
Check your work and ask for help¶
Read your translation again after saving. If Weblate reports failing quality checks, open their explanations and correct the problem. Ignore a check only when you have confirmed it is a false positive and your permissions allow it. Passing all checks does not guarantee that the meaning or tone is correct. Review suggestions from translation memory or machine translation just as carefully as text you write yourself.
Use a translation comment for questions about your language, or a source string comment for an unclear or incorrect original. Explain the problem and include the context you have found. If source editing or source review is available, follow the project's instructions for proposing a correction; otherwise use its advertised contact or repository link. See Komentar and Menerima umpan balik string sumber.
Keep contributing¶
Watch projects you want to return to and choose your Notifikasi. Your Dasbor helps you find watched translations in your selected languages. You can also help by reviewing existing translations and suggestions when your permissions allow it.
As you become familiar with the editor, explore Pintasan papan ketik, Konteks terjemahan, Glosarium, and Mencari. The editor's History tab shows earlier changes to a string. See Preferensi for editor preferences and Mengunduh dan mengunggah terjemahan for downloading and uploading translations to work offline.