Конфигурация¶
All settings are stored in settings.py
(as is usual for Django).
Примечание
After changing any of these settings, you need to restart Weblate - both WSGI and Celery processes.
In case it is run as mod_wsgi, you need to restart Apache to reload the configuration.
См.также
Please also check Django’s documentation for parameters configuring Django itself.
AUDITLOG_EXPIRY¶
Добавлено в версии 3.6.
How many days Weblate should keep audit logs, which contain info about account activity.
По умолчанию установлен в 180 дней.
AUTH_LOCK_ATTEMPTS¶
Добавлено в версии 2.14.
Maximum number of failed authentication attempts before rate limiting is applied.
This is currently applied in the following locations:
Logins. Deletes the account password, preventing the user from signing in without requesting a new password.
Password resets. Prevents new e-mails from being sent, avoiding spamming users with too many password reset attempts.
По умолчанию установлен в 10.
См.также
AUTO_UPDATE¶
Добавлено в версии 3.2.
Изменено в версии 3.11: The original on/off option was changed to differentiate which strings are accepted.
Updates all repositories on a daily basis.
Подсказка
Useful if you are not using Обработчики уведомлений to update Weblate repositories automatically.
Примечание
On/off options exist in addition to string selection for backward compatibility.
Options are:
"none"
No daily updates.
"remote"
илиFalse
Only update remotes.
"full"
илиTrue
Update remotes and merge working copy.
Примечание
This requires that Фоновые задачи с использованием Celery is working, and will take effect after it is restarted.
AVATAR_URL_PREFIX¶
Prefix for constructing avatar URLs as:
${AVATAR_URL_PREFIX}/avatar/${MAIL_HASH}?${PARAMS}
.
The following services are known to work:
- Gravatar (default), as per https://gravatar.com/
AVATAR_URL_PREFIX = 'https://www.gravatar.com/'
- Libravatar, as per https://www.libravatar.org/
AVATAR_URL_PREFIX = 'https://www.libravatar.org/'
См.также
AUTH_TOKEN_VALID¶
Добавлено в версии 2.14.
How long the authentication token and temporary password from password reset e-mails is valid for. Set in number of seconds, defaulting to 172800 (2 days).
AUTH_PASSWORD_DAYS¶
Добавлено в версии 2.15.
How many days using the same password should be allowed.
Примечание
Password changes made prior to Weblate 2.15 will not be accounted for in this policy.
По умолчанию установлен в 180 дней.
AUTOFIX_LIST¶
List of automatic fixes to apply when saving a string.
Примечание
Provide a fully-qualified path to the Python class that implementing the autofixer interface.
Available fixes:
weblate.trans.autofixes.whitespace.SameBookendingWhitespace
Matches whitespace at the start and end of the string to the source.
weblate.trans.autofixes.chars.ReplaceTrailingDotsWithEllipsis
Replaces trailing dots (…) if the source string has ellipsis (…).
weblate.trans.autofixes.chars.RemoveZeroSpace
Removes zero-width space characters if the source does not contain any.
weblate.trans.autofixes.chars.RemoveControlChars
Removes control characters if the source does not contain any.
weblate.trans.autofixes.html.BleachHTML
Removes unsafe HTML markup from strings flagged as
safe-html
(see Небезопасный HTML-код).
You can select which ones to use:
AUTOFIX_LIST = (
'weblate.trans.autofixes.whitespace.SameBookendingWhitespace',
'weblate.trans.autofixes.chars.ReplaceTrailingDotsWithEllipsis',
)
BASE_DIR¶
Base directory where Weblate sources are located. Used to derive several other paths by default:
Default value: Top level directory of Weblate sources.
CSP_SCRIPT_SRC, CSP_IMG_SRC, CSP_CONNECT_SRC, CSP_STYLE_SRC, CSP_FONT_SRC¶
Customize Content-Security-Policy
header for Weblate. The header is
automatically generated based on enabled integrations with third-party services
(Matomo, Google Analytics, Sentry, …).
All these default to empty list.
** Пример:: **
# Enable Cloudflare Javascript optimizations
CSP_SCRIPT_SRC = ["ajax.cloudflare.com"]
CHECK_LIST¶
List of quality checks to perform on a translation.
Примечание
Provide a fully-qualified path to the Python class implementing the check interface.
Adjust the list of checks to include ones relevant to you.
All built-in Проверки качества are turned on by default, from where you can change these settings. By default they are commented out in Пример конфигурации so that default values are used. New checks then carried out for each new Weblate version.
You can turn off all checks:
CHECK_LIST = ()
You can turn on only a few:
CHECK_LIST = (
'weblate.checks.chars.BeginNewlineCheck',
'weblate.checks.chars.EndNewlineCheck',
'weblate.checks.chars.MaxLengthCheck',
)
Примечание
Changing this setting only affects newly changed translations, existing checks
will still be stored in the database. To also apply changes to the stored translations, run
updatechecks
.
См.также
COMMENT_CLEANUP_DAYS¶
Добавлено в версии 3.6.
Delete comments after a given number of days.
Defaults to None
, meaning no deletion at all.
COMMIT_PENDING_HOURS¶
Добавлено в версии 2.10.
Number of hours between committing pending changes by way of the background task.
DATA_DIR¶
The folder Weblate stores all data in. It contains links to VCS repositories, a fulltext index and various configuration files for external tools.
The following subdirectories usually exist:
home
Home directory used for invoking scripts.
ssh
SSH keys and configuration.
static
Default location for static Django files, specified by
STATIC_ROOT
.media
Default location for Django media files, specified by
MEDIA_ROOT
.vcs
Version control repositories.
backups
Daily backup data, please check Дампы данных для резервного копирования for details.
Примечание
This directory has to be writable by Weblate. Running it as uWSGI means
the www-data
user should have write access to it.
The easiest way to achieve this is to make the user the owner of the directory:
sudo chown www-data:www-data -R $DATA_DIR
По умолчанию установлен в $BASE_DIR/data
.
DATABASE_BACKUP¶
Добавлено в версии 3.1.
Whether the database backups should be stored as plain text, compressed or skipped. The authorized values are:
"plain"
"compressed"
"none"
DEFAULT_ACCESS_CONTROL¶
Добавлено в версии 3.3.
The default access control setting for new projects:
0
Публичный
1
Защищённый
100
Частный
200
Настраиваемый
Use Custom if you are managing ACL manually, which means not relying on the internal Weblate management.
DEFAULT_ADD_MESSAGE, DEFAULT_ADDON_MESSAGE, DEFAULT_COMMIT_MESSAGE, DEFAULT_DELETE_MESSAGE, DEFAULT_MERGE_MESSAGE¶
Default commit messages for different operations, please check Конфигурация компонента for details.
DEFAULT_ADDONS¶
Default addons to install on every created component.
Примечание
This setting affects only newly created components.
Пример:
DEFAULT_ADDONS = {
# Addon with no parameters
"weblate.flags.target_edit": {},
# Addon with parameters
"weblate.autotranslate.autotranslate": {
"mode": "suggest",
"filter_type": "todo",
"auto_source": "mt",
"component": "",
"engines": ["weblate-translation-memory"],
"threshold": "80",
}
}
См.также
DEFAULT_COMMITER_EMAIL¶
Добавлено в версии 2.4.
Committer e-mail address for created translation components defaulting to noreply@weblate.org
.
DEFAULT_COMMITER_NAME¶
Добавлено в версии 2.4.
Committer name for created translation components defaulting to Weblate
.
DEFAULT_MERGE_STYLE¶
Добавлено в версии 3.4.
Merge style for any new components.
rebase - default
merge
См.также
DEFAULT_TRANSLATION_PROPAGATION¶
Добавлено в версии 2.5.
Значение по умолчанию для настройки распространения перевода, по умолчанию установлена в True
.
DEFAULT_PULL_MESSAGE¶
Title for new pull requests,
defaulting to 'Update from Weblate'
.
ENABLE_AVATARS¶
Whether to turn on Gravatar-based avatars for users. By default this is on.
Avatars are fetched and cached on the server, lowering the risk of leaking private info, speeding up the user experience.
См.также
ENABLE_HTTPS¶
Whether to send links to Weblate as HTTPS or HTTP. This setting affects sent e-mails and generated absolute URLs.
Подсказка
In the default configuration this is also used for several Django settings related to HTTPS.
ENABLE_SHARING¶
Turn on/off the Share menu so users can share translation progress on social networks.
GOOGLE_ANALYTICS_ID¶
Google Analytics ID to turn on monitoring of Weblate using Google Analytics.
HIDE_REPO_CREDENTIALS¶
Hide repository credentials from appearing in the web interface. In case you have repository URL with user and password, Weblate will hide it when related info is shown to users.
For example instead of https://user:password@git.example.com/repo.git
it
will show just https://git.example.com/repo.git
. It tries to clean up VCS
error messages too in a similar manner.
Примечание
This is turned on by default.
IP_BEHIND_REVERSE_PROXY¶
Добавлено в версии 2.14.
Indicates whether Weblate is running behind a reverse proxy.
If set to True
, Weblate gets IP address from a header defined by
IP_PROXY_HEADER
.
Предупреждение
Ensure you are actually using a reverse proxy and that it sets this header, otherwise users will be able to fake the IP address.
Примечание
This is not on by default.
IP_PROXY_HEADER¶
Добавлено в версии 2.14.
Indicates which header Weblate should obtain the IP address from when
IP_BEHIND_REVERSE_PROXY
is turned on.
По умолчанию установлен в HTTP_X_FORWARDED_FOR
.
IP_PROXY_OFFSET¶
Добавлено в версии 2.14.
Indicates which part of IP_PROXY_HEADER
is used as client IP
address.
Depending on your setup, this header might consist of several IP addresses,
(for example X-Forwarded-For: a, b, client-ip
) and you can configure
which address from the header is used as client IP address here.
Предупреждение
Setting this affects the security of your installation, you should only configure it to use trusted proxies for determining IP address.
По умолчанию установлен в 0.
LEGAL_URL¶
Добавлено в версии 3.5.
URL where your Weblate instance shows its legal documents.
Подсказка
Useful if you host your legal documents outside Weblate for embedding them inside Weblate, please check Право for details.
Пример:
LEGAL_URL = "https://weblate.org/terms/"
LICENSE_EXTRA¶
Additional licenses to include in the license choices.
Примечание
Each license definition should be tuple of its short name, a long name and an URL.
Например:
LICENSE_EXTRA = [
(
"AGPL-3.0",
"GNU Affero General Public License v3.0",
"https://www.gnu.org/licenses/agpl-3.0-standalone.html",
),
]
LICENSE_FILTER¶
Optional addition of licenses to show.
Примечание
This filter uses the short license names.
Например:
LICENSE_FILTER = {"AGPL-3.0", "GPL-3.0-or-later"}
LICENSE_REQUIRED¶
Defines whether the license attribute in Конфигурация компонента is required.
Примечание
This is off by default.
LIMIT_TRANSLATION_LENGTH_BY_SOURCE_LENGTH¶
Whether the length of a given translation should be limited. The restriction is the length of the source string * 10 characters.
Подсказка
Set this to False
to allow longer translations (up to 10.000 characters) irrespective of source string length.
Примечание
По умолчанию установлен в True
.
LOCALIZE_CDN_URL and LOCALIZE_CDN_PATH¶
These settings configure the CDN локализации JavaScript’а addon.
LOCALIZE_CDN_URL
defines root URL where the localization CDN is
available and LOCALIZE_CDN_PATH
defines path where Weblate should
store generated files which will be served at the LOCALIZE_CDN_URL
.
Подсказка
On Hosted Weblate, this uses https://weblate-cdn.com/
.
См.также
LOGIN_REQUIRED_URLS¶
A list of URLs you want to require logging into. (Besides the standard rules built into Weblate).
Подсказка
This allows you to password protect a whole installation using:
LOGIN_REQUIRED_URLS = (
r'/(.*)$',
)
REST_FRAMEWORK["DEFAULT_PERMISSION_CLASSES"] = [
"rest_framework.permissions.IsAuthenticated"
]
Подсказка
It is desirable to lock down API access as well, as shown in the above example.
LOGIN_REQUIRED_URLS_EXCEPTIONS¶
List of exceptions for LOGIN_REQUIRED_URLS
.
If not specified, users are allowed to access the login page.
Some of exceptions you might want to include:
LOGIN_REQUIRED_URLS_EXCEPTIONS = (
r'/accounts/(.*)$', # Required for login
r'/static/(.*)$', # Required for development mode
r'/widgets/(.*)$', # Allowing public access to widgets
r'/data/(.*)$', # Allowing public access to data exports
r'/hooks/(.*)$', # Allowing public access to notification hooks
r'/api/(.*)$', # Allowing access to API
r'/js/i18n/$', # JavaScript localization
)
MATOMO_SITE_ID¶
ID of a site in Matomo (formerly Piwik) you want to track.
Примечание
This integration does not support the Matomo Tag Manager.
См.также
MATOMO_URL¶
Full URL (including trailing slash) of a Matomo (formerly Piwik) installation you want to use to track Weblate use. Please check <https://matomo.org/> for more details.
Подсказка
This integration does not support the Matomo Tag Manager.
Например:
MATOMO_SITE_ID = 1
MATOMO_URL = "https://example.matomo.cloud/"
См.также
MT_SERVICES¶
Изменено в версии 3.0: The setting was renamed from MACHINE_TRANSLATION_SERVICES
to
MT_SERVICES
to be consistent with other machine translation settings.
List of enabled machine translation services to use.
Примечание
Many of the services need additional configuration like API keys, please check their documentation ref: machine for more details.
MT_SERVICES = (
'weblate.machinery.apertium.ApertiumAPYTranslation',
'weblate.machinery.deepl.DeepLTranslation',
'weblate.machinery.glosbe.GlosbeTranslation',
'weblate.machinery.google.GoogleTranslation',
'weblate.machinery.microsoft.MicrosoftCognitiveTranslation',
'weblate.machinery.microsoftterminology.MicrosoftTerminologyService',
'weblate.machinery.mymemory.MyMemoryTranslation',
'weblate.machinery.tmserver.AmagamaTranslation',
'weblate.machinery.tmserver.TMServerTranslation',
'weblate.machinery.yandex.YandexTranslation',
'weblate.machinery.weblatetm.WeblateTranslation',
'weblate.machinery.saptranslationhub.SAPTranslationHub',
'weblate.memory.machine.WeblateMemory',
)
См.также
MT_APERTIUM_APY¶
URL of the Apertium-APy server, https://wiki.apertium.org/wiki/Apertium-apy
См.также
MT_BAIDU_ID¶
Client ID for the Baidu Zhiyun API, you can register at https://api.fanyi.baidu.com/api/trans/product/index
MT_BAIDU_SECRET¶
Client secret for the Baidu Zhiyun API, you can register at https://api.fanyi.baidu.com/api/trans/product/index
MT_DEEPL_API_VERSION¶
Добавлено в версии 4.1.1.
API version to use with DeepL service. The version limits scope of usage:
- v1
Is meant for CAT tools and is usable with user-based subscription.
- v2
Is meant for API usage and the subscription is usage based.
Previously Weblate was classified as a CAT tool by DeepL, so it was supposed to use the v1 API, but now is supposed to use the v2 API. Therefore it defaults to v2, and you can change it to v1 in case you have an existing CAT subscription and want Weblate to use that.
См.также
MT_DEEPL_KEY¶
API key for the DeepL API, you can register at https://www.deepl.com/pro.html
См.также
MT_GOOGLE_KEY¶
API key for Google Translate API v2, you can register at https://cloud.google.com/translate/docs
См.также
MT_GOOGLE_CREDENTIALS¶
API v3 JSON credentials file obtained in the Google cloud console. Please provide a full OS path. Credentials are per service-account affiliated with certain project. Please check https://cloud.google.com/docs/authentication/getting-started for more details.
MT_GOOGLE_PROJECT¶
API v3 Google cloud project id with activated translation service and billing activated. Please check https://cloud.google.com/appengine/docs/standard/nodejs/building-app/creating-project for more details
MT_GOOGLE_LOCATION¶
API v3 Google Cloud Application Engine may be specific to a location.
Change accordingly if the default global
fallback does not work for you.
Please check https://cloud.google.com/appengine/docs/locations for more details
MT_MICROSOFT_BASE_URL¶
Region base URL domain as defined in the «Base URLs» section.
Defaults to api.cognitive.microsofttranslator.com
for Azure Global.
For Azure China, please use api.translator.azure.cn
.
MT_MICROSOFT_COGNITIVE_KEY¶
Client key for the Microsoft Cognitive Services Translator API.
MT_MICROSOFT_REGION¶
Region prefix as defined in «Multi service subscription».
MT_MICROSOFT_ENDPOINT_URL¶
Region endpoint URL domain for access token as defined in the «Authenticating with an access token» section.
Defaults to api.cognitive.microsoft.com
for Azure Global.
For Azure China, please use your endpoint from the Azure Portal.
MT_MODERNMT_URL¶
URL of ModernMT. It defaults to https://api.modernmt.com/
for the cloud
service.
См.также
MT_MYMEMORY_EMAIL¶
MyMemory identification e-mail address. It permits 1000 requests per day.
MT_MYMEMORY_KEY¶
MyMemory access key for private translation memory, use it with MT_MYMEMORY_USER
.
MT_MYMEMORY_USER¶
MyMemory user ID for private translation memory, use it with MT_MYMEMORY_KEY
.
MT_NETEASE_KEY¶
App key for NetEase Sight API, you can register at https://sight.netease.com/
MT_NETEASE_SECRET¶
App secret for the NetEase Sight API, you can register at https://sight.netease.com/
MT_YANDEX_KEY¶
API key for the Yandex Translate API, you can register at https://tech.yandex.com/translate/
См.также
MT_YOUDAO_ID¶
Client ID for the Youdao Zhiyun API, you can register at https://ai.youdao.com/product-fanyi-text.s.
MT_YOUDAO_SECRET¶
Client secret for the Youdao Zhiyun API, you can register at https://ai.youdao.com/product-fanyi-text.s.
MT_SAP_USE_MT¶
Whether to also use machine translation services, in addition to the term database.
Possible values: True
or False
См.также
NEARBY_MESSAGES¶
How many strings to show around the currently translated string. This is just a default value, users can adjust this in Профиль пользователя.
RATELIMIT_ATTEMPTS¶
Добавлено в версии 3.2.
Maximum number of authentication attempts before rate limiting is applied.
По умолчанию установлен в 5.
RATELIMIT_WINDOW¶
Добавлено в версии 3.2.
How long authentication is accepted after rate limiting applies.
An amount of seconds defaulting to 300 (5 minutes).
RATELIMIT_LOCKOUT¶
Добавлено в версии 3.2.
How long authentication is locked after rate limiting applies.
An amount of seconds defaulting to 600 (10 minutes).
REGISTRATION_ALLOW_BACKENDS¶
Добавлено в версии 4.1.
List of authentication backends to allow registration from in case it is otherwise disabled by
REGISTRATION_OPEN
.
Пример:
REGISTRATION_ALLOW_BACKENDS = ["azuread-oauth2", "azuread-tenant-oauth2"]
Подсказка
The backend names match names used in URL for authentication.
См.также
REGISTRATION_CAPTCHA¶
A value of either True
or False
indicating whether registration of new
accounts is protected by CAPTCHA. This setting is optional, and a default of
True
will be assumed if it is not supplied.
If turned on, a CAPTCHA is added to all pages where a users enters their e-mail address:
New account registration.
Password recovery.
Adding e-mail to an account.
Contact form for users that are not signed in.
REGISTRATION_EMAIL_MATCH¶
Добавлено в версии 2.17.
Allows you to filter which e-mail addresses can register.
Defaults to .*
, which allows any e-mail address to be registered.
You can use it to restrict registration to a single e-mail domain:
REGISTRATION_EMAIL_MATCH = r'^.*@weblate\.org$'
REGISTRATION_OPEN¶
Whether registration of new accounts is currently permitted.
This optional setting can remain the default True
, or changed to False
.
This setting affects built-in authentication by e-mail address or through the
Python Social Auth (you can whitelist certain back-ends using
REGISTRATION_ALLOW_BACKENDS
).
Примечание
If using third-party authentication methods such as Аутентификация через LDAP, it just hides the registration form, but new users might still be able to sign in and create accounts.
REPOSITORY_ALERT_THRESHOLD¶
Добавлено в версии 4.0.2.
Threshold for triggering an alert for outdated repositories, or ones that contain too many changes. Defaults to 25.
См.также
SIMPLIFY_LANGUAGES¶
Use simple language codes for default language/country combinations. For
example an fr_FR
translation will use the fr
language code. This is usually
the desired behavior, as it simplifies listing languages for these default
combinations.
Turn this off if you want to different translations for each variant.
SITE_DOMAIN¶
Configures site domain. This is necessary to produce correct absolute links in many scopes (for example activation e-mails, notifications or RSS feeds).
In case Weblate is running on non-standard port, include it here as well.
Примеры:
# Production site with domain name
SITE_DOMAIN = "weblate.example.com"
# Local development with IP address and port
SITE_DOMAIN = "127.0.0.1:8000"
Примечание
This setting should only contain the domain name. For configuring protocol,
(enabling and enforcing HTTPS) use ENABLE_HTTPS
and for changing
URL, use URL_PREFIX
.
Подсказка
On a Docker container, the site domain is configured through
WEBLATE_ALLOWED_HOSTS
.
SITE_TITLE¶
Site title to be used for the website and sent e-mails.
SPECIAL_CHARS¶
Additional characters to include in the visual keyboard, Визуальная клавиатура.
The default value is:
SPECIAL_CHARS = ('\t', '\n', '…')
SINGLE_PROJECT¶
Добавлено в версии 3.8.
Redirects users directly to a project or component instead of showing
the dashboard. You can either set it to True
and in this case it only works in
case there is actually only single project in Weblate. Alternatively set
the project slug, and it will redirect unconditionally to this project.
Изменено в версии 3.11: The setting now also accepts a project slug, to force displaying that single project.
Пример:
SINGLE_PROJECT = "test"
STATUS_URL¶
The URL where your Weblate instance reports its status.
SUGGESTION_CLEANUP_DAYS¶
Добавлено в версии 3.2.1.
Automatically deletes suggestions after a given number of days.
Defaults to None
, meaning no deletions.
URL_PREFIX¶
This setting allows you to run Weblate under some path (otherwise it relies on being run from the webserver root).
Примечание
To use this setting, you also need to configure your server to strip this prefix.
For example with WSGI, this can be achieved by setting WSGIScriptAlias
.
Подсказка
The prefix should start with a /
.
Пример:
URL_PREFIX = '/translations'
Примечание
This setting does not work with Django’s built-in server, you would have to
adjust urls.py
to contain this prefix.
VCS_BACKENDS¶
Configuration of available VCS backends.
Примечание
Weblate tries to use all supported back-ends you have the tools for.
Подсказка
You can limit choices or add custom VCS back-ends by using this.
VCS_BACKENDS = (
'weblate.vcs.git.GitRepository',
)
VCS_CLONE_DEPTH¶
Добавлено в версии 3.10.2.
Configures how deep cloning of repositories Weblate should do.
Примечание
Currently this is only supported in Git. By default Weblate does shallow clones of the repositories to make cloning faster and save disk space. Depending on your usage (for example when using custom Надстройки), you might want to increase the depth or turn off shallow clones completely by setting this to 0.
Подсказка
In case you get fatal: protocol error: expected old/new/ref, got 'shallow
<commit hash>'
error when pushing from Weblate, turn off shallow clones completely by setting:
VCS_CLONE_DEPTH = 0
WEBLATE_ADDONS¶
List of addons available for use. To use them, they have to be enabled for a given translation component. By default this includes all built-in addons, when extending the list you will probably want to keep existing ones enabled, for example:
WEBLATE_ADDONS = (
# Built-in addons
"weblate.addons.gettext.GenerateMoAddon",
"weblate.addons.gettext.UpdateLinguasAddon",
"weblate.addons.gettext.UpdateConfigureAddon",
"weblate.addons.gettext.MsgmergeAddon",
"weblate.addons.gettext.GettextCustomizeAddon",
"weblate.addons.gettext.GettextAuthorComments",
"weblate.addons.cleanup.CleanupAddon",
"weblate.addons.consistency.LangaugeConsistencyAddon",
"weblate.addons.discovery.DiscoveryAddon",
"weblate.addons.flags.SourceEditAddon",
"weblate.addons.flags.TargetEditAddon",
"weblate.addons.flags.SameEditAddon",
"weblate.addons.flags.BulkEditAddon",
"weblate.addons.generate.GenerateFileAddon",
"weblate.addons.json.JSONCustomizeAddon",
"weblate.addons.properties.PropertiesSortAddon",
"weblate.addons.git.GitSquashAddon",
"weblate.addons.removal.RemoveComments",
"weblate.addons.removal.RemoveSuggestions",
"weblate.addons.resx.ResxUpdateAddon",
"weblate.addons.autotranslate.AutoTranslateAddon",
"weblate.addons.yaml.YAMLCustomizeAddon",
"weblate.addons.cdn.CDNJSAddon",
# Addon you want to include
"weblate.addons.example.ExampleAddon",
)
См.также
WEBLATE_EXPORTERS¶
Добавлено в версии 4.2.
List of a available exporters offering downloading translations or glossaries in various file formats.
См.также
WEBLATE_FORMATS¶
Добавлено в версии 3.0.
List of file formats available for use.
Примечание
The default list already has the common formats.
См.также
WEBLATE_GPG_IDENTITY¶
Добавлено в версии 3.1.
Identity used by Weblate to sign Git commits, for example:
WEBLATE_GPG_IDENTITY = 'Weblate <weblate@example.com>'
The Weblate GPG keyring is searched for a matching key (home/.gnupg
under
DATA_DIR
). If not found, a key is generated, please check
Signing Git commits with GnuPG for more details.
См.также