summaryrefslogtreecommitdiff
path: root/locale/en/LC_MESSAGES/messages.po
diff options
context:
space:
mode:
Diffstat (limited to 'locale/en/LC_MESSAGES/messages.po')
-rw-r--r--locale/en/LC_MESSAGES/messages.po181
1 files changed, 75 insertions, 106 deletions
diff --git a/locale/en/LC_MESSAGES/messages.po b/locale/en/LC_MESSAGES/messages.po
index 320683e1..78b8e67b 100644
--- a/locale/en/LC_MESSAGES/messages.po
+++ b/locale/en/LC_MESSAGES/messages.po
@@ -2,7 +2,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2020-06-17 12:19+0200\n"
+"POT-Creation-Date: 2020-05-29 20:58+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: en <LL@li.org>\n"
@@ -1401,7 +1401,7 @@ msgid ""
msgstr ""
#: template/principles.html.j2:31
-msgid "1. Free/Libre Software"
+msgid "1. Free Software implementation"
msgstr ""
#: template/principles.html.j2:33
@@ -1410,191 +1410,160 @@ msgid ""
msgstr ""
#: template/principles.html.j2:36
-#, python-format
msgid ""
"GNU Taler must be <a href=\"https://www.gnu.org/philosophy/free-sw.html"
-"\">Free/Libre Software</a>. For merchants, Free/Libre Software prevents "
-"vendor lock-in meaning merchants can easily choose another service provider "
-"to process their payments. For countries, Free/Libre software means GNU "
-"Taler can not compromise sovereignty by imposing restrictions or "
-"requirements. And for exchange operators, transparency is crucial to satisfy "
-"<a href=\"https://en.wikipedia.org/wiki/Kerckhoffs%27s_principle"
-"\">Kerckhoff's principle</a> and to establish public confidence."
+"\">Free Software</a>. For merchants, our Free Software reference "
+"implementation prevents vendor lock-in. As the software of the payment "
+"provider itself is free, countries can deploy the payment system without "
+"compromising sovereignty."
msgstr ""
-#: template/principles.html.j2:49
+#: template/principles.html.j2:45
msgid ""
-"Customers benefit from Free/Libre Software because anyone is free to modify "
-"the wallet software support additional platforms. The source code must be "
-"available and make it easy to verify that user-hostile features such as "
-"tracking or telemetry are absent."
+"Customers benefit from Free Software as the wallet software can be made to "
+"run on a variety of platforms, and the absence of user-hostile features such "
+"as tracking or telemetry can easily be assured."
msgstr ""
-#: template/principles.html.j2:60
+#: template/principles.html.j2:56
msgid "2. Protect the privacy of buyers"
msgstr ""
-#: template/principles.html.j2:62
+#: template/principles.html.j2:58
msgid "You deserve some privacy"
msgstr ""
-#: template/principles.html.j2:64
+#: template/principles.html.j2:60
msgid ""
-"Privacy is most meaningful when it is guaranteed via technical measures, as "
-"opposed to mere policies. Without a technical layer providing privacy-by-"
-"default, financial transactions reveal unnecessary levels of personal or "
-"private data. This would be especially true when making micropayments for "
-"online publications. Thus, GNU Taler must protect the privacy of buyers to "
-"avoid facilitating totalitarian control over the population."
+"Privacy should be guaranteed via technical measures, as opposed to mere "
+"policies. Especially with micropayments for online publications, a "
+"disproportionate amount of rather private data about buyers would be "
+"revealed, if the payment system does not have privacy protections."
msgstr ""
-#: template/principles.html.j2:72
+#: template/principles.html.j2:68
msgid ""
-"Limited private data, such as the shipping address for a physical delivery, "
-"may need to be collected according to business needs and protected according "
-"to local laws. In this case, GNU Taler must enable deletion of such data as "
-"soon as it is no longer required."
+"In legislations with data protection regulations (such as the recently "
+"introduced GDPR in Europe), merchants benefit from this as well, as no data "
+"breach of customers can happen if this information is, by design, not "
+"collected in the first place. Obviously some private data, such as the "
+"shipping address for a physical delivery, must still be collected according "
+"to business needs."
msgstr ""
-#: template/principles.html.j2:83
+#: template/principles.html.j2:81
msgid ""
-"3. Auditability - enable the state to tax income and crack down on illegal "
-"business activities"
+"3. Enable the state to tax income and crack down on illegal business "
+"activities"
msgstr ""
-#: template/principles.html.j2:85
+#: template/principles.html.j2:83
msgid "Money laundering"
msgstr ""
-#: template/principles.html.j2:87
+#: template/principles.html.j2:85
msgid ""
-"As a payment system must comply with local laws in order to operate legally, "
-"GNU Taler must be designed to comply with these requirements. GNU Taler must "
-"provide an audit trail for investigators operating under the law. "
-"Furthermore, we consider levying of taxes as beneficial to society, and fair "
-"taxation requires income transparency. Thus, GNU Taler must enable "
-"authorities to track income."
+"As a payment system must be legal to operate and use, it must comply with "
+"regulatory requirements such as anti money laundering. Furthermore, we "
+"consider levying of taxes as beneficial to society, and fair taxation "
+"requires income transparency."
msgstr ""
-#: template/principles.html.j2:102
+#: template/principles.html.j2:96
msgid "4. Prevent payment fraud"
msgstr ""
-#: template/principles.html.j2:104
+#: template/principles.html.j2:98
msgid "Phishing attack"
msgstr ""
-#: template/principles.html.j2:106
+#: template/principles.html.j2:100
msgid ""
-"GNU Taler must mitigate the most common sources of payment fraud. We must "
-"follow best practices in software design, 3rd party design guidelines that "
-"prevent confusion and misleading user interfaces, and must have others "
-"inspect our publicly available code. Furthermore, GNU Taler must provide "
-"extensive cryptographic evidence for all key processes to enable all parties "
-"to precisely attribute bad behavior."
+"This imposes requirements on the security of the system, as well as on the "
+"general design, as payment fraud can also happen through misleading user "
+"interface design or the lack of cryptographic evidence for certain processes."
msgstr ""
-#: template/principles.html.j2:120
-msgid "5. Collect the minimum information necessary"
+#: template/principles.html.j2:110
+msgid "5. Only disclose the minimal amount of information necessary"
msgstr ""
-#: template/principles.html.j2:121
+#: template/principles.html.j2:111
msgid ""
"Privacy by design, privacy by default, General Data Protection Regulation "
"(GDPR) compliant"
msgstr ""
-#: template/principles.html.j2:123
+#: template/principles.html.j2:113
msgid ""
-"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."
+"The reason behind this goal is similar to (2). The privacy of buyers is "
+"given priority, but other parties such as merchants still benefit from it, "
+"for example, by keeping details about the merchant’s financials hidden from "
+"competitors."
msgstr ""
-#: template/principles.html.j2:137
+#: template/principles.html.j2:123
msgid "6. Be usable"
msgstr ""
-#: template/principles.html.j2:138
-msgid "Buy with one click. Easy for children."
+#: template/principles.html.j2:124
+msgid "Buy with one click"
msgstr ""
-#: template/principles.html.j2:140
+#: template/principles.html.j2:126
msgid ""
-"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 Advanced Programming Interfaces (APIs) to allow frictionless "
-"integrations between GNU Taler and other projects."
+"Specifically it must be usable for non-expert customers. Usability also "
+"applies to the integration with merchants, and informs choices about the "
+"architecture, such as encapsulating procedures that require cryptographic "
+"operations into an isolated component with a simple API."
msgstr ""
-#: template/principles.html.j2:157
+#: template/principles.html.j2:137
msgid "7. Be efficient"
msgstr ""
-#: template/principles.html.j2:158
+#: template/principles.html.j2:138
msgid "Energy efficiency"
msgstr ""
-#: template/principles.html.j2:160
+#: template/principles.html.j2:140
msgid ""
-"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."
+"Approaches such as proof-of-work are ruled out by this requirement. "
+"Efficiency is necessary for GNU Taler to be used for micropayments."
msgstr ""
-#: template/principles.html.j2:173
+#: template/principles.html.j2:150
msgid "8. Fault-tolerant design"
msgstr ""
-#: template/principles.html.j2:174
+#: template/principles.html.j2:151
msgid "Life Safers"
msgstr ""
-#: template/principles.html.j2:176
+#: template/principles.html.j2:153
msgid ""
-"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."
+"Taler should tolerate failure of individual components and systems, "
+"including malicious operators compromising core secrets. This manifests in "
+"architectural choices such as the isolation of certain components, and "
+"auditing procedures."
msgstr ""
-#: template/principles.html.j2:194
+#: template/principles.html.j2:164
msgid "9. Foster competition"
msgstr ""
-#: template/principles.html.j2:195
+#: template/principles.html.j2:165
msgid "A competitive market"
msgstr ""
-#: template/principles.html.j2:197
+#: template/principles.html.j2:167
msgid ""
"It must be relatively easy for competitors to deploy interoperable "
-"alternatives. The barriers for this in traditional financial systems are "
-"rather high and outside of our control. However, GNU Taler must minimize the "
-"technical burden for new competitors to enter the market."
-msgstr ""
-
-#: template/principles.html.j2:204
-msgid ""
-"GNU Taler must enable a diverse set of operators, breaking up the current "
-"system where only a few global companies dominate the market."
-msgstr ""
-
-#: template/principles.html.j2:209
-msgid ""
-"An example for a design choice that supports this is to split the whole "
-"system into smaller components that can be operated, developed and improved "
-"upon independently, instead of having one completely monolithic system."
+"alternatives. While the barriers for this in traditional financial systems "
+"are rather high, the technical burden for new competitors to join must be "
+"minimized. A design choice that supports this is to split the whole system "
+"into smaller components that can be operated, developed and improved upon "
+"independently, instead of having one completely monolithic system."
msgstr ""
#: template/schemafuzz.html.j2:6