summaryrefslogtreecommitdiff
path: root/locale/en/LC_MESSAGES/messages.po
blob: b6b62a09e0106fcf508b6c18220d71ec7ec7f6c5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
"POT-Creation-Date: 2019-06-27 13:33+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"
"Language: en\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n!=1)\n"
"Generated-By: Babel 2.3.4\n"

#: architecture.html.j2:6
msgid "Taler System Architecture"
msgstr ""

#: bibliography.html.j2:4
msgid "GNU Taler Bibliography"
msgstr ""

#: bibliography.html.j2:9 bibliography.html.j2:16 bibliography.html.j2:23
#: bibliography.html.j2:29
msgid "by"
msgstr ""

#: bibliography.html.j2:16 bibliography.html.j2:23 bibliography.html.j2:29
#: common/footer.j2.inc:30
msgid "and"
msgstr ""

#: bibliography.html.j2:30
msgid "available upon request"
msgstr ""

#: contact.html.j2:6
msgid "Contact information"
msgstr ""

#: contact.html.j2:13
msgid "The mailing list"
msgstr ""

#: contact.html.j2:15
msgid ""
"An archived, public mailing list for GNU Taler is hosted at <a href="
"\"https://lists.gnu.org/mailman/listinfo/taler\">https://lists.gnu.org/"
"mailman/listinfo/taler</a>. You can send messages to the list at <a href="
"\"mailto:taler@gnu.org\">taler@gnu.org</a>."
msgstr ""

#: contact.html.j2:25
msgid "Contacting individuals"
msgstr ""

#: contact.html.j2:27
msgid ""
"Team members are generally reachable at <tt>LASTNAME@taler.net</tt>. All of "
"us support receiving GnuPG encrypted e-mails."
msgstr ""

#: contact.html.j2:36
msgid "Reporting bugs"
msgstr ""

#: contact.html.j2:38
msgid ""
"We track open feature requests and bugs in our <a href=\"https://gnunet.org/"
"bugs/\">Bug tracker</a>, which is shared with the GNUnet project. You can "
"also report bugs or feature requests to the mailing list."
msgstr ""

#: contact.html.j2:49
msgid "Executive team"
msgstr ""

#: contact.html.j2:51
msgid ""
"For non-technical commercial requests, please contact <tt>ceo AT taler.net</"
"tt>."
msgstr ""

#: copyright.html.j2:6
msgid "Copyright Assignment"
msgstr ""

#: copyright.html.j2:8
msgid ""
"<p>Contributors to GNU Taler with Git access must sign the <a href=\"/pdf/"
"copyright.pdf\">copyright assignment</a> to ensure that the <a href="
"\"https://gnunet.org/git/gnunet-ev.git/tree/gnunet_taler_agreement.tex"
"\">GNUnet e.V. --- Taler Systems SA agreement on licensing and collaborative "
"development</a> of the GNUnet and GNU Taler projects is satisfied.</p>"
msgstr ""

#: copyright.html.j2:17
msgid ""
"<p>The agreements ensure that the code will continue to be made available "
"under free software licenses, but gives developers the freedom to move code "
"between GNUnet and GNU Taler without worrying about licenses and the company "
"the ability to dual-license (for example, so that we can distribute via App-"
"stores that are hostile to free software).</p>"
msgstr ""

#: copyright.html.j2:25
msgid ""
"<p>Minor contributions (basically, anyone without Git access) do not require "
"copyright assignment. Pseudonymous contributions are accepted, in this case "
"simply sign the agreement with your pseudonym. Scanned copies are "
"sufficient, but snail mail is preferred.</p>"
msgstr ""

#: developers.html.j2:5
msgid "Taler for developers"
msgstr ""

#: developers.html.j2:12 merchants.html.j2:58
msgid "Free"
msgstr ""

#: developers.html.j2:15
msgid ""
"GNU Taler is free software implementing an open protocol. Anybody is welcome "
"to integrate our reference implementation into their applications. Different "
"components of Taler are being made available under different licenses. The "
"Affero GPLv3+ is used for the exchange, the LGPLv3+ is used for reference "
"code demonstrating integration with merchant platforms, and licenses like "
"GPLv3+ are used for wallets and related customer-facing software. We are "
"open for constructive suggestions for maximizing the adoption of this "
"payment platform."
msgstr ""

#: developers.html.j2:32
msgid "RESTful"
msgstr ""

#: developers.html.j2:35
msgid ""
"Taler is designed to work on the Internet. To ensure that Taler payments can "
"work with restrictive network setups, Taler uses a RESTful protocol over "
"HTTP or HTTPS. Taler's security does not depend upon the use of HTTPS, but "
"obviously merchants may choose to offer HTTPS for consistency and because it "
"generally is better for privacy compared to HTTP. Taler uses JSON to encode "
"structure data, making it easy to integrate Taler with existing Web "
"applications. Taler's protocol is documented in detail at <a href=\"https://"
"docs.taler.net/\">docs.taler.net</a>."
msgstr ""

#: developers.html.j2:58
msgid "Code"
msgstr ""

#: developers.html.j2:61
msgid ""
"Taler is currently primarily developed by a research team at <a href="
"\"http://www.inria.fr/\">Inria</a> and <a href=\"https://gnunet.org/"
"\">GNUnet</a>. However, contributions from anyone are welcome. Our Git "
"repositories can be cloned using the Git and HTTP access methods against "
"<tt>git.taler.net</tt> with the name of the respective repository. A list of "
"repositories can be found in our <a href=\"https://git.taler.net/\">GitWeb</"
"a>."
msgstr ""

#: developers.html.j2:75
msgid "Documentation"
msgstr ""

#: developers.html.j2:78
msgid ""
"In addition to this website, the <a href=\"https://git.taler.net/"
"\">documented code</a> and the <a href=\"https://docs.taler.net/\">API "
"documentation</a>. Technical papers can be found in our <a href="
"\"bibliography.html\">bibliography</a>."
msgstr ""

#: developers.html.j2:88
msgid "Discussion"
msgstr ""

#: developers.html.j2:91
msgid ""
"We have a mailing list for developer discussions. You can subscribe to or "
"read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo/"
"taler\">http://lists.gnu.org/mailman/listinfo/taler</a>."
msgstr ""

