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 Accessing repositories from Hosted Weblate. Weblate also stores the host key fingerprint upon first connection, and fails to connect to the host should it be changed later (see Verifying SSH host keys). In

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 Accessing repositories from Hosted Weblate. Weblate also stores the host key fingerprint upon first connection, and fails to connect to the host should it be changed later (see Verifying SSH host keys). In

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 Accessing repositories from Hosted Weblate. Weblate also stores the host key fingerprint upon first connection, and fails to connect to the host should it be changed later (see Verifying SSH host keys). In

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 Accessing repositories from Hosted Weblate. Weblate also stores the host key fingerprint upon first connection, and fails to connect to the host should it be changed later (see Verifying SSH host keys). In

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 Accessing repositories from Hosted Weblate. Weblate also stores the host key fingerprint upon first connection, and fails to connect to the host should it be changed later (see Verifying SSH host keys). In

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 Accessing repositories from Hosted Weblate. Weblate also stores the host key fingerprint upon first connection, and fails to connect to the host should it be changed later (see Verifying SSH host keys). In

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 Accessing repositories from Hosted Weblate. Weblate also stores the host key fingerprint upon first connection, and fails to connect to the host should it be changed later (see Verifying SSH host keys). In

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 Accessing repositories from Hosted Weblate. Weblate also stores the host key fingerprint upon first connection, and fails to connect to the host should it be changed later (see Verifying SSH host keys). In

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 Accessing repositories from Hosted Weblate. Weblate also stores the host key fingerprint upon first connection, and fails to connect to the host should it be changed later (see Verifying SSH host keys). In

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 Accessing repositories from Hosted Weblate. Weblate also stores the host key fingerprint upon first connection, and fails to connect to the host should it be changed later (see Verifying SSH host keys). In