Imported Translations from Zanata

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

Change-Id: I192ec6e711bb405dce6a62267d4c4d7e789b28ae
This commit is contained in:
OpenStack Proposal Bot 2018-02-10 06:37:14 +00:00
parent 482fa891d0
commit bb9da32f0c
3 changed files with 76 additions and 184 deletions

View File

@ -4,9 +4,9 @@
# Andi Chandler <andi@gowling.com>, 2017. #zanata
msgid ""
msgstr ""
"Project-Id-Version: barbican 6.0.0.0b2.dev15\n"
"Project-Id-Version: barbican VERSION\n"
"Report-Msgid-Bugs-To: https://bugs.launchpad.net/openstack-i18n/\n"
"POT-Creation-Date: 2017-11-02 04:06+0000\n"
"POT-Creation-Date: 2018-02-09 17:50+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@ -87,9 +87,6 @@ msgstr ""
"management of connections). See http://docs.sqlalchemy.org/en/latest/core/"
"pooling.html for more details"
msgid "Add CA to project"
msgstr "Add CA to project"
msgid "Address of the KMIP server"
msgstr "Address of the KMIP server"
@ -128,21 +125,6 @@ msgstr "Bad format"
msgid "Bad key file permissions found, expected 400 for path: {file_path}"
msgstr "Bad key file permissions found, expected 400 for path: {file_path}"
msgid "CA Cert Chain retrieval"
msgstr "CA Cert Chain retrieval"
msgid "CA Signing Cert retrieval"
msgstr "CA Signing Cert retrieval"
msgid "CA creation"
msgstr "CA creation"
msgid "CA deletion"
msgstr "CA deletion"
msgid "CA projects retrieval"
msgstr "CA projects retrieval"
#, python-format
msgid "CA specified by ca_id %(ca_id)s not defined for project: %(project_id)s"
msgstr ""
@ -154,18 +136,6 @@ msgstr "Cannot generate a fullname for a null instance"
msgid "Cannot modify order type."
msgstr "Cannot modify order type."
msgid "Cannot set CA as a preferred CA as it is not a project CA."
msgstr "Cannot set CA as a preferred CA as it is not a project CA."
msgid "Certificate Authorities retrieval"
msgstr "Certificate Authorities retrieval"
msgid "Certificate Authorities retrieval (limited)"
msgstr "Certificate Authorities retrieval (limited)"
msgid "Certificate Authority retrieval"
msgstr "Certificate Authority retrieval"
msgid "Certificate event plugin \"{name}\" not found."
msgstr "Certificate event plugin \"{name}\" not found."
@ -722,18 +692,12 @@ msgstr "No data supplied to process."
msgid "No entities of type {entity_name} found"
msgstr "No entities of type {entity_name} found"
msgid "No global preferred CA defined"
msgstr "No global preferred CA defined"
msgid "No key handle was found"
msgstr "No key handle was found"
msgid "No plugin was found that could support your request"
msgstr "No plugin was found that could support your request"
msgid "No preferred CA defined for this project"
msgstr "No preferred CA defined for this project"
msgid "No profile_id specified"
msgstr "No profile_id specified"
@ -779,15 +743,6 @@ msgstr "No {entity} found with ID {id}"
msgid "Not Allowed. Sorry, only the creator of a consumer can delete it."
msgstr "Not Allowed. Sorry, only the creator of a consumer can delete it."
msgid "Not Found. CA attribute not found."
msgstr "Not Found. CA attribute not found."
msgid "Not Found. CA not found."
msgstr "Not Found. CA not found."
msgid "Not Found. CA not in project."
msgstr "Not Found. CA not in project."
msgid ""
"Not Found. Multiple backends support is not enabled in service configuration."
msgstr ""
@ -951,11 +906,6 @@ msgstr ""
"exceptions. If you notice this, you can lower this value to ensure that "
"SQLAlchemy reconnects before MySQL can drop the connection."
msgid ""
"Please change the preferred CA to a different project CA before removing it."
msgstr ""
"Please change the preferred CA to a different project CA before removing it."
msgid "Plugin does not support generation of subordinate CAs"
msgstr "Plugin does not support generation of subordinate CAs"
@ -1055,9 +1005,6 @@ msgstr "Quotas"
msgid "Read Error"
msgstr "Read Error"
msgid "Remove CA from project"
msgstr "Remove CA from project"
msgid "Removing preferred secret store"
msgstr "Removing preferred secret store"
@ -1074,12 +1021,6 @@ msgstr "Requested algorithm is not supported"
msgid "Retrieve global default secret store"
msgstr "Retrieve global default secret store"
msgid "Retrieve global preferred CA"
msgstr "Retrieve global preferred CA"
msgid "Retrieve project preferred CA"
msgstr "Retrieve project preferred CA"
msgid "Retrieve project preferred store"
msgstr "Retrieve project preferred store"
@ -1229,12 +1170,6 @@ msgstr ""
msgid "Server name for RPC task processing server"
msgstr "Server name for RPC task processing server"
msgid "Set global preferred CA"
msgstr "Set global preferred CA"
msgid "Set preferred project CA"
msgstr "Set preferred project CA"
msgid "Setting preferred secret store"
msgstr "Setting preferred secret store"
@ -1394,18 +1329,12 @@ msgstr "Unknown"
msgid "Unknown attribute type provided."
msgstr "Unknown attribute type provided."
msgid "Unset global preferred CA"
msgstr "Unset global preferred CA"
msgid "Update Order"
msgstr "Update Order"
msgid "Update Order failure seen - please contact site administrator."
msgstr "Update Order failure seen - please contact site administrator."
msgid "Updates are not supported for order type {0}."
msgstr "Updates are not supported for order type {0}."
msgid "User friendly plugin name"
msgstr "User friendly plugin name"

