持續在地化

有適當的基礎結構，因此您的翻譯緊隨開發。這樣，翻譯人員可以一直進行翻譯，而不必在發佈之前處理大量的新文本。

也參考

與 Weblate 整合 describes basic ways to integrate your development with Weblate. Code hosting integrations lists provider-specific setup steps for common code hosting sites.

這是過程：

1. 開發人員進行變更並將其推送到版本控制系統（VCS ）儲存庫。

2. 可以選擇更新翻譯件（這取決於檔案格式，請參閱 引入新字串）。

3. Weblate pulls changes from the VCS repository, parses translation files and updates its database, see 更新儲存庫.

4. 翻譯者使用 Weblate Web 介面提交翻譯，或上傳離線變更。

5. Once the translators are finished, Weblate commits the changes to the local repository (see 簡易提交).

6. Changes are pushed back to the upstream repository (see 推送 Weblate 的變更).

提示

Upstream code hosting is not necessary, you can use Weblate with 本地檔案 where there is only the repository inside Weblate.

更新儲存庫

應該新增一些從他們的來源來更新後端儲存庫的方式。

• Use 通知掛勾 to integrate with the majority of common code hosting services, see Code hosting integrations. You must also 啟用掛勾 for this to work.

• 在儲存庫管理中或使用 Weblate 的 REST API 或 Weblate 用戶端 來手動觸發更新

• 允許 AUTO_UPDATE 在您的Weblate事例上自動更新所有組件

• Execute updategit (with selection of project or --all to update all)

每當 Weblate 更新儲存庫時，更新後附加元件都將被觸發，請參閱 附加元件。

避免發生合併衝突

The merge conflicts from Weblate arise when same file was changed both in Weblate and outside it. Depending on the situation, there are several approaches that might help here:

• Avoiding merge conflicts by changing translation files in Weblate only

• Avoiding merge conflicts by locking Weblate while doing outside changes

• Avoiding merge conflicts by focusing on Git operations

Avoiding merge conflicts by changing translation files in Weblate only

Avoiding edits outside Weblate is easy with monolingual files — you can add new strings within Weblate and leave whole editing of the files there. For bilingual files, there is usually some kind of message extraction process to generate translatable files from the source code. In some cases, this can be split into two parts:

1. The extraction generates template (for example gettext POT is generated using xgettext).

2. Further process merges it into actual translations (the gettext PO files are updated using msgmerge).

You can perform the second step within Weblate and it will ensure that all pending changes are included before this operation.

Avoiding merge conflicts by locking Weblate while doing outside changes

Integrating Weblate into your updating process so that it flushes changes before updating the files outside Weblate can be achieved by using Weblate 的 REST API to force Weblate to push all pending changes and lock the translation while you are doing changes on your side.

進行更新的指令碼看起來像這樣：

# Lock Weblate translation
wlc lock
# Push changes from Weblate to upstream repository
wlc push
# Pull changes from upstream repository to your local copy
git pull
# Update translation files, this example is for Django
./manage.py makemessages --keep-pot -a
git commit -m 'Locale updates' -- locale
# Push changes to upstream repository
git push
# Tell Weblate to pull changes (not needed if Weblate follows your repo
# automatically)
wlc pull
# Unlock translations
wlc unlock

If you have multiple components sharing the same repository, you need to lock them all separately:

wlc lock foo/bar
wlc lock foo/baz
wlc lock foo/baj

備註

The example uses Weblate 用戶端, which needs configuration (API keys) to be able to control Weblate remotely. You can also achieve this using any HTTP client instead of Weblate 用戶端, for example curl, see Weblate 的 REST API.

儲存庫維護

The Repository maintenance view shows repository status for a project, component, or translation and lets privileged users run maintenance operations from the user interface.

The same actions can also be triggered using Weblate 的 REST API or, for the supported subset, Weblate 用戶端.

Availability of individual actions depends on permissions, the configured version control system, whether pushing is configured, and whether the selected object can be locked.

動作	What it does	Typical use
提交	Commits pending changes stored in Weblate to the local repository.	Flush pending Weblate changes before doing repository work elsewhere.
推送	Pushes committed local repository changes to the configured upstream.	Send committed translations upstream when automatic push is disabled or delayed.
更新	Fetches upstream changes and integrates them using the component's configured 合併類型.	Bring Weblate in sync with upstream using the default integration strategy.
Update with merge	Fetches upstream changes and integrates them with an explicit merge.	Override the default merge style for a single update.
Update with rebase	Fetches upstream changes and rebases local Weblate commits on top of upstream.	Keep history linear when that matches your workflow.
Update with merge without fast-forward	Fetches upstream changes and creates an explicit merge commit even when a fast-forward would be possible.	Preserve merge commits for auditing or branch-management reasons.
鎖定 / 解鎖	Prevents or allows translators to make further changes in Weblate.	Freeze translation changes while doing repository maintenance outside Weblate.
重設並丟棄	Resets Weblate's local repository to upstream and discards pending Weblate changes.	Use when upstream should overwrite the local Weblate repository state.
重設並重新套用	Resets Weblate's local repository to upstream while preserving pending translations. See Reset and reapply recovery behavior.	Recover from diverged history while keeping pending Weblate translations.
清理	Removes untracked files and stale branches from the local repository checkout.	Clean up leftover files or stale repository state in Weblate's checkout.
同步	Forces Weblate to write all known translations back to the repository files.	Repair cases where repository files became out of sync with the database state.
重新掃描	Re-reads translation files from the local repository into Weblate.	Import file changes after manual repository work or file creation.

Reset and reapply recovery behavior

