aboutsummaryrefslogtreecommitdiff
path: root/locale/en/LC_MESSAGES
diff options
context:
space:
mode:
Diffstat (limited to 'locale/en/LC_MESSAGES')
-rw-r--r--locale/en/LC_MESSAGES/messages.po1069
1 files changed, 1069 insertions, 0 deletions
diff --git a/locale/en/LC_MESSAGES/messages.po b/locale/en/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..17ac9f9c
--- /dev/null
+++ b/locale/en/LC_MESSAGES/messages.po
@@ -0,0 +1,1069 @@
1
2msgid ""
3msgstr ""
4"Project-Id-Version: PROJECT VERSION\n"
5"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
6"POT-Creation-Date: 2017-01-19 18:48+0100\n"
7"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
8"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
9"Language: en\n"
10"Language-Team: en <LL@li.org>\n"
11"Plural-Forms: nplurals=2; plural=(n!=1)\n"
12"MIME-Version: 1.0\n"
13"Content-Type: text/plain; charset=utf-8\n"
14"Content-Transfer-Encoding: 8bit\n"
15"Generated-By: Babel 2.3.4\n"
16
17#: about.html.j2:1 citizens.html.j2:1 developers.html.j2:1
18#: governments.html.j2:1 index.html.j2:1 investors.html.j2:1
19#: merchants.html.j2:1 news.html.j2:1
20msgid "en"
21msgstr ""
22
23#: about.html.j2:3 citizens.html.j2:3 developers.html.j2:3
24#: financial-news.html.j2:5 governments.html.j2:3 index.html.j2:3
25#: investors.html.j2:3 merchants.html.j2:3 news.html.j2:3 wallet.html.j2:5
26msgid "GNU Taler"
27msgstr ""
28
29#: about.html.j2:3 about.html.j2:12
30msgid "About us"
31msgstr ""
32
33#: about.html.j2:20
34msgid ""
35"GNU maintainer. Network security &amp; privacy researcher. Software "
36"architect."
37msgstr ""
38
39#: about.html.j2:25
40msgid ""
41"Entrepreneur, Investor, Fortune 100 CIO, IT company director in different"
42" industries, …."
43msgstr ""
44
45#: about.html.j2:30
46msgid "CFO"
47msgstr ""
48
49#: about.html.j2:37
50msgid "Applied cryptography. Contact to W3c &amp; Tor."
51msgstr ""
52
53#: about.html.j2:42
54msgid "Theoretical foundations."
55msgstr ""
56
57#: about.html.j2:47
58msgid "Founder of the GNU project. Ethical guidance and licensing."
59msgstr ""
60
61#: about.html.j2:54
62msgid "PhD Student, TU Munich. Currently teaching."
63msgstr ""
64
65#: about.html.j2:59
66msgid "PhD Student, Inria.."
67msgstr ""
68
69#: about.html.j2:64 about.html.j2:79
70msgid "Software engineer."
71msgstr ""
72
73#: about.html.j2:71
74msgid "Sustainable business development."
75msgstr ""
76
77#: about.html.j2:75
78msgid "Software engineer. Works on libebics."
79msgstr ""
80
81#: about.html.j2:85
82msgid "Translator (Spanish)"
83msgstr ""
84
85#: about.html.j2:89 about.html.j2:93
86msgid "Translator (Italian)"
87msgstr ""
88
89#: about.html.j2:99
90msgid "Hardware security module"
91msgstr ""
92
93#: about.html.j2:103
94msgid "Risk management"
95msgstr ""
96
97#: about.html.j2:107
98msgid "PhD student, TU Munich. Currently teaching."
99msgstr ""
100
101#: about.html.j2:113
102msgid "Software engineer. Works on Android wallet."
103msgstr ""
104
105#: citizens.html.j2:3
106msgid "Citizens"
107msgstr ""
108
109#: citizens.html.j2:12
110msgid "Advantages for citizens"
111msgstr ""
112
113#: citizens.html.j2:19
114msgid "Security"
115msgstr ""
116
117#: citizens.html.j2:21
118msgid ""
119"Taler is the electronic equivalent of cash, except harder to fake.\n"
120" If your digital wallet is lost -- say because\n"
121" your computer is irreparably damaged or compromised -- only "
122"the amount of coin\n"
123" stored in your wallet will be lost. Unlike a physical "
124"wallet, you can make\n"
125" backups of your digital wallet which can provide security "
126"against data loss.\n"
127" So your digital wallet works mostly just like\n"
128" a physical wallet, except online and without the need to "
129"manually count coins."
130msgstr ""
131
132#: citizens.html.j2:30
133msgid "Privacy"
134msgstr ""
135
136#: citizens.html.j2:32
137msgid ""
138"Your transactions are private, neither the exchange nor merchant needs to"
139"\n"
140" learn your identity. There is no need to give our credit "
141"card numbers or\n"
142" other sensitive information, and the merchant will only be "
143"able to do\n"
144" exactly the transaction you confirmed using your digital "
145"wallet."
146msgstr ""
147
148#: citizens.html.j2:40
149msgid "Convenience"
150msgstr ""
151
152#: citizens.html.j2:42
153msgid ""
154"You will be able to withdraw digital coins to replenish your wallet using"
155"\n"
156" your credit card or SEPA transactions, similar to how you "
157"pay or withdraw\n"
158" cash today."
159msgstr ""
160
161#: citizens.html.j2:47
162msgid "Stability "
163msgstr ""
164
165#: citizens.html.j2:49
166msgid ""
167"Coins in your digital wallet will be of the same denomination as the\n"
168" cash in your physical wallet. So you will not have to worry "
169"about\n"
170" currency fluctuations or conversion rates. Like a physical "
171"wallet,\n"
172" you can carry digital coins of different currencies in your "
173"digital\n"
174" wallet at the same time."
175msgstr ""
176
177#: citizens.html.j2:57
178msgid "Taler as seen by customers"
179msgstr ""
180
181#: citizens.html.j2:59
182msgid ""
183"Customers interact with the Taler system mostly using\n"
184" a free wallet implementation, which may be an extension or "
185"plugin\n"
186" to their browser or a custom application on their computer(s).\n"
187" Typical steps performed by customers are:\n"
188" "
189msgstr ""
190
191#: citizens.html.j2:68
192msgid ""
193"The customer selects an exchange (i.e. by visiting the\n"
194" respective website or selecting from a list of exchanges in"
195" the\n"
196" application) and asks the wallet to create bank transfer\n"
197" instructions to withdraw a certain amount of electronic "
198"cash.\n"
199" The bank transfer instructions will contain an\n"
200" access code that must be included in the subject of the\n"
201" transaction, as well as the wire details for the exchange "
202"(i.e.\n"
203" a SEPA account number)."
204msgstr ""
205
206#: citizens.html.j2:77
207msgid ""
208"The customer then instructs his <b>bank</b> to\n"
209" transfer funds from his account to the Taler exchange "
210"using\n"
211" these instructions provided by the wallet (top left)."
212msgstr ""
213
214#: citizens.html.j2:81
215msgid ""
216"Once the funds have arrived, the wallet will\n"
217" automatically withdraw the electronic coins. The\n"
218" customer can use the wallet to review his remaining "
219"balance\n"
220" at any time. He can also make backups to secure his "
221"digital\n"
222" coins against hardware failures."
223msgstr ""
224
225#: citizens.html.j2:87
226msgid ""
227"When visiting a merchant that supports Taler,\n"
228" an additional payment option for Taler is enabled in the "
229"checkout system.\n"
230" If the customer selects payments via Taler, the wallet\n"
231" displays the secured contract from the merchant and asks\n"
232" for confirmation. Taler does not require the customer\n"
233" to provide any identity information to the merchant.\n"
234" Transaction histories and digitally\n"
235" signed contracts can be preserved in the wallet for future"
236"\n"
237" review by the customer, or even use in court."
238msgstr ""
239
240#: developers.html.j2:3
241msgid "Developers"
242msgstr ""
243
244#: developers.html.j2:12
245msgid "Taler for developers"
246msgstr ""
247
248#: developers.html.j2:18
249msgid "Free"
250msgstr ""
251
252#: developers.html.j2:20
253msgid ""
254"Taler is free software implementing an open\n"
255" protocol. Anybody is welcome to inspect our code and\n"
256" integrate our reference implementation into their\n"
257" applications. Different components of Taler are being\n"
258" made available under different licenses. The Affero\n"
259" GPLv3+ is used for the exchange, the LGPLv3+ is used for\n"
260" reference code demonstrating integration with merchant\n"
261" platforms, and licenses like Apache/Mozilla/GPLv3+ are\n"
262" used for wallets and related customer-facing software.\n"
263" We are open for constructive suggestions for maximizing\n"
264" the adoption of this libre payment platform.\n"
265" "
266msgstr ""
267
268#: developers.html.j2:34
269msgid "RESTful"
270msgstr ""
271
272#: developers.html.j2:36
273msgid ""
274"Taler is designed to work on the Internet. To\n"
275"\t ensure that Taler payments can work with restrictive\n"
276"\t network setups, Taler uses a RESTful protocol over HTTP or\n"
277"\t HTTPS. Taler's security does not depend upon the use of\n"
278"\t HTTPS, but obviously merchants may choose to offer HTTPS\n"
279"\t for consistency and because it generally is better for\n"
280"\t privacy compared to HTTP. Taler uses JSON to encode\n"
281"\t structure data, making it easy to integrate Taler with\n"
282"\t existing Web applications. Taler's protocol is documented\n"
283"\t in detail <a href='https://api.taler.net/'>here</a>.\n"
284" "
285msgstr ""
286
287#: developers.html.j2:51
288msgid "Code"
289msgstr ""
290
291#: developers.html.j2:53
292msgid ""
293"Taler is currently primarily developed by a\n"
294"\t research team at Inria and TU Munich. However,\n"
295"\t contributions from anyone are welcome. Our Git\n"
296"\t repositories can be cloned using the Git and HTTP access\n"
297"\t methods against <tt>git.taler.net</tt> with the name of\n"
298"\t the respective repository. A list of public repositories\n"
299"\t can be found in\n"
300"\t our <a href='https://git.taler.net/'>GitWeb</a>.\n"
301" "
302msgstr ""
303
304#: developers.html.j2:64
305msgid "Documentation"
306msgstr ""
307
308#: developers.html.j2:66
309msgid ""
310"In addition to this website,\n"
311" the <a href='https://git.taler.net/'>documented\n"
312" code</a> and the <a href='https://api.taler.net/'>API\n"
313" documentation</a>, we are in the process of preparing a\n"
314" comprehensive design document which will be published here\n"
315" soon.\n"
316" "
317msgstr ""
318
319#: developers.html.j2:75
320msgid "Discussion"
321msgstr ""
322
323#: developers.html.j2:77
324msgid ""
325"We have a mailinglist for developer discussions.\n"
326" You can subscribe to it or read the list archive at\n"
327" <a "
328"href='http://lists.gnu.org/mailman/listinfo/taler'>http://lists.gnu.org/mailman/listinfo/taler</a>."
329msgstr ""
330
331#: developers.html.j2:85
332msgid "Regression Testing"
333msgstr ""
334
335#: developers.html.j2:87
336msgid ""
337"We\n"
338" have <a href='https://buildbot.net/'>Buildbot</a>\n"
339" automation tests to detect regressions and check for\n"
340" portability at\n"
341" <a href='https://buildbot.taler.net/'>buildbot.taler.net</a>."
342"\n"
343" "
344msgstr ""
345
346#: developers.html.j2:95
347msgid "Code Coverage Analysis"
348msgstr ""
349
350#: developers.html.j2:97
351msgid ""
352"We\n"
353" use <a "
354"href='http://ltp.sourceforge.net/coverage/lcov.php'>LCOV</a>\n"
355" to analyze the code coverage of our tests, the results are\n"
356" available\n"
357" at <a href='https://lcov.taler.net/'>lcov.taler.net</a>.\n"
358" "
359msgstr ""
360
361#: developers.html.j2:105
362msgid "Performance Analysis"
363msgstr ""
364
365#: developers.html.j2:107
366msgid ""
367"We\n"
368" use <a href='https://gnunet.org/gauger'>Gauger</a> for\n"
369" performance regression analysis of the exchange backend\n"
370" at <a href='https://gauger.taler.net/'>gauger.taler.net</a>.\n"
371" "
372msgstr ""
373
374#: developers.html.j2:116
375msgid "Taler system overview"
376msgstr ""
377
378#: developers.html.j2:118
379msgid ""
380"The Taler system consists of protocols executed\n"
381" among a number of actors with the help\n"
382" of <a href='https://www.fsf.org/'>Free Software</a> as\n"
383" illustrated in the illustration on the right. Typical\n"
384" transactions involve the following steps:\n"
385" "
386msgstr ""
387
388#: developers.html.j2:127
389msgid ""
390"A customer instructs his <b>bank</b> to\n"
391" transfer funds from his account to the Taler exchange\n"
392" (top left). In the subject of the transaction, he\n"
393" includes an authentication token from his\n"
394" electronic <b>wallet</b>. In Taler terminology, the\n"
395" customer creates a reserve at the exchange.\n"
396" "
397msgstr ""
398
399#: developers.html.j2:135
400msgid ""
401"Once the exchange has received the\n"
402" transfer, it allows the customer's electronic wallet\n"
403" to <b>withdraw</b> electronic coins. The electronic\n"
404" coins are digital representations of the original\n"
405" currency from the transfer. It is important to note\n"
406" that the exchange does not learn the &quot;serial "
407"numbers&quot;\n"
408" of the coins created in this process, so it cannot tell\n"
409" later which customer purchased what at which merchant.\n"
410" The use of Taler does not change the currency or the\n"
411" total value of the funds (except for fees which the\n"
412" exchange may charge for the service).\n"
413" "
414msgstr ""
415
416#: developers.html.j2:148
417msgid ""
418"Once the customer has the digital coins in\n"
419" his wallet, the wallet can be used to <b>spend</b> the\n"
420" coins with merchant portals that support the Taler\n"
421" payment system and accept the respective exchange as a\n"
422" business partner (bottom arrow). This creates a digital\n"
423" contract signed by the customer's coins and the\n"
424" merchant. If necessary, the customer can later use\n"
425" this digitally signed contract in a court of law to\n"
426" prove the exact terms of the contract and that he paid\n"
427" the respective amount. The customer does not learn the\n"
428" banking details of the merchant, and Taler does not\n"
429" require the merchant to learn the identity of the\n"
430" customer. Naturally, the customer can spend any\n"
431" fraction of his digital coins (the system takes care of\n"
432" customers getting change).\n"
433" "
434msgstr ""
435
436#: developers.html.j2:165
437msgid ""
438"Merchants receiving digital\n"
439" coins <b>deposit</b> the respective receipts that\n"
440" resulted from the contract signing with the customer at\n"
441" the exchange to redeem the coins. The deposit step\n"
442" does not reveal the details of the contract between the\n"
443" customer and the merchant or the identity of the\n"
444" customer to the exchange in any way. However, the\n"
445" exchange does learn the identity of the merchant via\n"
446" the provided bank routing information. The merchant\n"
447" can, for example when compelled by the state for\n"
448" taxation, provide information linking the individual\n"
449" deposit to the respective contract signed by the\n"
450" customer. Thus, the exchange's database allows the\n"
451" state to enforce that merchants pay applicable taxes\n"
452" (and do not engage in illegal contracts).\n"
453" "
454msgstr ""
455
456#: developers.html.j2:182
457msgid ""
458"Finally, the exchange transfers funds\n"
459" corresponding to the digital coins redeemed by the\n"
460" merchants to the merchant's <b>bank</b> account. The\n"
461" exchange may combine multiple small transactions into\n"
462" one larger bank transfer. The merchant can query the\n"
463" exchange about the relationship between the bank\n"
464" transfers and the individual claims that were\n"
465" deposited.\n"
466" "
467msgstr ""
468
469#: developers.html.j2:192
470msgid ""
471"Most importantly, the exchange keeps\n"
472" cryptographic proofs that allow it to demonstrate that\n"
473" it is operating correctly to third parties. The system\n"
474" requires an external <b>auditor</b>, such as a\n"
475" government-appointed financial regulatory body, to\n"
476" frequently verify the exchange's databases and check that\n"
477" its bank balance matches the total value of the\n"
478" remaining coins in circulation.\n"
479" "
480msgstr ""
481
482#: developers.html.j2:202
483msgid ""
484"Without the auditor, the exchange operators\n"
485" could embezzle funds they are holding in\n"
486" reserve. Customers and merchants cannot cheat each\n"
487" other or the exchange. If any party's computers are\n"
488" compromised, the financial damage is limited to the\n"
489" respective party and proportional to the funds they\n"
490" have in circulation during the period of the\n"
491" compromise.\n"
492" "
493msgstr ""
494
495#: financial-news.html.j2:5 financial-news.html.j2:14
496msgid "Financial News"
497msgstr ""
498
499#: governments.html.j2:3
500msgid "Governments"
501msgstr ""
502
503#: governments.html.j2:12
504msgid "Advantages for governments"
505msgstr ""
506
507#: governments.html.j2:19 index.html.j2:23
508msgid "Taxable"
509msgstr ""
510
511#: governments.html.j2:21
512msgid ""
513"Taler is an electronic payment system that was built with the goal of "
514"supporting taxation.\n"
515" With Taler, the receiver of any form of payment is known, "
516"and the payment information comes\n"
517" attached with some details about what the payment was made "
518"for (but not the identity of the customer). Thus, governments can use "
519"this\n"
520" data to tax buisnesses and individuals based on their "
521"income, making tax evasion and\n"
522" black markets less viable."
523msgstr ""
524
525#: governments.html.j2:28 investors.html.j2:26 merchants.html.j2:27
526msgid "Secure"
527msgstr ""
528
529#: governments.html.j2:30
530msgid ""
531"Taler's payments are cryptographically secured. Thus, customers, "
532"merchants and\n"
533" the exchange can mathematically demonstrate their lawful "
534"behavior in court in case\n"
535" of disputes. Financial damages are strictly limited, "
536"improving economic security\n"
537" for individuals, merchants, the exchange and the state. "
538"Most importantly, an\n"
539" independent auditor can ensure that there is no &quot;bad "
540"exchange&quot;\n"
541" within the Taler system who might threaten the economy due "
542"to fraud."
543msgstr ""
544
545#: governments.html.j2:40 index.html.j2:37
546msgid "Libre"
547msgstr ""
548
549#: governments.html.j2:42
550msgid ""
551"Taler is free software implementing an open protocol standard. Thus, "
552"Taler will\n"
553" enable competition and avoid the monopolization of payment "
554"systems that threatens\n"
555" global political and financial stability today."
556msgstr ""
557
558#: governments.html.j2:47 investors.html.j2:16
559msgid "Efficient"
560msgstr ""
561
562#: governments.html.j2:49
563msgid ""
564"Taler is designed to be efficient. Unlike timeline-based payment systems"
565" like\n"
566" BitCoin, Taler will not threaten the availability of "
567"national electric grids or\n"
568" (significantly) contribute to environmental pollution."
569msgstr ""
570
571#: governments.html.j2:55
572msgid "Taler as seen by governments"
573msgstr ""
574
575#: governments.html.j2:57
576msgid ""
577"Governments can observe traditional wire\n"
578" transfers entering and leaving the Taler system, and\n"
579" require merchants and exchange operators to provide certain\n"
580" information during financial audits. Exchange operators\n"
581" are expected to be permanently checked by auditors,\n"
582" while merchants may be required to reveal information\n"
583" during regular tax audits.\n"
584" Information available to the government includes:\n"
585" "
586msgstr ""
587
588#: governments.html.j2:69
589msgid ""
590"From the banking system:\n"
591" The total amount of digital currency\n"
592" obtained by a customer. The government could impose\n"
593" limits on how many digital coins a customer may\n"
594" withdraw within a given timeframe."
595msgstr ""
596
597#: governments.html.j2:75
598msgid ""
599"From the banking system:\n"
600" The total amount of income received\n"
601" by any merchant via the Taler system."
602msgstr ""
603
604#: governments.html.j2:79
605msgid ""
606"From auditing the exchange:\n"
607" The amounts of digital coins legitimately withdrawn by\n"
608" customers from the exchange, the value of non-redeemed "
609"digital coins\n"
610" in customer's wallets, the value and corresponding wire "
611"details\n"
612" of deposit operations performed by merchants with the "
613"exchange, and\n"
614" the income of the exchange from transaction fees."
615msgstr ""
616
617#: governments.html.j2:86
618msgid ""
619"From auditing merchants:\n"
620" For each deposit operation, the exact details of the\n"
621" underlying contract that was signed between\n"
622" customer and merchant. However, this information would\n"
623" typically not include the identity of the customer.\n"
624" Note that while the customer can decide to prove that it "
625"was his\n"
626" transaction (i.e. in court when suing the merchant if the\n"
627" merchant failed to deliver on the contract),\n"
628" merchant, exchange and government cannot find out the "
629"customer's\n"
630" identity from the information that Taler collects."
631msgstr ""
632
633#: index.html.j2:15
634msgid "Electronic payments for a liberal society!"
635msgstr ""
636
637#: index.html.j2:16
638msgid ""
639"Taler is a new electronic payment system under development\n"
640"\t at <a href='http://www.inria.fr/'>Inria</a>. Today, this website "
641"only\n"
642"\t presents the advantages our system is expected to provide. We "
643"expect to\n"
644"\t make the payment system operational in 2017."
645msgstr ""
646
647#: index.html.j2:24
648msgid ""
649"Unlike BitCoin or cash payments, Taler ensures that\n"
650"\t governments can learn their citizen's total income and thus "
651"collect\n"
652"\t sales, value-added or income taxes. Taler is thus a currency for "
653"the\n"
654"\t mainstream economy, and not the black market."
655msgstr ""
656
657#: index.html.j2:30
658msgid "Anonymous"
659msgstr ""
660
661#: index.html.j2:31
662msgid ""
663"When you pay with Taler, your identity does not have to\n"
664"\t be revealed to the merchant. The bank, government and exchange "
665"will also\n"
666"\t never learn how you spent your electronic money. However, you can\n"
667"\t prove that you paid in court if necessary."
668msgstr ""
669
670#: index.html.j2:38
671msgid ""
672"Taler is free software from <a href='http://www.gnu.org/'>GNU</a> "
673"implementing an open protocol.\n"
674"\t Anybody is welcome to inspect our code and integrate our reference"
675"\n"
676"\t implementation into their applications."
677msgstr ""
678
679#: index.html.j2:45
680msgid "Electronic"
681msgstr ""
682
683#: index.html.j2:46
684msgid ""
685"Taler is designed to work on the Internet. Using a\n"
686"\t so-called RESTful protocol over HTTP or HTTPS, Taler is easy to\n"
687"\t integrate with existing Web applications."
688msgstr ""
689
690#: index.html.j2:51
691msgid "Reserves"
692msgstr ""
693
694#: index.html.j2:52
695msgid ""
696"Taler uses an electronic exchange holding financial\n"
697" reserves in existing currencies. This means that Taler is "
698"not\n"
699"\t a new currency with the inherent currency fluctuation risks, but\n"
700"\t instead the cryptographic coins correspond to existing currencies,"
701" such as\n"
702"\t US Dollars, Euros or even BitCoins."
703msgstr ""
704
705#: index.html.j2:60
706msgid "Taler Web payments paper published."
707msgstr ""
708
709#: index.html.j2:61
710msgid "More news »"
711msgstr ""
712
713#: index.html.j2:65
714msgid "Taler technology: About taxability, change and privacy"
715msgstr ""
716
717#: index.html.j2:66
718msgid ""
719"One of the key goals of Taler is to provide anonymity for\n"
720" citizens buying goods and services, while ensuring that the "
721"state can\n"
722" observe incoming transactions to ensure businesses engage only"
723" in\n"
724" legal activities and do not evade taxes (such as income tax,\n"
725" sales tax or value-added tax). However, we also want to stay\n"
726" out of the immediate personal domain, so sharing funds within "
727"a\n"
728" family or copying coins between devices should not be subject "
729"to\n"
730" monitoring by the state.\n"
731" "
732msgstr ""
733
734#: index.html.j2:75
735msgid ""
736"As a result, Taler does not intrude into the\n"
737" personal economic domain, offers good privacy, taxability\n"
738" for transactions and the ability to give change.\n"
739" "
740msgstr ""
741
742#: investors.html.j2:3
743msgid "Investors"
744msgstr ""
745
746#: investors.html.j2:12
747msgid "Operate a Taler exchange!"
748msgstr ""
749
750#: investors.html.j2:18
751msgid ""
752"Taler uses efficient cryptographic primitives (such as RSA 2048 and\n"
753" EdDSA) and is thus expected to be able to handle large "
754"transaction\n"
755" volumes, only limited by the input/output capabilities of "
756"the\n"
757" database. Thus, running a Taler exchange should be "
758"profitable even\n"
759" with very low (less than 1 cent) transaction fees (at "
760"appropriate\n"
761" transaction volume)."
762msgstr ""
763
764#: investors.html.j2:28
765msgid ""
766"All transactions in Taler are secured using modern cryptography and\n"
767" trust in all parties is minimized. Financial damage is "
768"bounded\n"
769" (for customers, merchants and the exchange) even\n"
770" in the case that systems are compromised and private keys "
771"are stolen.\n"
772" Databases can be audited for consistency, resulting in "
773"either the\n"
774" detection of compromised systems or the demonstration that\n"
775" participants were honest."
776msgstr ""
777
778#: investors.html.j2:37
779msgid "Business model"
780msgstr ""
781
782#: investors.html.j2:39
783msgid ""
784"The basic business model for Taler is the operation of an exchange. An "
785"exchange converts money from traditional payment systems (Mastercard,\n"
786" SEPA, Visa, BitCoin, ACH, SWIFT, etc.) to anonymous "
787"electronic\n"
788" coins in the same currency. The customer can then redeem the"
789" electronic\n"
790" coins at a merchant, who can exchange them for money "
791"represented using\n"
792" traditional payment systems at the exchange. The exchange "
793"can then charge\n"
794" fees (to the customer, merchant or both) to facilitate the "
795"transactions."
796msgstr ""
797
798#: investors.html.j2:48
799msgid "Taler as seen by the exchange operator"
800msgstr ""
801
802#: investors.html.j2:50
803msgid ""
804"The exchange operator primarily operates a Web service\n"
805" portal and keeps databases with transaction details and\n"
806" cryptographic proofs. Its operational expenses are thus "
807"related to\n"
808" its interactions with the banking system and the operation of\n"
809" the computing infrastructure, while its income is based on\n"
810" transaction fees it may charge for the various interactions.\n"
811" Key interactions of the exchange include:\n"
812" "
813msgstr ""
814
815#: investors.html.j2:62
816msgid ""
817"Create a <b>reserve</b> based on an incoming\n"
818" wire transfer from a customer."
819msgstr ""
820
821#: investors.html.j2:65
822msgid ""
823"Allow customers to withdraw (and refresh)\n"
824" digital coins from their reserve."
825msgstr ""
826
827#: investors.html.j2:68
828msgid "Accept and validate deposits from merchants."
829msgstr ""
830
831#: investors.html.j2:70
832msgid ""
833"Execute wire transfers to merchants in\n"
834" response to validated deposits."
835msgstr ""
836
837#: investors.html.j2:73
838msgid ""
839"Preserve and provide cryptographic proofs of\n"
840" correct operation for audits by financial regulators."
841msgstr ""
842
843#: merchants.html.j2:3
844msgid "Merchants"
845msgstr ""
846
847#: merchants.html.j2:12
848msgid "Advantages for merchants"
849msgstr ""
850
851#: merchants.html.j2:16
852msgid "Fast"
853msgstr ""
854
855#: merchants.html.j2:18
856msgid ""
857"Processing transactions with Taler is fast, allowing you\n"
858"\t to confirm the transaction with your customer virtually "
859"immediately.\n"
860"\t Your customers will appreciate that they do not have to type in "
861"credit\n"
862"\t card information and play the &quot;verified by&quot; game. By "
863"making payments\n"
864"\t significantly more convenient for your customers, you may be able "
865"to\n"
866"\t use Taler for small transactions that would not work with credit "
867"card\n"
868"\t payments due to the mental overhead for customers."
869msgstr ""
870
871#: merchants.html.j2:29
872msgid ""
873"You never learn sensitive customer information. You need\n"
874"\t to ensure that your website provides the correct account "
875"information\n"
876"\t for your business, and that you correctly validate the payment\n"
877"\t confirmations from the Taler exchange. As a result, you will have"
878"\n"
879"\t cryptographic proof of payment for the specific contracts you "
880"entered\n"
881"\t with your customers, and cryptographically signed confirmations "
882"from\n"
883"\t the Taler exchange about the deposits. Taler does not require you "
884"to\n"
885"\t undergo any particular security audits, processes or procedures, "
886"as\n"
887"\t you never handle sensitive customer information. Your systems "
888"will\n"
889"\t have cryptographically signed contracts which you can use in court"
890" in\n"
891"\t case of disputes."
892msgstr ""
893
894#: merchants.html.j2:42
895msgid "Free Software"
896msgstr ""
897
898#: merchants.html.j2:44
899msgid ""
900"Taler is free software, and you can use the\n"
901"\t liberally-licensed reference code as a starting point to integrate"
902"\n"
903"\t Taler into your services. To use Taler, you do not need to pay "
904"license\n"
905"\t fees, and the free software development model will ensure that you"
906" can\n"
907"\t select from many competent developers to help you with your\n"
908"\t integration."
909msgstr ""
910
911#: merchants.html.j2:54
912msgid "Low Fees"
913msgstr ""
914
915#: merchants.html.j2:56
916msgid ""
917"Taler is designed to minimize the work the exchange needs to\n"
918"\t perform. Combined with Taler's strong security which prevents "
919"fraud,\n"
920"\t exchanges can operate with very low overhead and thus low "
921"transaction\n"
922"\t fees. Given Taler's free software exchange reference "
923"implementation,\n"
924"\t competition among exchanges will ensure fair, low transaction fees"
925" for\n"
926"\t merchants."
927msgstr ""
928
929#: merchants.html.j2:64
930msgid "Flexible"
931msgstr ""
932
933#: merchants.html.j2:66
934msgid ""
935"Taler can be used for different currencies (such as Euros\n"
936"\t or US Dollars) and different payment models limited only by what "
937"the\n"
938"\t exchange supports in its interactions."
939msgstr ""
940
941#: merchants.html.j2:71
942msgid "Ethical"
943msgstr ""
944
945#: merchants.html.j2:73
946msgid ""
947"Taler does not support tax evasion or money laundering, and is\n"
948" also not a pyramid scheme or speculative investment. "
949"Taler's\n"
950" protocols are efficient and do not waste energy. Taler "
951"encourages\n"
952" competition by providing an open standard and free software\n"
953" reference implementations."
954msgstr ""
955
956#: merchants.html.j2:81
957msgid "Taler as seen by merchants"
958msgstr ""
959
960#: merchants.html.j2:83
961msgid ""
962"Merchants supporting the Taler system need to integrate\n"
963" some relatively simple logic into their transaction processing\n"
964" system.\n"
965" Typical steps performed by the merchant system are:\n"
966" "
967msgstr ""
968
969#: merchants.html.j2:92
970msgid ""
971"The new logic detects when a customer's system\n"
972" supports Taler and then needs to send a cryptographically "
973"signed\n"
974" version of the proposed contract in a simple JSON format to"
975"\n"
976" the customer.\n"
977" The message also includes salted, hashed wire details for\n"
978" the merchant, as well as restrictions as to which exchange "
979"operators\n"
980" the merchant is willing to deal with."
981msgstr ""
982
983#: merchants.html.j2:100
984msgid ""
985"The customer sends a signed response which states\n"
986" that certain digital coins now belong to the merchant to "
987"both\n"
988" signal acceptance of the deal as well as to pay the "
989"respective\n"
990" amount (bottom)."
991msgstr ""
992
993#: merchants.html.j2:105
994msgid ""
995"The merchant then forwards the signed messages\n"
996" received from the customer to the exchange, together with "
997"its\n"
998" wire details and the salt (without hashing). The exchange"
999" verifies\n"
1000" the details and sends a signed confirmation (or an error\n"
1001" message) to the merchant. The merchant checks that the\n"
1002" exchange's signature is valid, sends a confirmation to the"
1003"\n"
1004" customer and executes the contract-specific business logic."
1005msgstr ""
1006
1007#: merchants.html.j2:113
1008msgid ""
1009"The exchange performs wire transfers corresponding to\n"
1010" the claims deposited by the merchant. Note that the "
1011"exchange may\n"
1012" charge fees for the deposit operation, hence merchants may"
1013"\n"
1014" impose limits restricting the set of exchange operators "
1015"they are\n"
1016" willing to deal with, for example by imposing a bound on\n"
1017" deposit fees."
1018msgstr ""
1019
1020#: merchants.html.j2:123
1021msgid "Manuals for merchants"
1022msgstr ""
1023
1024#: news.html.j2:3 news.html.j2:12
1025msgid "News"
1026msgstr ""
1027
1028#: wallet.html.j2:5
1029msgid "Wallet"
1030msgstr ""
1031
1032#: common/footer.inc.j2:3
1033msgid ""
1034"This page was created using <a href='https://www.gnu.org/'>Free "
1035"Software</a> only."
1036msgstr ""
1037
1038#: common/navigation.inc.j2:12
1039msgid "<a href='/'>Home</a>"
1040msgstr ""
1041
1042#: common/navigation.inc.j2:13
1043msgid "<a href='https://demo.taler.net/' target='_blank'>Demo</a>"
1044msgstr ""
1045
1046#: common/navigation.inc.j2:14
1047msgid "<a href='/citizens'>Citizens</a>"
1048msgstr ""
1049
1050#: common/navigation.inc.j2:15
1051msgid "<a href='/merchants'>Merchants</a>"
1052msgstr ""
1053
1054#: common/navigation.inc.j2:16
1055msgid "<a href='/governments'>Governments</a>"
1056msgstr ""
1057
1058#: common/navigation.inc.j2:17
1059msgid "<a href='/investors'>Operators</a>"
1060msgstr ""
1061
1062#: common/navigation.inc.j2:18
1063msgid "<a href='/developers'>Developers</a>"
1064msgstr ""
1065
1066#: common/navigation.inc.j2:19
1067msgid "<a href='/about'>About&nbsp;us</a>"
1068msgstr ""
1069