#: developers.html.j2:101
msgid "Regression Testing"
msgstr ""

#: developers.html.j2:104
msgid ""
"We have <a href=\"https://buildbot.net/\">Buildbot</a> automation tests to "
"detect regressions and check for portability at <a href=\"https://buildbot."
"taler.net/\">buildbot.taler.net</a>."
msgstr ""

#: developers.html.j2:113
msgid "Code Coverage Analysis"
msgstr ""

#: developers.html.j2:116
msgid ""
"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\">LCOV</a> to "
"analyze the code coverage of our tests, the results are available at <a href="
"\"https://lcov.taler.net/\">lcov.taler.net</a>."
msgstr ""

#: developers.html.j2:131
msgid "Technical Presentation"
msgstr ""

#: developers.html.j2:134 investors.html.j2:88
msgid "Download"
msgstr ""

#: developers.html.j2:150
msgid "Taler system overview"
msgstr ""

#: developers.html.j2:155
msgid ""
"The Taler system consists of protocols executed among a number of actors as "
"illustrated in the illustration on the right. Typical transactions involve "
"the following steps:"
msgstr ""

#: developers.html.j2:162
msgid "system overview"
msgstr ""

#: developers.html.j2:165
msgid ""
"A customer instructs his <b>bank</b> to transfer funds from his account to "
"the Taler exchange (top left). In the subject of the transaction, he "
"includes an authentication token from his electronic <b>wallet</b>. In Taler "
"terminology, the customer creates a reserve at the exchange."
msgstr ""

#: developers.html.j2:177
msgid ""
"Once the exchange has received the wire transfer, it allows the customer's "
"electronic wallet to <b>withdraw</b> electronic coins. The electronic coins "
"are digital representations of the original currency from the transfer. It "
"is important to note that the exchange does not learn the &quot;serial "
"numbers&quot; of the coins created in this process, so it cannot tell later "
"which customer purchased what at which merchant. The use of Taler does not "
"change the currency or the total value of the funds (except for fees which "
"the exchange may charge for the service)."
msgstr ""

#: developers.html.j2:195
msgid ""
"Once the customer has the digital coins in his wallet, the wallet can be "
"used to <b>spend</b> the coins with merchant portals that support the Taler "
"payment system and accept the respective exchange as a business partner "
"(bottom arrow). This creates a digital contract signed by the customer's "
"coins and the merchant. If necessary, the customer can later use this "
"digitally signed contract in a court of law to prove the exact terms of the "
"contract and that he paid the respective amount. The customer does not learn "
"the banking details of the merchant, and Taler does not require the merchant "
"to learn the identity of the customer. Naturally, the customer can spend any "
"fraction of his digital coins (the system takes care of customers getting "
"change)."
msgstr ""

#: developers.html.j2:217
msgid ""
"Merchants receiving digital coins <b>deposit</b> the respective claims that "
"resulted from the contract signing with the customer at the exchange to "
"redeem the coins. The deposit step does not reveal the details of the "
"contract between the customer and the merchant or the identity of the "
"customer to the exchange in any way. However, the exchange does learn the "
"identity of the merchant via the provided bank routing information. The "
"merchant can, for example when compelled by the state for taxation, provide "
"information linking the individual deposit to the respective contract signed "
"by the customer. Thus, the exchange's database allows the state to enforce "
"that merchants pay applicable taxes (and do not engage in illegal contracts)."
msgstr ""

#: developers.html.j2:240
msgid ""
"Finally, the exchange transfers funds corresponding to the digital coins "
"redeemed by the merchants to the merchant's <b>bank</b> account. The "
"exchange may combine multiple small transactions into one larger bank "
"transfer. The merchant can query the exchange about the relationship between "
"the bank transfers and the individual claims that were deposited."
msgstr ""

#: developers.html.j2:254
msgid ""
"Most importantly, the exchange keeps cryptographic proofs that allow it to "
"demonstrate that it is operating correctly to third parties. The system "
"requires an external <b>auditor</b>, such as a government-appointed "
"financial regulatory body, to frequently verify the exchange's databases and "
"check that its bank balance matches the total value of the remaining coins "
"in circulation."
msgstr ""

#: developers.html.j2:269
msgid ""
"Without the auditor, the exchange operators could embezzle funds they are "
"holding in reserve. Customers and merchants cannot cheat each other or the "
"exchange. If any party's computers are compromised, the financial damage is "
"limited to the respective party and proportional to the funds they have in "
"circulation during the period of the compromise."
msgstr ""

#: faq.html.j2:5
msgid "How is Taler related to Bitcoin or Blockchains?"
msgstr ""

#: faq.html.j2:6
msgid ""
"<p>Taler does not require any Blockchain technology, and is also not based "
"on proof-of-work or any other distributed consensus mechanism. Instead, "
"Taler is based on blind signatures. However, it is theoretically possible to "
"combine Taler with peer-to-peer crypto-currencies like Bitcoin.</p>"
msgstr ""

#: faq.html.j2:13
msgid ""
"<p>It would be possible, however, to withdraw coins denominated in Bitcoin "
"into a Taler wallet (with an appropriate exchange), which would give some "
"benefits over plain Bitcoin, such as instant confirmation times.</p>"
msgstr ""

#: faq.html.j2:20
msgid "Where is the balance in my wallet stored?"
msgstr ""

#: faq.html.j2:21
msgid ""
"<p>Your wallet stores digital coins and thus ultimately your computer holds "
"your balance. The exchange keeps funds matching all unspent coins in an "
"escrow bank account.</p>"
msgstr ""

#: faq.html.j2:27
msgid "What if my wallet is lost?"
msgstr ""

#: faq.html.j2:28
msgid ""
"<p>Since the digital coins of value in your wallet are anonymized, the "
"exchange can not assist you in recovering a lost or stolen wallet. Just like "
"with a physical wallet for cash, you are responsible for keeping it safe.</p>"
msgstr ""

#: faq.html.j2:34
msgid ""
"<p>The risk of losing a wallet can be mitigated by making backups or keeping "
"the balance reasonably low.</p>"
msgstr ""

