Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control This is the best approach for a one-time translation using a compendium or a similar translation database. You can set up tmserver with all databases you have and let Weblate use it. This is good when you weblate user is added, you can configure Source code repository and Repository push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control This is the best approach for a one-time translation using a compendium or a similar translation database. You can set up tmserver with all databases you have and let Weblate use it. This is good when you weblate user is added, you can configure Source code repository and Repository push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control This is the best approach for a one-time translation using a compendium or a similar translation database. You can set up tmserver with all databases you have and let Weblate use it. This is good when you weblate user is added, you can configure Source code repository and Repository push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control This is the best approach for a one-time translation using a compendium or a similar translation database. You can set up tmserver with all databases you have and let Weblate use it. This is good when you weblate user is added, you can configure Source code repository and Repository push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control This is the best approach for a one-time translation using a compendium or a similar translation database. • You can set up tmserver with all databases you have and let Weblate use it. This is good when weblate user is added, you can configure Source code repository and Repository push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). 1.11. Version control integration 77 The

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control This is the best approach for a one-time translation using a compendium or a similar translation database. • You can set up tmserver with all databases you have and let Weblate use it. This is good when weblate user is added, you can configure Source code repository and Repository push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control This is the best approach for a one-time translation using a compendium or a similar translation database. • You can set up tmserver with all databases you have and let Weblate use it. This is good when weblate user is added, you can configure Source code repository and Repository push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control This is the best approach for a one-time translation using a compendium or a similar translation database. • You can set up tmserver with all databases you have and let Weblate use it. This is good when weblate user is added, you can configure Source code repository and Repository push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control This is the best approach for a one-time translation using a compendium or a similar translation database. • You can set up tmserver with all databases you have and let Weblate use it. This is good when weblate user is added, you can configure Source code repository and Repository push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control This is the best approach for a one-time translation using a compendium or a similar translation database. • You can set up tmserver with all databases you have and let Weblate use it. This is good when weblate user is added, you can configure Source code repository and Repository push URL using the SSH protocol (for example git@github.com:WeblateOrg/weblate.git). SSH repositories The most frequently used