Imported Translations from Zanata
For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: Iebcfa847fbacdedb6d9cf1acd17188f7beb12952
This commit is contained in:
13 changed files with 88 additions and 50 deletions
@@ -1,20 +1,39 @@
# Andi Chandler <andi@gowling.com>, 2017. #zanata
# Andi Chandler <andi@gowling.com>, 2018. #zanata
# Andi Chandler <andi@gowling.com>, 2020. #zanata
msgid ""
msgstr ""
"Project-Id-Version: swift\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-08-09 00:11+0000\n"
"POT-Creation-Date: 2020-04-10 11:59+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-08-08 10:00+0000\n"
"PO-Revision-Date: 2020-04-07 08:39+0000\n"
"Last-Translator: Andi Chandler <andi@gowling.com>\n"
"Language-Team: English (United Kingdom)\n"
"Language: en_GB\n"
"X-Generator: Zanata 4.3.3\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
msgid ""
"**Dependency update**: ``eventlet`` must be at least 0.25.0. This also "
"dragged forward minimum-supported versions of ``dnspython``(1.15.0), "
"``greenlet``(0.3.2), and ``six``(1.10.0)."
msgstr ""
"**Dependency update**: ``eventlet`` must be at least 0.25.0. This also "
"dragged forward minimum-supported versions of ``dnspython``(1.15.0), "
"``greenlet``(0.3.2), and ``six``(1.10.0)."
msgid ""
"**Dependency updates**: we've increased our minimum supported version of "
"``cryptography`` to 2.0.2 and ``netifaces`` to 0.8. This is largely due to "
"the difficulty of continuing to test with the old versions."
msgstr ""
"**Dependency updates**: we've increased our minimum supported version of "
"``cryptography`` to 2.0.2 and ``netifaces`` to 0.8. This is largely due to "
"the difficulty of continuing to test with the old versions."
msgid "2.10.0"
msgstr "2.10.0"
@@ -36,6 +55,9 @@ msgstr "2.13.0"
msgid "2.13.1"
msgstr "2.13.1"
msgid "2.13.1-12"
msgstr "2.13.1-12"
msgid "2.14.0"
msgstr "2.14.0"
@@ -45,15 +67,24 @@ msgstr "2.15.0"
msgid "2.15.1"
msgstr "2.15.1"
msgid "2.15.2"
msgstr "2.15.2"
msgid "2.16.0"
msgstr "2.16.0"
msgid "2.17.0"
msgstr "2.17.0"
msgid "2.17.1"
msgstr "2.17.1"
msgid "2.18.0"
msgstr "2.18.0"
msgid "2.19.0"
msgstr "2.19.0"
msgid ""
"A PUT or POST to a container will now update the container's Last-Modified "
"time, and that value will be included in a GET/HEAD response."
@@ -1160,6 +1191,13 @@ msgstr ""
"path mangling, operators should set ``mangle_client_paths`` to \"True\" "
"before upgrading."
msgid ""
"The container-updater now reports zero objects and bytes used for child DBs "
"in sharded containers. This prevents double-counting in utilization reports."
msgstr ""
"The container-updater now reports zero objects and bytes used for child DBs "
"in sharded containers. This prevents double-counting in utilisation reports."
msgid ""
"The default for `object_post_as_copy` has been changed to False. The option "
"is now deprecated and will be removed in a future release. If your cluster "
@@ -1175,6 +1213,13 @@ msgstr ""
"copy, and future features will not be supported under post-as-copy. (\"Fast-"
"post\" is where `object_post_as_copy` is false)."
msgid ""
"The default location is now set to \"us-east-1\". This is more likely to be "
"the default region that a client will try when using v4 signatures."
msgstr ""
"The default location is now set to \"us-east-1\". This is more likely to be "
"the default region that a client will try when using v4 signatures."
msgid ""
"The erasure code reconstructor `handoffs_first` option has been deprecated "
"in favor of `handoffs_only`. `handoffs_only` is far more useful, and just "
@@ -1261,6 +1306,19 @@ msgstr ""
"thousands of greenthreads, all deadlocked. The fix is to use a mutex that "
"works across different greenlets and different pthreads."
msgid ""
"The object updater now supports two configuration settings: \"concurrency\" "
"and \"updater_workers\". The latter controls how many worker processes are "
"spawned, while the former controls how many concurrent container updates are "
"performed by each worker process. This should speed the processing of "
"async_pendings."
msgstr ""
"The object updater now supports two configuration settings: \"concurrency\" "
"and \"updater_workers\". The latter controls how many worker processes are "
"spawned, while the former controls how many concurrent container updates are "
"performed by each worker process. This should speed the processing of "
"async_pendings."
msgid ""
"The output of devices from ``swift-ring-builder`` has been reordered by "
"region, zone, ip, and device."
@@ -1296,6 +1354,9 @@ msgstr ""
msgid "Truncate error logs to prevent log handler from running out of buffer."
msgstr "Truncate error logs to prevent log handler from running out of buffer."
msgid "Unsigned payloads work with v4 signatures once more."
msgstr "Unsigned payloads work with v4 signatures once more."
msgid ""
"Update dnspython dependency to 1.14, removing the need to have separate "
"dnspython dependencies for Py2 and Py3."
@@ -1363,6 +1424,19 @@ msgstr ""
"functionality has been enabled in the ring modules to support this advanced "
"functionality. CLI tools will be delivered in a subsequent release."
msgid ""
"When listing objects in a container in json format, static large objects "
"(SLOs) will now include an additional new \"slo_etag\" key that matches the "
"etag returned when requesting the SLO. The existing \"hash\" key remains "
"unchanged as the MD5 of the SLO manifest. Text and XML listings are "
"unaffected by this change."
msgstr ""
"When listing objects in a container in json format, static large objects "
"(SLOs) will now include an additional new \"slo_etag\" key that matches the "
"etag returned when requesting the SLO. The existing \"hash\" key remains "
"unchanged as the MD5 of the SLO manifest. Text and XML listings are "
"unaffected by this change."
msgid ""
"When requesting objects, return 404 if a tombstone is found and is newer "
"than any data found. Previous behavior was to return stale data."
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.