Migrazione a 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.

Vedi anche

Prerequisites

Before starting your migration, ensure you have:

On your localization platform:

  • Accesso per esportare i tuoi file di traduzione

  • List of translators and their roles/permissions

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

Per Weblate:

Prepara i tuoi file di traduzione

Esporta traduzioni dalla tua piattaforma attuale

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

  • Transifex: utilizza il loro strumento CLI o scarica le traduzioni dall’interfaccia web

  • 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

Suggerimento

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

Invia le traduzioni al tuo repository Git

Suggerimento

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.

Se le tue traduzioni non sono già 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

Vedi anche

Importa il tuo progetto in Weblate

Crea un nuovo progetto

  1. Passa alla tua istanza 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)

../_images/user-add-project.webp

Vedi anche

Adding translation projects and components for detailed project creation instructions

Aggiungi un componente dal tuo repository Git

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

  2. Seleziona Dal controllo della versione

  3. Configura il tuo componente:

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

    • Repository URL: Your Git repository URL (HTTPS or SSH)

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

  4. Weblate will automatically detect:

    • Formato del file di traduzione

    • Lingue disponibili

    • Lingua di origine

  5. Esaminare e confermare le impostazioni rilevate

Nota

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 Parsing language codes; configure Alias lingua only if your repository uses codes Weblate cannot map as intended.

../_images/user-add-component-discovery.webp

Suggerimento

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 Scoperta dei componenti to automatically create them.

Vedi anche

Configura il tuo flusso di lavoro

Configura il controllo degli accessi

Choose your project’s visibility and access level:

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

  2. Select the appropriate access control:

    • Public: Open-source projects, anyone can contribute

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

    • Private: Only invited users can view and translate

../_images/project-access.webp

Vedi anche

Gestione controllo accessi per progetto for detailed access control configuration

Configura la localizzazione continua

Enable automatic updates and commits:

  1. Configura l’integrazione del repository:

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

    • Push changes: Configure Pushing changes from Weblate so translations are committed back to your repository

  2. Abilita le azioni automatiche nelle impostazioni del componente:

    • Push on commit: Automatically push translations to your repository

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

Vedi anche

Localizzazione continua per l’automazione completa del flusso di lavoro

Configura controlli di qualità e flussi di lavoro

Personalizza i controlli qualità della traduzione:

  1. Enable checks: Review Quality checks and enable any opt-in quality checks you need.

  2. Set up review workflow: Enable Abilita revisioni if you want an approval process.

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

Facoltativo: abilita i componenti aggiuntivi

Weblate offers Add-on to automate common tasks:

Vedi anche

Add-on for all available add-ons

Testare e verificare

Before announcing the migration to your translators:

  1. Test the workflow:

    • Fai una traduzione di prova

    • Verifica che appaia nel tuo repository Git

    • Prova a trasferire le modifiche dal tuo repository a Weblate

  2. Importa eventuali memorie di traduzione esistenti (opzionale):

    • Utilizza Memoria traduzione per importare le traduzioni precedenti

    • This helps with consistency and speeds up translation

  3. Configura notifiche:

Vedi anche

Memoria traduzione for translation memory management

Invita e gestisci gli utenti

Invita traduttori

Per progetti Protetti e Privati:

  1. Passa a Operazioni → Utenti nel tuo progetto

  2. Usa Add user per invitare i traduttori

  3. Assign them to appropriate teams:

    • Traduttori: possono tradurre stringhe

    • Revisori: possono rivedere e approvare le traduzioni

    • Managers: Can manage project settings

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

Suggerimento

Send your translators a welcome message with:

  • Link al tuo progetto su Weblate

  • Overview of any project-specific terminology or style guides

  • Informazioni sul processo di revisione

Vedi anche

Prossimi passi

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.

Suggerimento

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

Risorse aggiuntive

Suggerimento

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