遷移至 Weblate

Are you using a different localization platform and considering switching to Weblate? This guide provides a quick, step-by-step process to help you migrate your translation project from platforms like Transifex, Crowdin, Lokalise, or similar services.

Weblate is designed around continuous localization with Git integration at its core, making it ideal for teams that want to keep translations close to their development workflow.

也參考

• 通過國際化來開始 for choosing the right internationalization framework

• 與 Weblate 整合 for detailed integration options

• 持續在地化 for setting up automated workflows

Prerequisites

Before starting your migration, ensure you have:

On your localization platform:

• Access to export your translation files

• List of translators and their roles/permissions

• Understanding of your current workflow (review process, automation, etc.)

對於 Weblate：

• A Weblate instance (either Hosted Weblate or self-hosted)

• Admin or project creation permissions on your Weblate instance

準備您的翻譯檔案

Export translations from your current platform

Most localization platforms allow you to export all translations at once:

• Transifex: Use their CLI tool or download translations from the web interface

• Crowdin: Export all translations as a ZIP file from project settings

• Lokalise: Use the bulk export feature

• Phrase: Download all locales from the project dashboard

提示

Keep your translation files in the format native to your internationalization framework (PO, XLIFF, JSON, etc.) rather than converting them. Weblate supports many formats.

提交翻譯至您的 Git 儲存庫

提示

If you would rather not store translations in an external Git repository, you can skip this step and use the Upload translation files option when creating a component.

If your translations aren't already in Git:

1. Create a Git repository or use your existing project repository

2. Organize translation files following your project structure

3. Commit and push the files to your Git hosting service (GitHub, GitLab, Bitbucket, etc.)

git add locales/
git commit -m "Add translation files for Weblate migration"
git push origin main

也參考

• 持續在地化 for optimal repository structure

• 版本控制整合 for supported version control systems

匯入您的專案至 Weblate 中

建立新專案

1. 導覽至您的 Weblate 實例。

2. Click Add new translation project in the + menu.

3. Fill in your project details:

   • Project name: Your application or project name

   • URL slug: Short identifier (e.g., myapp)

   • Project website: Your project homepage (optional)

也參考

新增翻譯專案和組件 for detailed project creation instructions

Add a component from your Git repository

1. After creating the project, click Add new translation component

2. Select From version control

3. 配置您的組件：

   • Component name: e.g., "Application strings", "Website", "Documentation"

   • 儲存庫 URL： 您的 Git 儲存庫 URL （HTTPS 或 SSH）

   • Repository branch: Optional: Specify repository branch (Weblate automatically detects the default branch if not specified)

4. Weblate 將自動偵測：

   • 翻譯檔案格式

   • 可用語言

   • 來源語言

5. Review and confirm the detected settings

備註

If your repository contains a Transifex .tx/config, Weblate parses it using translation-finder and offers matching component configurations during discovery. This only covers file-related configuration, such as file masks and source files. Other project settings from the previous platform, including workflows, permissions, and language aliases, still need to be configured manually in Weblate.

Language aliases are usually not needed because Weblate already recognizes and normalizes common language-code variants while parsing translation files. See 解析語言代碼; configure 語言別名 only if your repository uses codes Weblate cannot map as intended.

提示

For repositories with multiple translation components (e.g., separate files for backend, frontend, documentation), create a separate Weblate component for each.

You can speed this up using From existing component for shared repositories or 組件探索 to automatically create them.

也參考

• 組件配置 for all configuration options

• 雙語言和單語格式 for understanding monolingual vs. bilingual formats

• 組件探索

配置您的工作流程

設定存取控制

Choose your project's visibility and access level:

1. Go to your project settings: Operations → Settings → Access tab

2. Select the appropriate access control:

   • 公開：開源專案，任何人都可以貢獻

   • Protected: Visible to all, but only invited users can translate

   • Private: Only invited users can view and translate

也參考

管理個別專案存取控制 for detailed access control configuration

設定持續在地化

啟用自動更新與提交：

1. 配置儲存庫整合：

   • Pull changes: Set up a webhook so Weblate updates when your source code changes

   • Push changes: Configure 推送 Weblate 的變更 so translations are committed back to your repository

2. Enable automatic actions in component settings:

   • Push on commit: Automatically push translations to your repository

   • Commit interval: Set how often pending translations are committed (e.g., every 24 hours)

也參考

持續在地化 for complete workflow automation

配置品質檢查與工作流程

自訂翻譯品質控制：

1. Enable checks: Review 品質檢查 and enable any opt-in quality checks you need.

2. Set up review workflow: Enable 啟用檢閱 if you want an approval process.

3. Add enforced checks: Configure which quality checks should block translations.

可選：啟用附加元件

Weblate offers 附加元件 to automate common tasks:

• 更新 PO 檔案以符合 POT (msgmerge): Automatically update PO files from POT templates

• 清理翻譯檔案: Remove unused translation strings

• 匯併 Git 提交: Squash commits before pushing to your repository

• 組件探索: Automatically discover new translation files

也參考

附加元件 for all available add-ons

測試與驗證

Before announcing the migration to your translators:

1. 測試工作流程：

   • 做個測試翻譯

   • Verify it appears in your Git repository

   • Test pulling changes from your repository into Weblate

2. Import any existing translation memory (optional):

   • Use 翻譯記憶 to import previous translations

   • This helps with consistency and speeds up translation

3. 配置通知：

   • Set up 通知 for translation events

   • Configure repository 通知掛勾 for your Git hosting service

也參考

翻譯記憶 for translation memory management

邀請與管理使用者

邀請翻譯者

For Protected and Private projects:

1. Navigate to Operations → Users in your project

2. Use Add user to invite translators

3. Assign them to appropriate teams:

   • 翻譯者: 可以翻譯字串

   • Reviewers: Can review and approve translations

   • Managers: Can manage project settings

For Public projects, users can start contributing immediately after signing up.

小訣竅

Send your translators a welcome message with:

• Link to your project on Weblate

• Overview of any project-specific terminology or style guides

• Information about your review process

也參考

• 管理個別專案存取控制 用於團隊管理

• 存取控制 for advanced permission configuration

下一步

After completing the migration:

• Announce to translators: Let your translation team know about the migration with clear instructions

• Monitor initial usage: Watch for any issues during the first few days

• Gather feedback: Ask translators about their experience compared to the previous platform

• Optimize workflow: Adjust settings based on your team's needs

• Remove previous platform: Once the migration is completed, remember to revoke access granted to the previous platform.

小訣竅

During migration, you can run both platforms in parallel for a transition period to ensure everything works as expected before fully switching over.

額外資源

• 與 Weblate 整合 - Detailed integration patterns

• 翻譯工作流程 - Different workflow configurations

• 持續在地化 - Automated continuous localization

• Weblate 的 REST API - API for automation and integrations

• 翻譯進度報告 - Setting up translation progress reports

• 常見問題 - 常見問題

提示

Join the Weblate community if you need help during your migration. The community is active and helpful!