#: faq.html.j2:39
msgid "What if my computer is hacked?"
msgstr ""

#: faq.html.j2:40
msgid ""
"<p>In case of a compromise of one of your devices, an attacker can spend "
"coins from your wallet. Checking your balance might reveal to you that your "
"device has been compromised.</p>"
msgstr ""

#: faq.html.j2:46
msgid "Can I send money to my friend with Taler?"
msgstr ""

#: faq.html.j2:47
msgid ""
"<p>If your friend provides goods or services for you in exchange for a "
"payment, they can easily set up a Taler merchant and receive the payment in "
"their bank account.</p>"
msgstr ""

#: faq.html.j2:52
msgid ""
"<p>Future versions of the Taler wallet may allow exchanging coins among "
"friends directly as well.</p>"
msgstr ""

#: faq.html.j2:58
msgid "How does Taler handle payments in different currencies?"
msgstr ""

#: faq.html.j2:59
msgid ""
"<p>Taler wallets can store digital coins corresponding to multiple different "
"currencies such as the Euro, US Dollars or Bitcoins.</p>"
msgstr ""

#: faq.html.j2:63
msgid "<p>Taler currently does not offer conversion between currencies.</p>"
msgstr ""

#: faq.html.j2:67
msgid "How does Taler protect my privacy?"
msgstr ""

#: faq.html.j2:68
msgid ""
"<p>Your wallet stores digital coins that are <a href=\"https://en.wikipedia."
"org/wiki/Blind_signature\">blindly signed</a> by an exchange. The use of a "
"blind signature protects your privacy as it prevents the exchange from "
"knowing which coin it signed for which customer.</p>"
msgstr ""

#: faq.html.j2:79
msgid "How much does it cost?"
msgstr ""

#: faq.html.j2:80
msgid ""
"<p>The Taler protocol allows any exchange to set its own fee structure, "
"allowing operators to set fees for withdrawing, depositing, refreshing or "
"refunding coins. Operators can also charge fees for closing reserves and for "
"(aggregated) wire transfers to merchants. Merchants may choose to cover some "
"of the fees customers incur. Actual transaction costs are estimated around "
"0.001 cent/transaction (at high transaction rates, amortized over billions "
"of transactions, excluding migration costs). Note that this is an early "
"estimate, details may depend on hosting and backup requirements from the "
"regulator and could thus easily be 10x higher.</p>"
msgstr ""

#: faq.html.j2:95
msgid "Does Taler work with international payments?"
msgstr ""

#: faq.html.j2:96
msgid ""
"<p>Taler's wallet supports multiple currencies, but the system currently "
"does not support conversion between currencies. However, in principle an "
"entity that accepts deposits in one currency and allows withdrawals in "
"another currency could be created. Still, the regulatory hurdles in this "
"case tend to be particularly complex. The focus for Taler is on day-to-day "
"payments, so we have no plans to support currency conversion in the near "
"future.</p>"
msgstr ""

#: faq.html.j2:109
msgid "How does Taler relate to the (European) Electronic Money Directive?"
msgstr ""

#: faq.html.j2:110
msgid ""
"<p>We believe the European Electronic Money Directive provides part of the "
"regulatory framework a Taler exchange with coins denominated in Euros would "
"have to follow.</p>"
msgstr ""

#: faq.html.j2:118
msgid ""
"What bank would guarantee the conversion between Taler coins and bank money "
"in regular bank accounts?"
msgstr ""

#: faq.html.j2:119
msgid ""
"<p>The exchange would be operated by a bank or in cooperation with a bank, "
"and that bank would hold the funds in escrow. Note that this bank could be a "
"regular bank or a central bank for a centrally banked electronic currency. "
"Regardless, the bank would fall under the respective banking regulations "
"establishing a reason why consumers would have faith in the conversion from "
"Taler coins into regular bank money.</p>"
msgstr ""

#: faq.html.j2:129
msgid ""
"To whom would consumers complain to in case of non-conversion or non-"
"compliance?"
msgstr ""

#: faq.html.j2:130
msgid ""
"<p>Any exchange should be audited by one or more independent auditors. "
"Merchants and consumer wallets will report certain issues automatically to "
"the auditors, but auditors may also provide a method for manual submission "
"of issues. The auditors are expected to make their reports available to the "
"respective regulatory authorities, or even the general public.</p>"
msgstr ""

#: faq.html.j2:140
msgid "Are there any projects already using Taler?"
msgstr ""

#: faq.html.j2:141
msgid ""
"<p>We are aware of several businesses running exploratory projects or having "
"developed working prototypes. We are also in discussions with several "
"regular banks as well as several central banks about the project. That said, "
"there are currently no products in the market yet, and we believe this would "
"be premature given the state of the project (see also <a href=\"https://"
"gnunet.org/bugs/\">our bugtracker</a> for a list of open issues).</p>"
msgstr ""

#: faq.html.j2:153
msgid "Does Taler support recurring payments?"
msgstr ""

#: faq.html.j2:155
msgid ""
"<p>Today, our wallet implementation does not support recurring payments. "
"Recurring payments, where some fixed amount is paid on a regular basis are "
"in theory possible with Taler, but they come with a few caveats. "
"Specifically, recurring payments can only work if the Taler wallet is "
"running and online around the desired time. Furthermore, given their "
"repetitive nature they are linkable, and could thus be used to deanonymize "
"the user making the recurring payment, for example by forcing the user "
"offline at the time of the payment and observing that it does then not "
"happen on time. Finally, the Taler wallet does not work with credit and thus "
"the user would have to make sure to carry a sufficient balance for the "
"recurring payment to be made. Still, they can be useful, and a future "
"version of the Taler wallet will likely support them. But this is not a "
"feature that we are targeting for Taler 1.0. at this time</p>"
msgstr ""

#: features.html.j2:41
msgid "Paying with Taler"
msgstr ""

#: features.html.j2:42
msgid ""
"<p>To pay with Taler, customers install an electronic wallet on their "
"device. Before the first payment, the desired currency must be added to the "
"wallet's balance by some other means of payment.</p> <p>Once the wallet is "
"charged, payments on websites take only one click, are never falsely "
"rejected by fraud detection and do not pose any risk of phishing or identity "
"theft.</p> <p><a href=\"https://demo.taler.net\">Try it yourself with the "
"interactive demo!</a></p>"
msgstr ""

