Imported Translations from Zanata

For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: I224e8eed5b7ec6a8b99972052d22011e31a4e14e
Signed-off-by: OpenStack Proposal Bot <openstack-infra@lists.openstack.org>
Generated-By: openstack/openstack-zuul-jobs:roles/prepare-zanata-client/files/common_translation_update.sh
This commit is contained in:
OpenStack Proposal Bot
2025-07-09 03:55:49 +00:00
parent 9a5271ccdd
commit fb6d454f0f

View File

@@ -12,7 +12,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Glance_store Release Notes\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-02-06 17:30+0000\n"
"POT-Creation-Date: 2025-07-02 09:14+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@@ -151,9 +151,6 @@ msgstr "4.5.0"
msgid "4.6.0"
msgstr "4.6.0"
msgid "4.6.1-7"
msgstr "4.6.1-7"
msgid "4.7.0"
msgstr "4.7.0"
@@ -163,9 +160,6 @@ msgstr "4.7.0-4"
msgid "4.8.0"
msgstr "4.8.0"
msgid "4.8.1-4"
msgstr "4.8.1-4"
msgid "4.9.0"
msgstr "4.9.0"
@@ -1087,8 +1081,8 @@ msgid ""
"texts, defaults for sample configuration files, explicit choices of values "
"for operators to choose from, and a strict range defined with ``min`` and "
"``max`` boundaries. It is to be noted that the configuration options that "
"take integer values now have a strict range defined with \"min\" and/or \"max"
"\" boundaries where appropriate. This renders the configuration options "
"take integer values now have a strict range defined with \"min\" and/or "
"\"max\" boundaries where appropriate. This renders the configuration options "
"incapable of taking certain values that may have been accepted before but "
"were actually invalid. For example, configuration options specifying counts, "
"where a negative value was undefined, would have still accepted the supplied "
@@ -1103,8 +1097,8 @@ msgstr ""
"texts, defaults for sample configuration files, explicit choices of values "
"for operators to choose from, and a strict range defined with ``min`` and "
"``max`` boundaries. It is to be noted that the configuration options that "
"take integer values now have a strict range defined with \"min\" and/or \"max"
"\" boundaries where appropriate. This renders the configuration options "
"take integer values now have a strict range defined with \"min\" and/or "
"\"max\" boundaries where appropriate. This renders the configuration options "
"incapable of taking certain values that may have been accepted before but "
"were actually invalid. For example, configuration options specifying counts, "
"where a negative value was undefined, would have still accepted the supplied "