Translations by 師工程
師工程 has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 1. |
read_deleted can only be one of 'no', 'yes' or 'only', not %r
|
|
| 2016-07-22 |
read_deleted 只能是“no”、“yes”或“only”其中一項，而不能是 %r
|
|
| 2. |
Coordinator uninitialized.
|
|
| 2016-07-22 |
協調程序未初始化。
|
|
| 3. |
Not a valid string: %s
|
|
| 2016-07-22 |
無效字符串：%s
|
|
| 4. |
An unknown exception occurred.
|
|
| 2016-07-22 |
發生未知異常。
|
|
| 5. |
Bad or unexpected response from the storage volume backend API: %(data)s
|
|
| 2016-07-22 |
來自儲存磁區後端 API 的回應錯誤或不符合預期：%(data)s
|
|
| 6. |
Volume driver reported an error: %(message)s
|
|
| 2016-07-22 |
磁區驅動程式報告了錯誤：%(message)s
|
|
| 7. |
Backup driver reported an error: %(message)s
|
|
| 2016-07-22 |
備份驅動程式報告了錯誤：%(message)s
|
|
| 8. |
Connection to glance failed: %(reason)s
|
|
| 2016-07-22 |
Glance 連線失敗：%(reason)s
|
|
| 9. |
Not authorized.
|
|
| 2016-07-22 |
未被授權。
|
|
| 10. |
User does not have admin privileges
|
|
| 2016-07-22 |
使用者並沒有管理員權限
|
|
| 11. |
Policy doesn't allow %(action)s to be performed.
|
|
| 2016-07-22 |
原則不容許執行 %(action)s。
|
|
| 12. |
Not authorized for image %(image_id)s.
|
|
| 2016-07-22 |
未獲映像檔 %(image_id)s 的授權。
|
|
| 13. |
Volume driver not ready.
|
|
| 2016-07-22 |
磁區驅動程式未備妥。
|
|
| 14. |
Unacceptable parameters.
|
|
| 2016-07-22 |
不可接受的參數值
|
|
| 15. |
Invalid snapshot: %(reason)s
|
|
| 2016-07-22 |
無效的快照：%(reason)s
|
|
| 16. |
Invalid attaching mode '%(mode)s' for volume %(volume_id)s.
|
|
| 2016-07-24 |
連接模式“%(mode)s”不適用於磁區 %(volume_id)s。
|
|
| 2016-07-22 |
連接模式 '%(mode)s' 不適用於磁區 %(volume_id)s。
|
|
| 17. |
Volume %(volume_id)s is still attached, detach volume first.
|
|
| 2016-07-22 |
磁區 %(volume_id)s 仍處於連接狀態，請先將磁區分離。
|
|
| 18. |
The results are invalid.
|
|
| 2016-07-22 |
結果無效。
|
|
| 19. |
Invalid input received: %(reason)s
|
|
| 2016-07-22 |
收到的輸入無效：%(reason)s
|
|
| 20. |
Invalid volume type: %(reason)s
|
|
| 2016-07-22 |
無效的磁區類型：%(reason)s
|
|
| 21. |
Invalid volume: %(reason)s
|
|
| 2016-07-22 |
無效的磁區：%(reason)s
|
|
| 22. |
Invalid content type %(content_type)s.
|
|
| 2016-07-22 |
無效的內容類型 %(content_type)s。
|
|
| 23. |
Invalid host: %(reason)s
|
|
| 2016-07-22 |
無效的主機：%(reason)s
|
|
| 24. |
%(err)s
|
|
| 2016-07-22 |
%(err)s
|
|
| 25. |
Invalid auth key: %(reason)s
|
|
| 2016-07-22 |
認證密鑰無效：%(reason)s
|
|
| 26. |
Value "%(value)s" is not valid for configuration option "%(option)s"
|
|
| 2016-07-22 |
值“%(value)s”不適用於配置選項“%(option)s”
|
|
| 27. |
Service is unavailable at this time.
|
|
| 2016-07-22 |
暫時無法使用服務。
|
|
| 28. |
Image %(image_id)s is unacceptable: %(reason)s
|
|
| 2016-07-22 |
無法接受映像檔 %(image_id)s：%(reason)s
|
|
| 29. |
The device in the path %(path)s is unavailable: %(reason)s
|
|
| 2016-07-22 |
路徑 %(path)s 中的裝置無法使用：%(reason)s
|
|
| 30. |
Expected a uuid but received %(uuid)s.
|
|
| 2016-07-22 |
需要 UUID，但是收到 %(uuid)s。
|
|
| 31. |
API Version String %(version)s is of invalid format. Must be of format MajorNum.MinorNum.
|
|
| 2016-07-22 |
API 版本字串 %(version)s 的格式無效。格式必須是 MajorNum.MinorNum。
|
|
| 32. |
API version %(version)s is not supported on this method.
|
|
| 2016-07-22 |
此方法不支援 API %(version)s 版。
|
|
| 33. |
Version %(req_ver)s is not supported by the API. Minimum is %(min_ver)s and maximum is %(max_ver)s.
|
|
| 2016-07-22 |
API 不支援 %(req_ver)s 版。下限為 %(min_ver)s，上限為 %(max_ver)s。
|
|
| 34. |
Error while requesting %(service)s API.
|
|
| 2016-07-22 |
請求 %(service)s API 時發生錯誤。
|
|
| 35. |
Timeout while requesting %(service)s API.
|
|
| 2016-07-22 |
請求 %(service)s API 時發生逾時。
|
|
| 36. |
Timeout while requesting capabilities from backend %(service)s.
|
|
| 2016-07-22 |
請求後端 %(service)s 中的功能時逾時。
|
|
| 37. |
Resource could not be found.
|
|
| 2016-07-22 |
找不到資源。
|
|
| 38. |
Volume %(volume_id)s could not be found.
|
|
| 2016-07-22 |
找不到磁區 %(volume_id)s。
|
|
| 39. |
Volume attachment could not be found with filter: %(filter)s .
|
|
| 2016-07-22 |
使用過濾器 %(filter)s 找不到磁區附件。
|
|
| 40. |
Volume %(volume_id)s has no metadata with key %(metadata_key)s.
|
|
| 2016-07-22 |
磁區 %(volume_id)s 沒有索引鍵為 %(metadata_key)s 的 meta 資料。
|
|
| 41. |
Volume %(volume_id)s has no administration metadata with key %(metadata_key)s.
|
|
| 2016-07-22 |
磁區 %(volume_id)s 沒有索引鍵為%(metadata_key)s 的管理 meta 資料。
|
|
| 42. |
Invalid metadata: %(reason)s
|
|
| 2016-07-22 |
無效的 meta 資料：%(reason)s
|
|
| 43. |
Invalid metadata size: %(reason)s
|
|
| 2016-07-22 |
無效的 meta 資料大小：%(reason)s
|
|
| 44. |
Snapshot %(snapshot_id)s has no metadata with key %(metadata_key)s.
|
|
| 2016-07-22 |
快照 %(snapshot_id)s 沒有索引鍵為 %(metadata_key)s 的 meta 資料。
|
|
| 45. |
Volume type %(volume_type_id)s could not be found.
|
|
| 2016-07-22 |
找不到磁區類型 %(volume_type_id)s。
|
|
| 46. |
Volume type with name %(volume_type_name)s could not be found.
|
|
| 2016-07-22 |
找不到名稱為 %(volume_type_name)s 的磁區類型。
|
|
| 47. |
Volume type access not found for %(volume_type_id)s / %(project_id)s combination.
|
|
| 2016-07-22 |
找不到 %(volume_type_id)s / %(project_id)s 組合的磁區類型存取。
|
|
| 48. |
Volume Type %(volume_type_id)s has no extra specs with key %(extra_specs_key)s.
|
|
| 2016-07-22 |
磁區類型 %(volume_type_id)s 沒有索引鍵為 %(extra_specs_key)s 的額外規格。
|
|
| 49. |
Volume Type %(volume_type_id)s deletion is not allowed with volumes present with the type.
|
|
| 2016-07-22 |
磁區類型 %(volume_type_id)s 刪除作業，不為該類型的磁區所接受。
|
|