View File

@ -9,9 +9,9 @@
# Jeremy Liu <liujiong@gohighsec.com>, 2016. #zanata
msgid ""
msgstr ""
"Project-Id-Version: barbican 5.0.0.0rc2.dev1\n"
"Project-Id-Version: barbican VERSION\n"
"Report-Msgid-Bugs-To: https://bugs.launchpad.net/openstack-i18n/\n"
"POT-Creation-Date: 2017-08-11 03:08+0000\n"
"POT-Creation-Date: 2018-02-09 17:50+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@ -50,9 +50,6 @@ msgstr "带有那个标签的主密钥已经存在"
msgid "A new project preferred CA must be set before this one can be deleted."
msgstr "在删除项目首选CA之前必须先设置一个新的首选CA。"
msgid "Add CA to project"
msgstr "将CA添加到项目"
msgid "Address of the KMIP server"
msgstr "KMIP服务器的地址"
@ -86,21 +83,6 @@ msgstr "错误的格式"
msgid "Bad key file permissions found, expected 400 for path: {file_path}"
msgstr "发现错误的密钥文件权限,路径:{file_path}期望400"
msgid "CA Cert Chain retrieval"
msgstr "检索CA签发链"
msgid "CA Signing Cert retrieval"
msgstr "检索CA签发证书"
msgid "CA creation"
msgstr "创建CA"
msgid "CA deletion"
msgstr "删除CA"
msgid "CA projects retrieval"
msgstr "检索CA项目"
#, python-format
msgid "CA specified by ca_id %(ca_id)s not defined for project: %(project_id)s"
msgstr "指定的CA %(ca_id)s 未在项目:%(project_id)s中定义"
@ -111,18 +93,6 @@ msgstr "不能为空实例生成全名"
msgid "Cannot modify order type."
msgstr "不能修改order类型。"
msgid "Cannot set CA as a preferred CA as it is not a project CA."
msgstr "不能设置CA为首选CA因为其不是项目CA。"
msgid "Certificate Authorities retrieval"
msgstr "检索CA"
msgid "Certificate Authorities retrieval (limited)"
msgstr "检索CA受限"
msgid "Certificate Authority retrieval"
msgstr "检索CA"
msgid "Certificate event plugin \"{name}\" not found."
msgstr "证书事件插件“{name}”未发现。"
@ -542,18 +512,12 @@ msgstr "没有提供数据供处理。"
msgid "No entities of type {entity_name} found"
msgstr "未发现类型{entity_name}的实体"
msgid "No global preferred CA defined"
msgstr "没有定义全局首选CA"
msgid "No key handle was found"
msgstr "未发现密钥操作"
msgid "No plugin was found that could support your request"
msgstr "没有找到可以支持你的请求的插件"
msgid "No preferred CA defined for this project"
msgstr "该项目未设置首选CA"
msgid "No profile_id specified"
msgstr "未指定profile_id"
@ -597,15 +561,6 @@ msgstr "未找到ID为{id}的{entity}"
msgid "Not Allowed. Sorry, only the creator of a consumer can delete it."
msgstr "不被允许。对不起,只有消费者的创建者才能删除它。"
msgid "Not Found. CA attribute not found."
msgstr "未找到。CA属性未找到。"
msgid "Not Found. CA not found."
msgstr "未找到。未找到CA。"
msgid "Not Found. CA not in project."
msgstr "未找到。CA不在项目中。"
msgid ""
"Not Found. Multiple backends support is not enabled in service configuration."
msgstr "未发现。服务配置未启动多后端支持。"
@ -720,10 +675,6 @@ msgstr "NSS证书数据库的路径"
msgid "Path to vendor PKCS11 library"
msgstr "提供PKCS11库的路径"
msgid ""
"Please change the preferred CA to a different project CA before removing it."
msgstr "删除CA之前请先将首选CA设置为项目的其他CA。"
msgid "Plugin does not support generation of subordinate CAs"
msgstr "插件不支持生成子CA"
@ -807,9 +758,6 @@ msgstr "配额"
msgid "Read Error"
msgstr "读取错误"
msgid "Remove CA from project"
msgstr "将CA从项目中移除"
msgid "Removing preferred secret store"
msgstr "移除首选秘密存储"
@ -821,12 +769,6 @@ msgstr "请求{request_id}报告了status_complete状态但是未返回cert_i
msgid "Requested algorithm is not supported"
msgstr "请求的算法不支持"
msgid "Retrieve global preferred CA"
msgstr "检索全局首选CA"
msgid "Retrieve project preferred CA"
msgstr "检索项目首选CA"
msgid "Role used to identify an authenticated user as administrator."
msgstr "一种角色,用来确定该已认证用户是管理员。"
@ -943,12 +885,6 @@ msgstr "{secret_type}类型的秘密不应在数据库中有密码,因为在
msgid "Server name for RPC task processing server"
msgstr "RPC任务服务器的名称"
msgid "Set global preferred CA"
msgstr "设置全局首选CA"
msgid "Set preferred project CA"
msgstr "设置项目首选CA"
msgid "Setting preferred secret store"
msgstr "设置首选秘密存储"
@ -1064,18 +1000,12 @@ msgstr "未知"
msgid "Unknown attribute type provided."
msgstr "提供的属性类型未知"
msgid "Unset global preferred CA"
msgstr "取消设置全局首选CA"
msgid "Update Order"
msgstr "更新order"
msgid "Update Order failure seen - please contact site administrator."
msgstr "更新order失败。请联系站点管理员。"
msgid "Updates are not supported for order type {0}."
msgstr "不支持order类型{0}的更新"
msgid "Username for authenticating with KMIP server"
msgstr "KMIP服务器的认证用户名"