#: features.html.j2:54
msgid "Receiving payments with Taler"
msgstr ""

#: features.html.j2:55
msgid ""
"<p>To receive Taler payments, a merchant needs a bank account in the desired "
"currency. We provide supporting software in various programming languages to "
"make the integration painless. The merchant's backend for Taler transaction "
"processing can run on the merchant's premises or be hosted by a third party."
"</p> <p>Merchant integration is simple, and customers can pay for products "
"without even having to register an account.</p> <p><a href=\"https://docs."
"taler.net\">See how merchant integration works in our developer "
"documentation!</a></p>"
msgstr ""

#: features.html.j2:74
msgid "Practical"
msgstr ""

#: features.html.j2:77
msgid ""
"Taler is easy to integrate with existing Web applications. Payments are "
"cryptographically secured and are confirmed within milliseconds with "
"extremely low transaction costs."
msgstr ""

#: features.html.j2:87
msgid "Stable"
msgstr ""

#: features.html.j2:90
msgid ""
"Taler does not introduce a new currency. Taler uses a digital wallet storing "
"coins and payment service providers with escrow accounts in existing "
"currencies. Thus, Taler's cryptographic coins correspond to existing "
"currencies, such as US Dollars, Euros or even Bitcoins."
msgstr ""

#: features.html.j2:101 governments.html.j2:58 merchants.html.j2:41
msgid "Secure"
msgstr ""

#: features.html.j2:104
msgid ""
"By design Taler does not suffer from many classes of security problems such "
"as phishing or counterfeit. Thanks to its security features, Taler never "
"rejects a legitimate customer due to a fraud-detection false positive."
msgstr ""

#: features.html.j2:116 governments.html.j2:25
msgid "Taxable"
msgstr ""

#: features.html.j2:119
msgid ""
"When using Taler, merchant's revenue is transparent for tax collection "
"authorities. Unlike cash and most digital currencies, Taler helps prevent "
"black markets. Taler is not suitable for illegal activities."
msgstr ""

#: features.html.j2:129
msgid "Private"
msgstr ""

#: features.html.j2:131
msgid ""
"When you pay with Taler, your identity does not have to be revealed. Just "
"like payments in cash, nobody else can track how you spent your electronic "
"money. However, you obtain a legally valid proof of payment."
msgstr ""

#: features.html.j2:142 governments.html.j2:88
msgid "Libre"
msgstr ""

#: features.html.j2:145
msgid ""
"Taler provides protocols and reference implementations that in principle "
"enables anybody to run their own payment infrastructure, be it individuals, "
"organizations or whole countries. Since the reference implementation is a <a "
"href=\"http://www.gnu.org/\">GNU</a> package, it will always remain free "
"software."
msgstr ""

#: financial-news.html.j2:6
msgid "Financial News"
msgstr ""

#: financial-news.html.j2:9
msgid ""
"This page explains (only in English) how Taler can change ongoing "
"developments in the financial industry."
msgstr ""

#: glossary.html.j2:6
msgid "auditor"
msgstr ""

#: glossary.html.j2:8
msgid ""
"trusted third party that verifies that the `exchange` is operating correctly"
msgstr ""

#: glossary.html.j2:12
msgid "bank"
msgstr ""

#: glossary.html.j2:14
msgid ""
"traditional financial service provider who offers wire `transfers` between "
"accounts"
msgstr ""

#: glossary.html.j2:18
msgid "coin"
msgstr ""

#: glossary.html.j2:20
msgid ""
"coins are individual token representing a certain amount of value, also "
"known as the `denomination` of the coin"
msgstr ""

#: glossary.html.j2:24
msgid "contract"
msgstr ""

#: glossary.html.j2:26
msgid "the proposal signed by the wallet."
msgstr ""

#: glossary.html.j2:30
msgid "denomination"
msgstr ""

#: glossary.html.j2:32
msgid ""
"unit of currency, specifies both the currency and the face value of a `coin`"
msgstr ""

#: glossary.html.j2:36
msgid "denomination key"
msgstr ""

#: glossary.html.j2:38
msgid ""
"RSA key used by the exchange to certify that a given `coin` is valid and of "
"a particular `denomination`"
msgstr ""

#: glossary.html.j2:42
msgid "deposit"
msgstr ""

#: glossary.html.j2:44
msgid ""
"operation by which a merchant passes coins to an exchange, expecting the "
"exchange to credit his `bank` account in the future using a wire `transfer`"
msgstr ""

#: glossary.html.j2:48
msgid "dirty"
msgstr ""

#: glossary.html.j2:50
msgid ""
"a `coin` is dirty if its public key may be known to an entity other than the "
"customer, thereby creating the danger of some entity being able to link "
"multiple transactions of coin's owner if the coin is not refreshed first"
msgstr ""

#: glossary.html.j2:54
msgid "exchange"
msgstr ""

#: glossary.html.j2:56
msgid ""
"Taler's payment service provider. Issues electronic `coins` during "
"`withdrawal` and redeems them when they are `deposited` by merchants."
msgstr ""

#: glossary.html.j2:60
msgid "extension"
msgstr ""

#: glossary.html.j2:62
msgid "implementation of a `wallet` for browsers"
msgstr ""

#: glossary.html.j2:66
msgid "fresh coin"
msgstr ""

#: glossary.html.j2:68
msgid "a `coin` is fresh if its public key is only known to the customer"
msgstr ""

#: glossary.html.j2:72
msgid "master key"
msgstr ""

#: glossary.html.j2:74
msgid ""
"offline key used by the exchange to certify denomination keys and message "
"signing keys"
msgstr ""

#: glossary.html.j2:78
msgid "message signing key"
msgstr ""

#: glossary.html.j2:80
msgid "key used by the exchange to sign online messages, other than coins"
msgstr ""

#: glossary.html.j2:84
msgid "offer"
msgstr ""

