openstack/zaqar
Code Issues Proposed changes

Imported Translations from Zanata

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

Change-Id: I9b3ea0d56e63bd8e299460cb3b24c4814174ed0f
This commit is contained in:
OpenStack Proposal Bot 2017-10-23 07:30:01 +00:00
parent ffd58efb1e
commit b10066de60
1 changed files with 318 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

318
releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po Normal file
View File

@ -0,0 +1,318 @@
# Andi Chandler <andi@gowling.com>, 2017. #zanata
msgid ""
msgstr ""
"Project-Id-Version: Zaqar Release Notes 5.0.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-10-13 03:36+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2017-10-19 05:53+0000\n"
"Last-Translator: Andi Chandler <andi@gowling.com>\n"
"Language-Team: English (United Kingdom)\n"
"Language: en-GB\n"
"X-Generator: Zanata 3.9.6\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
msgid "1.1.0"
msgstr "1.1.0"
msgid "2.0.0-10"
msgstr "2.0.0-10"
msgid "3.0.0"
msgstr "3.0.0"
msgid "4.0.0"
msgstr "4.0.0"
msgid "5.0.0"
msgstr "5.0.0"
msgid ""
"A new queue action is added so that users can purge a queue quickly. That "
"means all the messages and subscriptions will be deleted automatically but "
"the metadata of the queue will be kept."
msgstr ""
"A new queue action is added so that users can purge a queue quickly. That "
"means all the messages and subscriptions will be deleted automatically but "
"the metadata of the queue will be kept."
msgid ""
"Add a new webhook notifier using trust authentication. When using the 'trust"
"+' URL prefix, Zaqar will create a Keystone trust for the user, and then use "
"it when a notification happens to authenticate against Keystone and send the "
"token to the endpoint."
msgstr ""
"Add a new webhook notifier using trust authentication. When using the 'trust"
"+' URL prefix, Zaqar will create a Keystone trust for the user, and then use "
"it when a notification happens to authenticate against Keystone and send the "
"token to the endpoint."
msgid "Add migration support for Zaqar's sqlalchemy storage driver."
msgstr "Add migration support for Zaqar's sqlalchemy storage driver."
msgid ""
"Add two configurations for the notification endpoint of the websocket "
"server, instead of a random port and local address. One is 'notification-"
"bind', address on which the notification server will listen. Another is "
"'notification-port', port on which the notification server will listen."
msgstr ""
"Add two configurations for the notification endpoint of the websocket "
"server, instead of a random port and local address. One is 'notification-"
"bind', address on which the notification server will listen. Another is "
"'notification-port', port on which the notification server will listen."
msgid "Bug Fixes"
msgstr "Bug Fixes"
msgid "Critical Issues"
msgstr "Critical Issues"
msgid "Current Series Release Notes"
msgstr "Current Series Release Notes"
msgid ""
"Currently Zaqar can support more built-in/reserved attributes in queue. For "
"now there are two important attributes 'max_messages_post_size' and "
"'max_message_ttl'. With this feature, when user query queues Zaqar will show "
"those two attributes (read from config file if there is no customized value "
"from user) in queue metadata so that user can know what value it is."
msgstr ""
"Currently Zaqar can support more built-in/reserved attributes in queue. For "
"now there are two important attributes 'max_messages_post_size' and "
"'max_message_ttl'. With this feature, when user query queues Zaqar will show "
"those two attributes (read from config file if there is no customised value "
"from user) in queue metadata so that user can know what value it is."
msgid ""
"Currently, the v1 API is still accessible though it has been deprecated for "
"a while. And we're going to deprecate v1.1 soon. To keep the backward "
"compatibility, a new config option - ``enable_deprecated_api_versions`` is "
"added so that operator can totally turn off an API version or still support "
"it by adding the API version to the list of the new config option."
msgstr ""
"Currently, the v1 API is still accessible though it has been deprecated for "
"a while. And we're going to deprecate v1.1 soon. To keep the backward "
"compatibility, a new config option - ``enable_deprecated_api_versions`` is "
"added so that operator can totally turn off an API version or still support "
"it by adding the API version to the list of the new config option."
msgid "Deprecation Notes"
msgstr "Deprecation Notes"
msgid ""
"In IPv6 management network environment, starting Zaqar server will run into "
"'Address family for hostname not support' error when use WSGI simple server. "
"The root cause is that Python's TCPServer implementation is hard-coded to "
"use IPv4, even in IPv6 environments. Now this issue has been fixed."
msgstr ""
"In IPv6 management network environment, starting Zaqar server will run into "
"'Address family for hostname not support' error when use WSGI simple server. "
"The root cause is that Python's TCPServer implementation is hard-coded to "
"use IPv4, even in IPv6 environments. Now this issue has been fixed."
msgid ""
"Introduce Guru to Zaqar. Guru is a mechanism whereby developers and system "
"administrators can generate a report about the state of a running Zaqar "
"executable. This report is called a *Guru Meditation Report*. Now Guru can "
"support wsgi, websocket and uwsgi modes all."
msgstr ""
"Introduce Guru to Zaqar. Guru is a mechanism whereby developers and system "
"administrators can generate a report about the state of a running Zaqar "
"executable. This report is called a *Guru Meditation Report*. Now Guru can "
"support wsgi, websocket and uwsgi modes all."
msgid "Liberty Series Release Notes"
msgstr "Liberty Series Release Notes"
msgid "Mitaka Series Release Notes"
msgstr "Mitaka Series Release Notes"
msgid "New Features"
msgstr "New Features"
msgid "Newton Series Release Notes"
msgstr "Newton Series Release Notes"
msgid ""
"Now before users send messages to subscribers through a queue, the "
"subscribers should be confirmed first. Zaqar only sends messages to the "
"confirmed subscribers. This feature supports \"webhook\" and \"mailto\" "
"subscribers with mongoDB or redis backend. The \"mailto\" part will be done "
"in O cycle. Set \"require_confirmation = True\" to enable this feature. The "
"default value is \"False\" now and we will enable it by default after one or "
"two cycles."
msgstr ""
"Now before users send messages to subscribers through a queue, the "
"subscribers should be confirmed first. Zaqar only sends messages to the "
"confirmed subscribers. This feature supports \"webhook\" and \"mailto\" "
"subscribers with MongoDB or Redis backend. The \"mailto\" part will be done "
"in O cycle. Set \"require_confirmation = True\" to enable this feature. The "
"default value is \"False\" now and we will enable it by default after one or "
"two cycles."
msgid "Ocata Series Release Notes"
msgstr "Ocata Series Release Notes"
msgid "Other Notes"
msgstr "Other Notes"
msgid "Pike Series Release Notes"
msgstr "Pike Series Release Notes"
msgid ""
"Query for all subscriptions on a given queue by taking into account the "
"returned marker, if any. Without this fix, only 10 subscriptions can be "
"extracted from database to send notification."
msgstr ""
"Query for all subscriptions on a given queue by taking into account the "
"returned marker, if any. Without this fix, only 10 subscriptions can be "
"extracted from database to send notification."
msgid ""
"Queues now behave lazy in subscriptions also. So there is no need for the "
"user to pre-create a queue before creating a subscription for this queue. "
"Zaqar will create the queue automatically on the subscription creation "
"request. As before, all subscriptions will continue to stay active even if "
"the corresponding queue was deleted."
msgstr ""
"Queues now behave lazy in subscriptions also. So there is no need for the "
"user to pre-create a queue before creating a subscription for this queue. "
"Zaqar will create the queue automatically on the subscription creation "
"request. As before, all subscriptions will continue to stay active even if "
"the corresponding queue was deleted."
msgid "Start using reno to manage release notes."
msgstr "Start using Reno to manage release notes."
msgid ""
"Support 'post_data' and 'post_headers' options on subscribers, allowing "
"customization of the payload when having a webhook subscriber. The "
"'post_data' option supports the '$zaqar_message$' string template, which "
"will be replaced by the serialized JSON message if specified."
msgstr ""
"Support 'post_data' and 'post_headers' options on subscribers, allowing "
"customisation of the payload when having a webhook subscriber. The "
"'post_data' option supports the '$zaqar_message$' string template, which "
"will be replaced by the serialised JSON message if specified."
msgid "Support dot character in queue's name, like 'service.test_queue'."
msgstr "Support dot character in queue's name, like 'service.test_queue'."
msgid ""
"Support for dead letter queue is added for MongoDB, Redis and Swift. With "
"this feature, message will be moved to the specified dead letter queue if "
"it's claimed many times but still can't successfully processed by a client. "
"New reseved metadata keys of queue are added: _max_claim_count, "
"_dead_letter_queue and _dead_letter_queue_messages_ttl."
msgstr ""
"Support for dead letter queue is added for MongoDB, Redis and Swift. With "
"this feature, message will be moved to the specified dead letter queue if "
"it's claimed many times but still can't successfully processed by a client. "
"New reserved metadata keys of queue are added: _max_claim_count, "
"_dead_letter_queue and _dead_letter_queue_messages_ttl."
msgid ""
"Support notificaiton delivery policy in webhook type. It will work when the "
"notification is sent from Zaqar to the subscriber failed. User can define "
"the retry policy in the options of subscription or metadata of queue."
msgstr ""
"Support notification delivery policy in webhook type. It will work when the "
"notification is sent from Zaqar to the subscriber failed. User can define "
"the retry policy in the options of subscription or metadata of queue."
msgid ""
"The OSprofiler is integrated to Zaqar in Ocata. It is a library from oslo. "
"It aims to analyse the performance bottleneck issue by making possible to "
"generate one trace per request affecting all involved services and build a "
"tree of calls."
msgstr ""
"The OSprofiler is integrated to Zaqar in Ocata. It is a library from Oslo. "
"It aims to analyse the performance bottleneck issue by making possible to "
"generate one trace per request affecting all involved services and build a "
"tree of calls."
msgid ""
"The new Swift storage backend is added to Zaqar in Ocata. It's experimental "
"currently. To use this backend, you should modify the \"drivers\" section in "
"the config file. [Blueprint `swift-storage-driver <https://blueprints."
"launchpad.net/zaqar/+spec/swift-storage-driver>`_]"
msgstr ""
"The new Swift storage backend is added to Zaqar in Ocata. It's experimental "
"currently. To use this backend, you should modify the \"drivers\" section in "
"the config file. [Blueprint `swift-storage-driver <https://blueprints."
"launchpad.net/zaqar/+spec/swift-storage-driver>`_]"
msgid ""
"This feature is the third part of subscription confirmation feature. Support "
"to send email to subscriber if confirmation is needed. To use this feature, "
"user need to set the config option \"external_confirmation_url\", "
"\"subscription_confirmation_email_template\" and "
"\"unsubscribe_confirmation_email_template\". The confirmation page url that "
"will be used in email subscription confirmation before notification, this "
"page is not hosted in Zaqar server, user should build their own web service "
"to provide this web page. The subscription_confirmation_email_template let "
"user to customize the subscription confimation email content, including "
"topic, body and sender. The unsubscribe_confirmation_email_template let user "
"to customize the unsubscribe confimation email content, including topic, "
"body and sender too."
msgstr ""
"This feature is the third part of subscription confirmation feature. Support "
"to send email to subscriber if confirmation is needed. To use this feature, "
"user need to set the config option \"external_confirmation_url\", "
"\"subscription_confirmation_email_template\" and "
"\"unsubscribe_confirmation_email_template\". The confirmation page URL that "
"will be used in email subscription confirmation before notification, this "
"page is not hosted in Zaqar server, user should build their own web service "
"to provide this web page. The subscription_confirmation_email_template let "
"user to customize the subscription confirmation email content, including "
"topic, body and sender. The unsubscribe_confirmation_email_template let user "
"to customise the unsubscribe confirmation email content, including topic, "
"body and sender too."
msgid ""
"When access the root path of Zaqar service, for example: curl GET "
"http://127.0.0.1:8888/, user will see 401 error. Which will cause some front "
"end proxy (like HAProxy) to complain. Now this issue has been fixed."
msgstr ""
"When access the root path of Zaqar service, for example: curl GET "
"http://127.0.0.1:8888/, user will see 401 error. Which will cause some front "
"end proxy (like HAProxy) to complain. Now this issue has been fixed."
msgid ""
"When using the sqlalchemy driver, operators now are required to run \"zaqar-"
"sql-db-manage upgrade\" before making the service available. The service "
"previously tried to create the database on the first request, but it was "
"bound to race conditions."
msgstr ""
"When using the sqlalchemy driver, operators now are required to run \"zaqar-"
"sql-db-manage upgrade\" before making the service available. The service "
"previously tried to create the database on the first request, but it was "
"bound to race conditions."
msgid ""
"Zaqar API v2 has been released for several cycles and it is integrated as "
"the default API version by most of the OpenStack services. So it is time to "
"deprecated v1.1 in favor of v2. Now in Newton cycle, Zaqar API v1.1 is "
"officially deprecated."
msgstr ""
"Zaqar API v2 has been released for several cycles and it is integrated as "
"the default API version by most of the OpenStack services. So it is time to "
"deprecated v1.1 in favour of v2. Now in Newton cycle, Zaqar API v1.1 is "
"officially deprecated."
msgid "Zaqar Release Notes"
msgstr "Zaqar Release Notes"
msgid ""
"Zaqar didn't return the reserved metadata when listing detailed queue. After "
"this fix, Zaqar will return reserved metadata '_default_message_ttl' and "
"'_max_messages_post_size' in response of listing detailed queue."
msgstr ""
"Zaqar didn't return the reserved metadata when listing detailed queue. After "
"this fix, Zaqar will return reserved metadata '_default_message_ttl' and "
"'_max_messages_post_size' in response of listing detailed queue."
msgid "Zaqar now supports Cross-Origin Resource Sharing (CORS)."
msgstr "Zaqar now supports Cross-Origin Resource Sharing (CORS)."