View File

@ -1,13 +1,14 @@
# Andi Chandler <andi@gowling.com>, 2017. #zanata
# Andi Chandler <andi@gowling.com>, 2018. #zanata
msgid ""
msgstr ""
"Project-Id-Version: Barbican Release Notes 6.0.0\n"
"Project-Id-Version: Barbican Release Notes\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-10-26 11:05+0000\n"
"POT-Creation-Date: 2018-02-09 17:50+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-26 11:35+0000\n"
"PO-Revision-Date: 2018-01-30 02:34+0000\n"
"Last-Translator: Andi Chandler <andi@gowling.com>\n"
"Language-Team: English (United Kingdom)\n"
"Language: en-GB\n"
@ -29,12 +30,18 @@ msgstr "4.0.0"
msgid "5.0.0"
msgstr "5.0.0"
msgid "6.0.0.0b1"
msgstr "6.0.0.0b1"
msgid "6.0.0.0b3"
msgstr "6.0.0.0b3"
msgid "Barbican Release Notes"
msgstr "Barbican Release Notes"
msgid "CAs"
msgstr "CAs"
msgid "Certificate Orders"
msgstr "Certificate Orders"
msgid "Contents:"
msgstr "Contents:"
@ -77,29 +84,6 @@ msgstr "Mitaka Series Release Notes"
msgid "New Features"
msgstr "New Features"
msgid ""
"New feature to support multiple secret store plugin backends. This feature "
"is not enabled by default. To use this feature, the relevant feature flag "
"needs to be enabled and supporting configuration needs to be added in the "
"service configuration. Once enabled, a project administrator will be able to "
"specify one of the available secret store backends as a preferred secret "
"store for their project secrets. This secret store preference applies only "
"to new secrets (key material) created or stored within that project. "
"Existing secrets are not impacted. See http://docs.openstack.org/developer/"
"barbican/setup/plugin_backends.html for instructions on how to setup "
"Barbican multiple backends, and the API documentation for further details."
msgstr ""
"New feature to support multiple secret store plugin backends. This feature "
"is not enabled by default. To use this feature, the relevant feature flag "
"needs to be enabled and supporting configuration needs to be added in the "
"service configuration. Once enabled, a project administrator will be able to "
"specify one of the available secret store backends as a preferred secret "
"store for their project secrets. This secret store preference applies only "
"to new secrets (key material) created or stored within that project. "
"Existing secrets are not impacted. See http://docs.openstack.org/developer/"
"barbican/setup/plugin_backends.html for instructions on how to setup "
"Barbican multiple backends, and the API documentation for further details."
msgid ""
"New feature to support multiple secret store plugin backends. This feature "
"is not enabled by default. To use this feature, the relevant feature flag "
@ -126,17 +110,6 @@ msgstr ""
msgid "Newton Series Release Notes"
msgstr "Newton Series Release Notes"
msgid ""
"Now within a single deployment, multiple secret store plugin backends can be "
"configured and used. With this change, a project administrator can pre-"
"define a preferred plugin backend for storing their secrets. New APIs are "
"added to manage this project level secret store preference."
msgstr ""
"Now within a single deployment, multiple secret store plugin backends can be "
"configured and used. With this change, a project administrator can pre-"
"define a preferred plugin backend for storing their secrets. New APIs are "
"added to manage this project level secret store preference."
msgid ""
"Now within a single deployment, multiple secret store plugin backends can be "
"configured and used. With this change, a project adminstrator can pre-define "
@ -264,9 +237,69 @@ msgstr ""
"migration of any existing data stored by previous versions of the PKCS#11 "
"backend."
msgid ""
"This release notify that we will remove Certificate Orders and CAs from API."
msgstr ""
"This release notify that we will remove Certificate Orders and CAs from the "
"API."
msgid "Upgrade Notes"
msgstr "Upgrade Notes"
msgid ""
"Why are we deprecating Certificate Issuance? There are a few reasons that "
"were considered for this decision. First, there does not seem to be a lot "
"of interest in the community to fully develop the Certificate Authority "
"integration with Barbican. We have a few outstanding blueprints that are "
"needed to make Certificate Issuance fully functional, but so far no one has "
"committed to getting the work done. Additionally, we've had very little buy-"
"in from public Certificate Authorities. Both Symantec and Digicert were "
"interested in integration in the past, but that interest didn't materialize "
"into robust CA plugins like we hoped it would. Secondly, there have been new "
"developments in the space of Certificate Authorities since we started "
"Barbican. The most significant of these was the launch of the Let's Encrypt "
"public CA along with the definition of the ACME protocol for certificate "
"issuance. We believe that future certificate authority services would do "
"good to implement the ACME standard, which is quite different than the API "
"the Barbican team had developed. Lastly, deprecating Certificate Issuance "
"within Barbican will simplify both the architecture and deployment of "
"Barbican. This will allow us to focus on the features that Barbican does "
"well -- the secure storage of secret material."
msgstr ""
"Why are we deprecating Certificate Issuance? There are a few reasons that "
"were considered for this decision. First, there does not seem to be a lot "
"of interest in the community to fully develop the Certificate Authority "
"integration with Barbican. We have a few outstanding blueprints that are "
"needed to make Certificate Issuance fully functional, but so far no one has "
"committed to getting the work done. Additionally, we've had very little buy-"
"in from public Certificate Authorities. Both Symantec and Digicert were "
"interested in integration in the past, but that interest didn't materialise "
"into robust CA plugins like we hoped it would. Secondly, there have been new "
"developments in the space of Certificate Authorities since we started "
"Barbican. The most significant of these was the launch of the Let's Encrypt "
"public CA along with the definition of the ACME protocol for certificate "
"issuance. We believe that future certificate authority services would do "
"good to implement the ACME standard, which is quite different than the API "
"the Barbican team had developed. Lastly, deprecating Certificate Issuance "
"within Barbican will simplify both the architecture and deployment of "
"Barbican. This will allow us to focus on the features that Barbican does "
"well -- the secure storage of secret material."
msgid ""
"Will Barbican still be able to store Certificates? Yes, absolutely! The "
"only thing we're deprecating is the plugin interface that talks to "
"Certificate Authorites and associated APIs. While you will not be able to "
"use Barbican to issue a new certificate, you will always be able to securely "
"store any certificates in Barbican, including those issued by public CAs or "
"internal CAs."
msgstr ""
"Will Barbican still be able to store Certificates? Yes, absolutely! The "
"only thing we're deprecating is the plugin interface that talks to "
"Certificate Authorities and associated APIs. While you will not be able to "
"use Barbican to issue a new certificate, you will always be able to securely "
"store any certificates in Barbican, including those issued by public CAs or "
"internal CAs."
msgid ""
"``'P11CryptoPluginException: HSM returned response code: 0xc0L "
"CKR_SIGNATURE_INVALID'``"