#: glossary.html.j2:86
msgid ""
"specification of the details of a transaction, specifies the payment "
"obligations for the customer (i.e. the amount), the deliverables of the "
"merchant and other related information, such as deadlines or locations; "
"However, it lacks some information that the backend is supposed to provide. "
"In other words, after the backend adds the missing information to the offer "
"and signs it, it becomes a proposal."
msgstr ""

#: glossary.html.j2:95
msgid "owner"
msgstr ""

#: glossary.html.j2:97
msgid "a `coin` is owned by the entity that knows the private key of the coin"
msgstr ""

#: glossary.html.j2:101
msgid "proof"
msgstr ""

#: glossary.html.j2:103
msgid ""
"message that cryptographically demonstrates that a particular claim is "
"correct"
msgstr ""

#: glossary.html.j2:107
msgid "proposal"
msgstr ""

#: glossary.html.j2:109
msgid "a sketch that has been completed and signed by the merchant backend."
msgstr ""

#: glossary.html.j2:113
msgid "reserve"
msgstr ""

#: glossary.html.j2:115
msgid ""
"funds set aside for future use; either the balance of a customer at the "
"exchange ready for `withdrawal`, or the funds kept in the exchange's bank "
"account to cover obligations from coins in circulation"
msgstr ""

#: glossary.html.j2:119
msgid "refreshing"
msgstr ""

#: glossary.html.j2:121
msgid ""
"operation by which a `dirty` `coin` is converted into one or more `fresh` "
"coins"
msgstr ""

#: glossary.html.j2:125
msgid "refund"
msgstr ""

#: glossary.html.j2:127
msgid ""
"operation by which a merchant steps back from the right to funds that he "
"obtained from a `deposit` operation, giving the right to the funds back to "
"the customer"
msgstr ""

#: glossary.html.j2:131
msgid "sharing"
msgstr ""

#: glossary.html.j2:133
msgid ""
"users can share ownership of a `coin` by sharing access to the coin's "
"private key, thereby allowing all co-owners to spend the coin at any time."
msgstr ""

#: glossary.html.j2:137
msgid "signing key"
msgstr ""

#: glossary.html.j2:139
msgid "see message signing key."
msgstr ""

#: glossary.html.j2:143
msgid "spending"
msgstr ""

#: glossary.html.j2:145
msgid ""
"operation by which a customer gives a merchant the right to `deposit` coins "
"in return for merchandise"
msgstr ""

#: glossary.html.j2:149
msgid "transfer"
msgstr ""

#: glossary.html.j2:151
msgid "method of sending funds between `bank` accounts"
msgstr ""

#: glossary.html.j2:155
msgid "transaction"
msgstr ""

#: glossary.html.j2:157
msgid ""
"method by which ownership is exclusively transferred from one entity to "
"another"
msgstr ""

#: glossary.html.j2:161
msgid "transaction id"
msgstr ""

#: glossary.html.j2:163
msgid "unique number by which a merchant identifies a `transaction`"
msgstr ""

#: glossary.html.j2:167
msgid "wallet"
msgstr ""

#: glossary.html.j2:169
msgid ""
"software running on a customer's computer; withdraws, stores and spends coins"
msgstr ""

#: glossary.html.j2:173
msgid "wire transfer"
msgstr ""

#: glossary.html.j2:175
msgid "see `transfer`"
msgstr ""

#: glossary.html.j2:179
msgid "wire transfer identifier"
msgstr ""

#: glossary.html.j2:181
msgid ""
"subject of a wire `transfer`; usually a random string to uniquely identify "
"the `transfer`"
msgstr ""

#: glossary.html.j2:185
msgid "withdrawal"
msgstr ""

#: glossary.html.j2:187
msgid ""
"operation by which a `wallet` can convert funds from a reserve to fresh coins"
msgstr ""

#: governments.html.j2:6
msgid "Advantages for Governments"
msgstr ""

#: governments.html.j2:8
msgid ""
"Taler provides accountability to ensure business operate legally, while also "
"respecting civil liberties of citizens. Taler is a payment system based on "
"open standards and free software. Taler needs governments as they set a "
"financial framework and act as trusted regulators. Taler contributes to "
"digital sovereignty in the critical financial infrastructure."
msgstr ""

#: governments.html.j2:28
msgid ""
"Taler was built with the goal of fighting corruption and supporting "
"taxation. With Taler, the receiver of any form of payment is easily "
"identified by the government, and the merchant can be compelled to provide "
"the contract that was accepted by the customer. Governments can use this "
"data to tax businesses and individuals based on their income, making tax "
"evasion and black markets less viable."
msgstr ""

#: governments.html.j2:41
msgid ""
"Thus, despite offering anonymity for citizens spending digital cash to buy "
"goods and services, Taler also ensures that the state can observe incoming "
"funds. This can be used to ensure businesses engage only in legal "
"activities, and do not evade income tax, sales tax or value-added tax. "
"However, this observational capability does not extend to the immediate "
"personal domain. In particular, monitoring does not cover shared access to "
"funds with trusted friends and family, or synchronizing wallets across "
"multiple devices."
msgstr ""

#: governments.html.j2:61
msgid ""
"Taler's payments are cryptographically secured. Thus, customers, merchants "
"and the Taler payment service provider (the exchange) can mathematically "
"demonstrate their lawful behavior in court in case of disputes. Financial "
"damages are strictly limited, improving economic security for individuals, "
"merchants, the exchange and the state."
msgstr ""

#: governments.html.j2:73
msgid ""
"As a payment service provider, the Taler exchange is subject to financial "
"regulation. Financial regulation and regular audits are critical to "
"establish trust. In particular, the Taler design mandates the existence of "
"an independent auditor who checks cryptographic proofs that accumulate at "
"the exchange to ensure that the escrow account is managed honestly. This "
"ensures that the exchange does not threaten the economy due to fraud."
msgstr ""

#: governments.html.j2:91
msgid ""
"Taler is free software implementing an open protocol standard. Thus, Taler "
"will enable competition and avoid the monopolization of payment systems that "
"threatens global political and financial stability today."
msgstr ""

#: governments.html.j2:101
msgid "Efficient"
msgstr ""

#: governments.html.j2:104
msgid ""
"Taler has an efficient design. Unlike Blockchain-based payment systems, such "
"as Bitcoin, Taler will not threaten the availability of national electric "
"grids or (significantly) contribute to environmental pollution."
msgstr ""

