Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control formats are suitable for embedding into existing documentation, while JSON is useful for further processing of the data. Translator credits Generates document usable for crediting translators - sorted permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control formats are suitable for embedding into existing documentation, while JSON is useful for further processing of the data. Translator credits Generates document usable for crediting translators - sorted permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control formats are suitable for embedding into existing documentation, while JSON is useful for further processing of the data. Translator credits Generates a document usable for crediting translators - sorted permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control formats are suitable for embedding into existing documentation, while JSON is useful for further processing of the data. Translator credits Generates document usable for crediting translators - sorted permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control formats are suitable for embedding into existing documentation, while JSON is useful for further processing of the data. Translator credits Generates document usable for crediting translators - sorted permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control formats are suitable for embedding into existing documentation, while JSON is useful for further processing of the data. Translator credits Generates a document usable for crediting translators - sorted permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control formats are suitable for embedding into existing documentation, while JSON is useful for further processing of the data. Translator credits Generates a document usable for crediting translators - sorted permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in the underlaying version control formats are suitable for embedding into existing documentation, while JSON is useful for further processing of the data. Translator credits Generates a document usable for crediting translators - sorted permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control formats are suitable for embedding into existing documentation, while JSON is useful for further processing of the data. Translator credits Generates document usable for crediting translators - sorted permissions Creating database for Weblate Creating database in PostgreSQL Creating database in MySQL Other configurations Outgoing mail Setting up hub Installation Filling up the database Production setup

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control formats are suitable for embedding into existing documentation, while JSON is useful for further processing of the data. Translator credits Generates document usable for crediting translators - sorted permissions Creating database for Weblate Creating database in PostgreSQL Creating database in MySQL Other configurations Outgoing mail Setting up hub Installation Filling up the database Production setup