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 seconds. All of Weblate’s dependencies are already included. PostgreSQL is set up as the default database. Hardware requirements Weblate should run on any contemporary hardware without problems, the following

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 seconds. All of Weblate’s dependencies are already included. PostgreSQL is set up as the default database. Hardware requirements Weblate should run on any contemporary hardware without problems, the following

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 seconds. All of Weblate’s dependencies are already included. PostgreSQL is set up as the default database. Hardware requirements Weblate should run on all contemporary hardware without problems, the following

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 seconds. All of Weblate’s dependencies are already included. PostgreSQL is set up as the default database. Hardware requirements Weblate should run on any contemporary hardware without problems, the following

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 seconds. All of Weblate’s dependencies are already included. PostgreSQL is set up as the default database. Hardware requirements Weblate should run on any contemporary hardware without problems, the following

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 seconds. All of Weblate’s dependencies are already included. PostgreSQL is set up as the default database. Hardware requirements Weblate should run on any contemporary hardware without problems, the following

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 seconds. All of Weblate’s dependencies are already included. PostgreSQL is set up as the default database. Hardware requirements Weblate should run on any contemporary hardware without problems, the following

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 seconds. All of Weblate’s dependencies are already included. PostgreSQL is set up as the default database. Hardware requirements Weblate should run on any contemporary hardware without problems, the following

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 example.com as the domain? Weblate uses Django’s sites framework and defines the sitename inside the database. You need to set the domain name to match your installation. See also: Set correct site domain 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

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 example.com as the domain? Weblate uses Django’s sites framework and defines the sitename inside the database. You need to set the domain name to match your installation. See also: Set correct site domain 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