#: governments.html.j2:120
msgid "Taler and regulation"
msgstr ""

#: governments.html.j2:122
msgid "Anti money laundering (AML)"
msgstr ""

#: governments.html.j2:123
msgid ""
"With Taler, income is visible and can be tied to the contract signed by both "
"parties."
msgstr ""

#: governments.html.j2:124
msgid "Know your customer (KYC)"
msgstr ""

#: governments.html.j2:125
msgid ""
"In Taler, payer and payee are known by their bank accounts when withdrawing "
"or depositing coins respectively"
msgstr ""

#: governments.html.j2:126
msgid "General Data Protection Regulation (GDPR)"
msgstr ""

#: governments.html.j2:127
msgid ""
"Taler cryptographically protects citizen's privacy, and by design implements "
"data minimization and privacy by default."
msgstr ""

#: governments.html.j2:128
msgid "Payment Services Directive (PSD2)"
msgstr ""

#: governments.html.j2:129
msgid ""
"Taler provides an open standard with public APIs contributing to a "
"competitive banking sector."
msgstr ""

#: governments.html.j2:137
msgid "Taler provides privacy and accountability"
msgstr ""

#: governments.html.j2:140
msgid ""
"Taler assumes governments can observe traditional wire transfers entering "
"and leaving the Taler payment system. Starting with the wire transfers, "
"governments can obtain:"
msgstr ""

#: governments.html.j2:148
msgid ""
"The total amount of digital currency withdrawn by a customer. The government "
"can impose limits on how much digital cash a customer can withdraw within a "
"given time frame."
msgstr ""

#: governments.html.j2:157
msgid "The income received by any merchant via the Taler system."
msgstr ""

#: governments.html.j2:164
msgid ""
"The exact details of the underlying contract that was signed between "
"customer and merchant. However, this information would typically not include "
"the identity of the customer."
msgstr ""

#: governments.html.j2:174
msgid ""
"The amounts of digital coins legitimately withdrawn by customers from the "
"exchange, the value of non-redeemed digital coins in customer's wallets, the "
"value and corresponding wire details of deposit operations performed by "
"merchants with the exchange, and the income of the exchange from transaction "
"fees."
msgstr ""

#: gsoc-codeless.html.j2:5
msgid "GSoC 2018: Codeless Payment"
msgstr ""

#: gsoc-codeless.html.j2:6
msgid ""
"Implemented by Shivam Kohli as part of GSoC 2018 under the mentoring and "
"guidance of Florian Dold."
msgstr ""

#: gsoc-codeless.html.j2:12
msgid "Overview"
msgstr ""

#: gsoc-codeless.html.j2:14
msgid ""
"Codeless payment is a component that sits between the seller's frontend and "
"the GNU Taler merchant backend. This component has a web interface, where "
"payment buttons are configured. Registered merchants can manage their "
"inventory and simultaneously create a 'Buy Now' button for a specific "
"product. This code can be directly copy pasted on the seller's frontend and "
"can be used for 'Pay with Taler'."
msgstr ""

#: gsoc-codeless.html.j2:23
msgid "Use Cases"
msgstr ""

#: gsoc-codeless.html.j2:24
msgid "The various use cases and features of codeless payment are:"
msgstr ""

#: gsoc-codeless.html.j2:28
msgid ""
"The primary use case is the registration of the merchant. The codeless "
"payment backend provides a secure django authenticated login to the "
"merchant. The registered merchant can add inventory (both digital as well as "
"physical) in their stocks. They can manage inventory and simultaneously "
"create a 'Buy Now' button for the product. The merchant also monitors the "
"orders placed and updates the status of the order which helps in shipment "
"tracking."
msgstr ""

#: gsoc-codeless.html.j2:33
msgid ""
"Merchant has the flexibility to add two types of inventory as follows: <ul> "
"<li>The merchant can upload digital inventory (like a PDF or HTML page) via "
"the codeless payments frontend and the user can then purchase it and view "
"the version hosted by the codeless payment frontend.</li> <li>The merchant "
"can add any physical inventory available in his stocks. While adding these "
"inventory, the seller is prompted to add minimum quantity of product that is "
"required to be maintained in the stock. Whenever the stocks run below this "
"limit the seller would be notified (currently this feature has not been "
"added but soon email notification would be added).</li> </ul>"
msgstr ""

#: gsoc-codeless.html.j2:42
msgid ""
"The buyers will access the seller's frontend where the code for the 'Buy "
"Now' button is present. When this button is triggered, they are redirected "
"to codeless payment backend and eventually redirected to the payment page. "
"After successful payment, the buyer can also track their shipment for "
"physical products or view the digital version hosted by the codeless payment "
"frontend."
msgstr ""

#: gsoc-codeless.html.j2:47
msgid ""
"The other use case of the codeless payment backend is to handle the event "
"when the 'Buy Now' button is triggered on the seller's frontend. To perform "
"the payment the backend communicates with merchant backend api. After "
"successful payment, the users are redirected to the fulfilment page."
msgstr ""

#: gsoc-codeless.html.j2:53
msgid "Dynamic Merchant Instance"
msgstr ""

#: gsoc-codeless.html.j2:57
msgid "Use Case Diagram"
msgstr ""

#: gsoc-codeless.html.j2:63
msgid "Link to the contributions made"
msgstr ""

#: gsoc-codeless.html.j2:66
msgid "Codeless Payment Backend"
msgstr ""

#: gsoc-codeless.html.j2:68
msgid "Documentation to dynamically manage Merchant Instances"
msgstr ""

#: gsoc-codeless.html.j2:77
msgid "Future Work"
msgstr ""

#: gsoc-codeless.html.j2:79
msgid ""
"The backend of codeless payment is very robust and can be easily extended as "
"per the requirements. It is adaptive to add new features to this framework. "
"But as per the discussion and the scope of this project, there are various "
"features that will be soon added in the Codeless Merchant Backend. The list "
"of future work is as follows:"
msgstr ""

