設定¶
すべての設定は settings.py
に保存されます(Django の通常の方法)。
注釈
これらの設定の変更後、Weblate(WSGI プロセスと Celery プロセスの両方)の再起動が必要です。
mod_wsgi として実行する場合は、Apache を再起動して設定のリロードが必要です。
参考
Django 本体の設定パラメーターについては、 Django's documentation も確認してください。
AUTH_LOCK_ATTEMPTS¶
バージョン 2.14 で追加.
レート制限を適用する前に失敗した認証試行の最大回数。
現在、以下の場所に適用しています:
ログイン。アカウント パスワードを削除し、ユーザーが新しいパスワードを要求しなければサインインできないようにしています。
Password resets. Prevents new e-mails from being sent, avoiding spamming users with too many password reset attempts.
Defaults to 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"
alsoFalse
Only update remotes.
"full"
alsoTrue
Update remotes and merge working copy.
注釈
This requires that Background tasks using 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¶
翻訳に対して実行する品質検査のリストです。
注釈
check インタフェースを実装する Python クラスへの完全修飾パスを指定します。
検査するリストを調整して、関連する検査を含めます。
デフォルトでは、すべての内蔵の 品質検査 が有効なっているので、ここで設定を変更できます。デフォルトでは、サンプル設定 でコメント化されているため、デフォルト値が使用されます。その後は、Weblate の新しいバージョンのリリースのたびに新しい検査が行われます。
すべての検査を無効にする:
CHECK_LIST = ()
指定する項目だけ有効にする:
CHECK_LIST = (
'weblate.checks.chars.BeginNewlineCheck',
'weblate.checks.chars.EndNewlineCheck',
'weblate.checks.chars.MaxLengthCheck',
)
注釈
この設定を変更すると、新しく変更した翻訳のみ検査されて、過去の検査結果は引き続きデータベースに保存されたままです。保存されている翻訳にも、新しい検査を適用するには、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 Dumped data for backups 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
Defaults to $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
Public
1
Protected
100
Private
200
Custom
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 Component configuration 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_TRANSLATION_PROPAGATION¶
バージョン 2.5 で追加.
Default setting for translation propagation, defaults to 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.
GITLAB_CREDENTIALS¶
バージョン 4.3 で追加.
List for credentials for GitLab servers.
ヒント
Use this in case you want Weblate to interact with more of them, for single
GitLab endpoint stick with GITLAB_USERNAME
and GITLAB_TOKEN
.
GITLAB_CREDENTIALS = {
"gitlab.com": {
"username": "weblate",
"token": "your-api-token",
},
"gitlab.example.com": {
"username": "weblate",
"token": "another-api-token",
},
}
GITLAB_USERNAME¶
GitLab username used to send merge requests for translation updates.
GITHUB_CREDENTIALS¶
バージョン 4.3 で追加.
List for credentials for GitHub servers.
ヒント
Use this in case you want Weblate to interact with more of them, for single
GitHub endpoint stick with GITHUB_USERNAME
and GITHUB_TOKEN
.
GITHUB_CREDENTIALS = {
"api.github.com": {
"username": "weblate",
"token": "your-api-token",
},
"github.example.com": {
"username": "weblate",
"token": "another-api-token",
},
}
GITHUB_USERNAME¶
GitHub username used to send pull requests for translation updates.
GITHUB_TOKEN¶
バージョン 4.3 で追加.
GitHub personal access token used to make API calls to send pull requests for translation updates.
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.
Defaults to 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.
Defaults to 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.
For example:
LICENSE_EXTRA = [
(
"AGPL-3.0",
"GNU Affero General Public License v3.0",
"https://www.gnu.org/licenses/agpl-3.0-standalone.html",
),
]
LICENSE_FILTER¶
バージョン 4.3 で変更: Setting this to blank value now disables license alert.
Filter list of licenses to show. This also disables the license alert when set to empty.
注釈
This filter uses the short license names.
For example:
LICENSE_FILTER = {"AGPL-3.0", "GPL-3.0-or-later"}
Following disables the license alert:
LICENSE_FILTER = set()
LICENSE_REQUIRED¶
Defines whether the license attribute in Component configuration 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.
注釈
Defaults to True
.
LOCALIZE_CDN_URL and LOCALIZE_CDN_PATH¶
These settings configure the JavaScript 現地語化 CDN 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.
For example:
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 機械翻訳 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¶
Google Cloud API v3 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 App 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 the "Authenticating with a Multi-service resource" section.
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://yandex.com/dev/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.
Defaults to 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. This only limits new registrations, users can still authenticate and add authentication using all configured authentication backends.
It is recommended to keep REGISTRATION_OPEN
enabled while limiting
registration backends, otherwise users will be able to register, but Weblate
will not show links to register in the user interface.
例:
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 authentication, 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.
REQUIRE_LOGIN¶
バージョン 4.1 で追加.
This enables LOGIN_REQUIRED_URLS
and configures REST framework to
require login for all API endpoints.
注釈
This is in implemented in the サンプル設定. For Docker, use
WEBLATE_REQUIRE_LOGIN
.
SESSION_COOKIE_AGE_AUTHENTICATED¶
バージョン 4.3 で追加.
Set session expiry for authenticated users. This complements
SESSION_COOKIE_AGE
which is used for unauthenticated users.
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.
Examples:
# 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.