Weblate 基礎知識

專案和組件結構

In Weblate translations are organized into projects and components. Each project can contain number of components and those contain translations into individual languages. The component corresponds to one translatable file (for example GNU gettext PO (Portable Object) or Android 字串資源). The projects are there to help you organize component into logical sets (for example to group all translations used within one application).

Additionally, components within projects can be structured using categories. Components can belong to a category, and categories can be nested.

預設情況下，每個專案內都有對跨組件傳播的公共字串的翻譯。這減輕了重複和多版本翻譯的負擔。但假如翻譯應當有所不同，可以使用 允許翻譯再用 通過 組件配置 停用翻譯傳播。

儲存庫整合

Weblate is built to integrate with upstream version control repository, 持續在地化 describes building blocks and how the changes flow between them.

也參考

架構概覽 describes how Weblate works internally.

使用者歸屬

Weblate keeps the translations properly authored by translators in the version control repository by using name and e-mail. Having a real e-mail attached to the commit follows the distributed version control spirits and allows services like GitHub to associate your contributions done in Weblate with your GitHub profile.

This feature also brings in risk of misusing e-mail published in the version control commits. Moreover, once such a commit is published on public hosting (such as GitHub), there is effectively no way to redact it. Weblate allows choosing a private commit e-mail in 帳號 to avoid this.

Therefore, admins should consider this while configuring Weblate:

  • Such a usage of e-mail should be clearly described in service terms in case such document is needed. 法律模組 can help with that.

  • PRIVATE_COMMIT_EMAIL_OPT_IN 可以讓電子郵件預設隱藏。