#: gsoc-codeless.html.j2:84
msgid ""
"To send email notification to the merchant when the stocks run below a "
"certain limit. The minimum quantity required to be maintained in the stocks "
"is currently taken from the merchant(specific to each product) but no such "
"notification system is designed."
msgstr ""

#: gsoc-codeless.html.j2:90
msgid ""
"To add API access to the merchant backend via the codeless payment service. "
"Basically, it would be used as a hosting platform for multiple merchants. "
"There would be an additional user interface part in the codeless payment "
"service where a logged-in merchant can generate an API key. This API key can "
"be used to access the functionality of the merchant backend in a controlled "
"way. After requesting an API key, the page would display the generated key "
"and a base URL for the API to use by the seller, which is handled by the "
"codeless payments service."
msgstr ""

#: gsoc-codeless.html.j2:96
msgid ""
"Mapping every seller account to a separate merchant backend instance. This "
"is not required for a simple version of codeless payments, but as soon as "
"API access for sellers, this is a useful feature. The codeless payment "
"service then can also double as a hosting service for merchants."
msgstr ""

#: gsoc-codeless.html.j2:102
msgid ""
"To add various analytics for the merchant. Various analysis could be "
"performed on the orders placed for the respective merchant. Some of the "
"analysis that can be performed are displaying the most frequently purchased "
"product, some insights about the shipment tracking, analysis of products "
"based on delivery location, etc. For this part, dicussions and some more "
"research have to be done before proceeding to the implementation."
msgstr ""

#: gsoc-codeless.html.j2:114
msgid "Screenshots"
msgstr ""

#: investors.html.j2:6
msgid "Invest in Taler!"
msgstr ""

#: investors.html.j2:9
msgid ""
"We have created a company, Taler Systems SA in Luxembourg.<br> Please "
"contact <tt>invest@taler.net</tt> if you want to invest in Taler."
msgstr ""

#: investors.html.j2:24
msgid "The Team"
msgstr ""

#: investors.html.j2:27
msgid ""
"Our <a href=\"about.html\">team</a> combines world-class business leaders, "
"cryptographers, software engineers, civil-rights activists and academics. We "
"are unified by a vision of how payments should work and the goal of imposing "
"this vision upon the world."
msgstr ""

#: investors.html.j2:37
msgid ""
"We are currently supported by <a href=\"http://www.inria.fr/\">Inria</a>, "
"the French national institute for research in informatics and automation, "
"and the <a href=\"https://renewablefreedom.org/\">Renewable Freedom "
"Foundation</a>."
msgstr ""

#: investors.html.j2:45
msgid "The Technology"
msgstr ""

#: investors.html.j2:48
msgid ""
"All transactions in Taler are secured using <a href=\"bibliography.html"
"\">modern cryptography</a> and trust in all parties is minimized. Financial "
"damage is bounded (for customers, merchants and the exchange) even in the "
"case that systems are compromised and private keys are stolen. Databases can "
"be audited for consistency, resulting in either the detection of compromised "
"systems or the demonstration that participants were honest. Actual "
"transaction costs are fractions of a cent."
msgstr ""

#: investors.html.j2:63
msgid "The Business"
msgstr ""

#: investors.html.j2:66
msgid ""
"The scalable business model for Taler is the operation of the payment "
"service provider, which converts money from traditional payment systems "
"(MasterCard, SEPA, UPI, Visa, Bitcoin, ACH, SWIFT, etc.) to anonymous "
"electronic coins in the same currency. The customer can then redeem the "
"electronic coins at a merchant, who can exchange them for money represented "
"using traditional payment systems at the exchange. The exchange charges fees "
"to facilitate the transactions."
msgstr ""

#: investors.html.j2:85
msgid "The Business Case"
msgstr ""

#: investors.html.j2:91
msgid ""
"Our <a href=\"financial-news.html\">financial news</a> page explains in "
"English how Taler can impact current developments in the global payment "
"market."
msgstr ""

#: investors.html.j2:114
msgid "Running a Taler payment service operator"
msgstr ""

#: investors.html.j2:117
msgid ""
"The payment service operator runs the <em>Taler exchange</em>. The exchange "
"charges <b>transaction fees</b> to customers or merchants. Its operational "
"expenses are from wire transfers with the banking system and the operation "
"of the computing infrastructure."
msgstr ""

#: investors.html.j2:127
msgid ""
"Cryptographic operations, bandwidth and storage costs are less than 0.01 "
"cent per transaction."
msgstr ""

#: investors.html.j2:129
msgid ""
"Multiple Taler transactions can be aggregated into larger wire transfers to "
"merchants to minimize wire transfer costs."
msgstr ""

#: investors.html.j2:131
msgid ""
"Protocol allows the exchange to charge fees for any expensive operation "
"(withdraw, deposit, refresh, refund or aggregated wire transfers)."
msgstr ""

#: investors.html.j2:133
msgid "Partnership with banks establishes consumer trust."
msgstr ""

#: investors.html.j2:135
msgid "Partnership with free software community enables rapid deployment."
msgstr ""

#: merchants.html.j2:5
msgid "Advantages for Merchants"
msgstr ""

#: merchants.html.j2:8
msgid ""
"Taler is a cost-effective electronic payment system which provides you with "
"cryptographic proof that the payment worked correctly within milliseconds. "
"Your Web customers pay with previously unknown levels of convenience without "
"risk of fraud."
msgstr ""

#: merchants.html.j2:22
msgid "Fast"
msgstr ""

#: merchants.html.j2:25
msgid ""
"Processing transactions with Taler is fast, allowing you to confirm the "
"transaction with your customer virtually immediately. Your customers will "
"appreciate that they do not have to type in credit card information and play "
"the &quot;verified by&quot; game. By making payments significantly more "
"convenient for your customers, you may be able to use Taler for small "
"transactions that would not work with credit card payments due to the mental "
"overhead for customers."
msgstr ""

#: merchants.html.j2:44
msgid ""
"You will have cryptographic proof of payment from the Taler payment service "
"provider. With Taler you never handle sensitive customer account information "
"and thus do not have to undergo any particular security audits (such as PCI "
"DSS). Your systems will have customer contracts with qualified signatures "
"for all transactions which you can use in court in case of disputes."
msgstr ""