The Reset and reapply operation keeps pending translations from Weblate while resetting the local repository state to match upstream.

The operation can restore pending translations only when the target language files still exist after the reset or when Weblate can create them for the component, for example using a valid 新翻譯的範本.

If neither of these conditions is met, Weblate keeps the pending changes in its database and reports a recovery error instead of failing later with a generic parse error.

Avoiding merge conflicts by focusing on Git operations

Even when Weblate is the single source of the changes in the translation files, conflicts can appear when using 匯併 Git 提交 add-on, 合併類型 is configured to Rebase, or you are squashing commits outside of Weblate (for example, when merging a pull request).

The reason for merge conflicts is different in this case - there are changes in Weblate which happened after you merged Weblate commits. This typically happens if merging is not automated and waits for days or weeks for a human to review them. Git is then sometimes no longer able to identify upstream changes as matching the Weblate ones and refuses to perform a rebase.

To approach this, you either need to minimize the amount of pending changes in Weblate when you merge a pull request, or avoid the conflicts completely by not squashing changes.

Here are few options how to avoid that:

• Do not use neither 匯併 Git 提交 nor squashing at merge time. This is the root cause why git doesn't recognize changes after merging.

• Let Weblate commit pending changes before merging. This will update the pull request with all its changes, and both repositories will be in sync.

• Use the review features in Weblate (see 翻譯工作流程) so that you can automatically merge GitHub pull requests after CI passes.

• Use locking in Weblate to avoid changes while GitHub pull request is in review.

也參考

Weblate 用戶端

Code hosting notifications

Provider-specific app and webhook instructions for GitHub, GitLab, Bitbucket, Pagure, Azure Repos, Gitea, Forgejo, and Gitee are covered in Code hosting integrations.

Provider-specific notifications

These legacy anchors are kept for compatibility. Current provider-specific app and webhook setup is documented in Code hosting integrations.

也參考

• GitHub notifications

• GitLab notifications

• Bitbucket notifications

• Pagure notifications

• Azure Repos notifications

• Gitea notifications

• Forgejo notifications

• Gitee notifications

每晚自動更新儲存庫

Weblate 在後面合併變更時，每晚自動擷取遠端儲存庫來提高效能。可以選擇將其同樣轉換為進行每晚合併，通過允許 AUTO_UPDATE。

推送 Weblate 的變更

Each translation component can have a push URL set up (see 儲存庫推送 URL), and in that case Weblate will be able to push changes to the remote repository. Weblate can also be configured to automatically push changes on every commit, see 提交時一併推送.

For the push options table and provider-specific pull, merge, and review request workflows, see 推送 Weblate 的變更.

也參考

請參閱 存取儲存庫 來設定 SSH 金鑰，和 簡易提交 獲得關於 Weblate 決定提交變更的資訊。

受保護的分支

如果在受保護的分支上使用 Weblate，可以配置使用拉取請求，並執行翻譯的實際複查（對您不知道的語言可能有問題）。另一個方法是去掉對 Weblate 推送使用者的這個限制。

例如在 GitHub，這可以在儲存庫配置中進行：

與其他相互影響

Weblate 通過使用它的 API，使與他人的交流更容易。

也參考

Weblate 的 REST API

簡易提交

Weblate 會盡可能將同一作者的提交分組到一個提交中。這大大減少了提交的數量，但是如果您想同步版本控制系統（VCS ）儲存庫，例如合併，您可能需要明確地告訴它去做提交（這對 Managers 群組是預設允許的，參閱 特權清單）。

如果多個組件分享相同的儲存庫，需要分別將他們全部鎖定：

• 某人另外變更了已經被變更的字串。

• 來自上游的結合發生了。

• 明確地請求了提交。

• A file download is requested.

• 變更比 組件配置 上定義為 變更後提交的經過時間 的時間段更陳舊。

提示

Commits are created for every component. So in case you have many components you will still see lot of commits. You might utilize 匯併 Git 提交 add-on in that case.

If you want to commit changes more frequently and without checking of age, you can schedule a regular task to perform a commit. This can be done using Periodic Tasks in Django 管理介面. First create desired Interval (for example 120 seconds). Then add new periodic task and choose weblate.trans.tasks.commit_pending as Task with {"hours": 0} as Keyword Arguments and desired interval.

用指令稿處理儲存庫

自訂 Weblate 與儲存庫互動方式是 附加元件。關於如何通過附加元件執行外部指令稿的資訊，請參閱 從附加元件執行指令稿。

跨組件保持翻譯一致

一旦具有多個翻譯組件，您會想要確保相同的字串具有相同的翻譯。這可以在幾個層次實現。

翻譯宣傳

With 允許翻譯再用 enabled (what is the default, see 組件配置), all new translations are automatically done in all components with matching strings. Such translations are properly credited to currently translating user in all components.

Propagation preconditions:

• All components have to reside in a single project (linking component is not enough).

• Enable 允許翻譯再用 to automatically reuse translations for matching strings.

• 翻譯宣傳需要金鑰來匹配單語言翻譯格式，因此在建立翻譯金鑰匙請記住。

• The strings are propagated while translating, strings loaded from the repository are not propagated.

小訣竅

This feature currently has limitations, and we want to make it more universal. Please share your feedback at https://github.com/WeblateOrg/weblate/issues/3166.

一致性檢查

在字串不同時 不一致 會啟動檢查。您可以藉此來手動複查其差異，並選擇正確的翻譯。

自動翻譯

Automatic translation based on different components can be way to synchronize the translations across components. You can either trigger it manually (see 自動翻譯) or make it run automatically on repository update using add-on (see 自動翻譯).