English Chinese (Traditional) Actions
Privacy by design, privacy by default, General Data Protection Regulation (GDPR) compliant 基於隱私來設計,以隱私為默認值,符合通用數據保護法規 (GDPR)
The privacy of buyers is given particular priority as part of principle (2). However, other parties - such as merchants - also must have data protection. Generally, GNU Taler must collect the minimum information necessary: data that is not collected or is no longer stored can not be compromised. 作為原則(2)的一部分,買方的隱私受到特別重視。然而,其他各方(例如商家)的資料也必受到保護。通常,GNU Taler 會收集必要的最少信息:不會破壞未收集或不再被存儲的資料。
6. Be usable 6. 要為可用的
Buy with one click. Easy for children. 一鍵購買。對孩童來說也十分容易。
GNU Taler must be usable for non-expert customers including end-users of a GNU Taler wallet, merchants who wish to accept payments using GNU Taler, and 3rd party application developers for e-commerce and other platforms. GNU Taler must follow best-practices usability guidelines and incorporate feedback from experts and users. Free/Libre software also requires Free/Libre documentation to allow for informed choices. GNU Taler must provide well-documented Application Programming Interfaces (APIs) to allow frictionless integrations between GNU Taler and other projects. GNU Taler 必須適用於非專家客戶,包括 GNU Taler 錢包的終端使用者、希望使用 GNU Taler 接受付款的商家以及電子商務和其他平台的第三方應用程序開發人員。GNU Taler 必須遵循最佳實踐可用性準則,並吸收專家和用戶的回饋。為了做出明智的選擇,自由軟體還需要自由文件。
GNU Taler 必須提供文件齊全的應用程序編程接口 (APIs) ,以實現 GNU Taler 與其他項目之間的無障礙整合 (frictionless integrations)。
7. Be efficient 7. 要有效率
Energy efficiency 能量效率
GNU Taler must be designed to be efficient. Quite simply, efficiency means fewer things to break, and it means more transactions per second and lowers our environmental impact. Efficiency is also critical for GNU Taler to be used for micropayments. Therefore certain expensive primitives, such as proof-of-work, must not be used by GNU Taler. GNU Taler 必須設計成高效率地。簡而言之,效率代表更少工作量、每秒從事更多的交易、更低的環境影響。效率對於將 GNU Taler 用於小額付款也至關重要。因此,GNU Taler 不得使用某些昂貴的原語 (primitives),例如工作量證明 (proof-of-work)。
8. Fault-tolerant design 8. 容錯設計
Life Safers 救星
Malicious operators, fat fingers, computer glitches, gremlins. Things go wrong. GNU Taler must be designed to tolerate failure of individual components and systems. Where the system can continue running safely, it will continue running safely. Where it must halt an operation, other operations must not be needlessly pulled offline. Where systems fail, they must fail gracefully. GNU Taler must have a plan to recover from malicious operators compromising core secrets. 惡意操作員、手滑 (fat fingers)、電腦故障、gremlins。差錯會發生。GNU Taler 的設計必須有容忍單個組件和系統的故障的能力。在系統可以繼續安全運行的地方,它將繼續安全運行。在它必須暫停運作的時,其他操作在非必要情況下不能離線。系統發生故障時,它們必須正常運行。GNU Taler 必須制定一個計劃,以從危害核心秘密的惡意運營者中恢復。


User avatar Ting-Yi

Translation changed

GNU Taler / Main web siteChinese (Traditional)

a year ago
User avatar Ting-Yi

Marked for edit

GNU Taler / Main web siteChinese (Traditional)

a year ago
Browse all component changes


English Chinese (Traditional)
No related strings found in the glossary.

String information

Source string location
String age
a year ago
Source string age
2 years ago
Translation file
locale/zh_Hant/LC_MESSAGES/messages.po, string 258