#: merchants.html.j2:61
msgid ""
"Taler is free software, and you can use the liberally-licensed reference "
"code as a starting point to integrate Taler into your services. To use "
"Taler, you do not need to pay license fees, and the free software "
"development model will ensure that you can select from many competing "
"integrators for support."
msgstr ""

#: merchants.html.j2:76
msgid "Cheap"
msgstr ""

#: merchants.html.j2:79
msgid ""
"Taler is uses efficient cryptographic constructions with low bandwidth and "
"storage requirements. Combined with Taler's strong security which makes "
"fraud impossible, Taler payment service providers can operate with very low "
"overhead and thus offer low transaction fees."
msgstr ""

#: merchants.html.j2:89
msgid "Flexible"
msgstr ""

#: merchants.html.j2:92
msgid ""
"Taler can be used for different currencies (such as Euros, US Dollars or "
"Bitcoins) and any amount, limited only by applicable regulation and what "
"denominations the payment service provider supports."
msgstr ""

#: merchants.html.j2:101
msgid "Ethical"
msgstr ""

#: merchants.html.j2:104
msgid ""
"Taler prevents tax evasion and money laundering. Taler's protocols are "
"efficient and do not use wasteful proof-of-work calculations. Taler "
"encourages transparency by providing an open standard and free software "
"reference implementations."
msgstr ""

#: merchants.html.j2:119
msgid "Manuals for merchants"
msgstr ""

#: merchants.html.j2:122
msgid "The GNU Taler merchant backend operator manual"
msgstr ""

#: merchants.html.j2:125
msgid "The GNU Taler Web shop integration tutorial (PHP)"
msgstr ""

#: merchants.html.j2:128
msgid "The GNU Taler Web shop integration tutorial (Python)"
msgstr ""

#: merchants.html.j2:140
msgid "The GNU Taler Merchant Backend"
msgstr ""

#: merchants.html.j2:142
msgid "Merchants process payments using the Taler backend:"
msgstr ""

#: merchants.html.j2:147
msgid ""
"The backend <b>signs</b> and <b>stores</b> the complete terms of offers made "
"by the merchant to customers. For this, the merchant's frontend needs to "
"give the customer's order in a JSON format to the backend."
msgstr ""

#: merchants.html.j2:156
msgid ""
"The backend <b>validates</b> payments received from the wallet and "
"<b>executes</b> them with the Taler payment service provider (the exchange). "
"For this, the merchant's frontend must pass the payment request through to "
"the Taler backend and check the HTTP status code that is returned."
msgstr ""

#: merchants.html.j2:167
msgid ""
"The backend can <b>list</b> completed transactions and <b>map</b> wire "
"transfers to sets of business transactions, including the exact terms of "
"each contract."
msgstr ""

#: merchants.html.j2:183
msgid "customer perspective"
msgstr ""

#: news.html.j2:16
msgid "More news"
msgstr ""

#: old-news.html.j2:6
msgid "Older News"
msgstr ""

#: old-news.html.j2:9
msgid "This page documents the GNU Taler history."
msgstr ""

#: press.html.j2:4
msgid "GNU Taler in the Press"
msgstr ""

#: schemafuzz.html.j2:6
msgid "SchemaFuzz"
msgstr ""

#: team.html.j2:16
msgid ""
"GNU maintainer. Network security &amp; privacy researcher. Software "
"architect."
msgstr ""

#: team.html.j2:21
msgid ""
"Entrepreneur, Investor, Fortune 100 CIO, IT company director in different "
"industries, …."
msgstr ""

#: team.html.j2:28
msgid "Applied cryptography. Contact to W3c &amp; Tor."
msgstr ""

#: team.html.j2:33
msgid "Theoretical foundations."
msgstr ""

#: team.html.j2:38
msgid "Founder of the GNU project. Ethical guidance and licensing."
msgstr ""

#: team.html.j2:45
msgid "PhD Student, TU Munich. Currently teaching."
msgstr ""

#: team.html.j2:50
msgid "PhD Student, Inria.."
msgstr ""

#: team.html.j2:55
msgid "Software engineer."
msgstr ""

#: team.html.j2:62
msgid "Sustainable business development."
msgstr ""

#: team.html.j2:66
msgid "Software engineer. Works on libebics."
msgstr ""

#: team.html.j2:72 team.html.j2:76 team.html.j2:80
msgid "Translator (Spanish)"
msgstr ""

#: team.html.j2:86 team.html.j2:90 team.html.j2:94
msgid "Translator (Italian)"
msgstr ""

#: team.html.j2:98
msgid "Translator (German)"
msgstr ""

#: team.html.j2:104
msgid "Hardware security module"
msgstr ""

#: team.html.j2:108
msgid "Risk management"
msgstr ""

#: team.html.j2:112
msgid "PhD student, TU Munich. Currently teaching."
msgstr ""

#: team.html.j2:118
msgid "Software engineer. Works on Android wallet."
msgstr ""

#: common/base.j2:5
msgid "GNU Taler"
msgstr ""

#: common/base.j2:6
msgid "Taxable Anonymous Libre Electronic Reserves"
msgstr ""

#: common/footer.j2.inc:11 common/navigation.j2.inc:18
msgid "Team"
msgstr ""

#: common/footer.j2.inc:12
msgid "Contact"
msgstr ""

#: common/footer.j2.inc:17
msgid "GSoc 2018"
msgstr ""

#: common/footer.j2.inc:18
msgid "Developer Resources"
msgstr ""

#: common/footer.j2.inc:23
msgid "FAQ"
msgstr ""

#: common/footer.j2.inc:24
msgid "Bibliography"
msgstr ""

#: common/footer.j2.inc:33
msgid ""
"We are grateful for support and free hosting of this site by <a href='http://"
"www.bfh.ch/'>BFH</a>"
msgstr ""

#: common/footer.j2.inc:35
msgid ""
"This page was created using <a href='https://www.gnu.org/'>Free Software</a> "
"only."
msgstr ""

#: common/navigation.j2.inc:15
msgid "Features"
msgstr ""

#: common/navigation.j2.inc:16
msgid "Principles"
msgstr ""

#: common/navigation.j2.inc:17
msgid "Docs"
msgstr ""