aboutsummaryrefslogtreecommitdiff
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.po1896
1 files changed, 491 insertions, 1405 deletions
diff --git a/locale/en/LC_MESSAGES/messages.po b/locale/en/LC_MESSAGES/messages.po
index bb3307fe..8e3d522d 100644
--- a/locale/en/LC_MESSAGES/messages.po
+++ b/locale/en/LC_MESSAGES/messages.po
@@ -1,23 +1,18 @@
1 1
2msgid "" 2msgid ""
3msgstr "" 3msgstr ""
4"Project-Id-Version: PROJECT VERSION Report-Msgid-Bugs-To: EMAIL@ADDRESS " 4"Project-Id-Version: PROJECT VERSION\n"
5"POT-Creation-Date: 2017-05-23 10:32+0200 PO-Revision-Date: YEAR-MO-DA "
6"HO:MI+ZONE Last-Translator: FULL NAME <EMAIL@ADDRESS> Language: en "
7"Language-Team: en <LL@li.org> Plural-Forms: nplurals=2; plural=(n!=1) "
8"MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-"
9"Transfer-Encoding: 8bit Generated-By: Babel 2.3.4 \n"
10"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" 5"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
11"POT-Creation-Date: 2017-06-02 13:48+0200\n" 6"POT-Creation-Date: 2017-05-23 10:32+0200\n"
12"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" 7"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
13"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" 8"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
14"Language: en\n" 9"Language: en\n"
15"Language-Team: en <LL@li.org>\n" 10"Language-Team: en <LL@li.org>\n"
16"Plural-Forms: nplurals=2; plural=(n != 1)\n" 11"Plural-Forms: nplurals=2; plural=(n!=1)\n"
17"MIME-Version: 1.0\n" 12"MIME-Version: 1.0\n"
18"Content-Type: text/plain; charset=utf-8\n" 13"Content-Type: text/plain; charset=utf-8\n"
19"Content-Transfer-Encoding: 8bit\n" 14"Content-Transfer-Encoding: 8bit\n"
20"Generated-By: Babel 2.4.0\n" 15"Generated-By: Babel 2.3.4\n"
21 16
22#: about.html.j2:8 17#: about.html.j2:8
23msgid "" 18msgid ""
@@ -114,9 +109,11 @@ msgstr ""
114 109
115#: citizens.html.j2:9 110#: citizens.html.j2:9
116msgid "" 111msgid ""
117"Taler largely functions like digital cash. You withdraw money from your " 112"Taler largely functions like digital cash. You\n"
118"bank account into your electronic wallet, and can henceforth spend " 113"withdraw money from your bank account into your\n"
119"digital cash. The electronic wallet can carry multiple currencies." 114"electronic wallet, and can henceforth spend digital\n"
115"cash. The electronic wallet can carry multiple\n"
116"currencies.\n"
120msgstr "" 117msgstr ""
121 118
122#: citizens.html.j2:25 governments.html.j2:58 index.html.j2:56 119#: citizens.html.j2:25 governments.html.j2:58 index.html.j2:56
@@ -126,10 +123,12 @@ msgstr ""
126 123
127#: citizens.html.j2:27 124#: citizens.html.j2:27
128msgid "" 125msgid ""
129"Taler uses modern cryptography, ensuring that there is no counterfeit. " 126"Taler uses modern cryptography, ensuring that there\n"
130"Your digital wallet is safer than your physical wallet. At most, you can " 127"is no counterfeit. Your digital wallet is safer\n"
131"lose its contents because your computer or mobile is irreparably damaged " 128"than your physical wallet. At most, you can lose\n"
132"or compromised. Unlike a physical wallet, you can make backups to secure " 129"its contents because your computer or mobile is\n"
130"irreparably damaged or compromised. Unlike a\n"
131"physical wallet, you can make backups to secure\n"
133"against data loss." 132"against data loss."
134msgstr "" 133msgstr ""
135 134
@@ -139,10 +138,12 @@ msgstr ""
139 138
140#: citizens.html.j2:39 139#: citizens.html.j2:39
141msgid "" 140msgid ""
142"Your transactions are private, neither the payment service provider nor " 141"Your transactions are private, neither the payment\n"
143"merchant needs to learn your identity. There is no need to give out " 142"service provider nor merchant needs to learn your\n"
144"credit card numbers or other sensitive information. The merchant will " 143"identity. There is no need to give out credit card\n"
145"only be able to do exactly the transaction you agreed to." 144"numbers or other sensitive information. The merchant\n"
145"will only be able to do exactly the transaction you\n"
146"agreed to."
146msgstr "" 147msgstr ""
147 148
148#: citizens.html.j2:50 149#: citizens.html.j2:50
@@ -151,10 +152,11 @@ msgstr ""
151 152
152#: citizens.html.j2:52 153#: citizens.html.j2:52
153msgid "" 154msgid ""
154"You will be able to withdraw money to replenish the digital coins in your" 155"You will be able to withdraw money to replenish the\n"
155" wallet using your credit card or wire transfers. Afterwards you can pay " 156"digital coins in your wallet using your credit card\n"
156"with one-click using the Taler wallet, which optionally keeps your " 157"or wire transfers. Afterwards you can pay with\n"
157"transaction history on your computer." 158"one-click using the Taler wallet, which optionally\n"
159"keeps your transaction history on your computer."
158msgstr "" 160msgstr ""
159 161
160#: citizens.html.j2:61 index.html.j2:42 162#: citizens.html.j2:61 index.html.j2:42
@@ -163,10 +165,12 @@ msgstr ""
163 165
164#: citizens.html.j2:63 166#: citizens.html.j2:63
165msgid "" 167msgid ""
166"Coins in your digital wallet will be of the same denomination as the cash" 168"Coins in your digital wallet will be of the same\n"
167" in your physical wallet. Taler is not a crypto-currency, so you do not " 169"denomination as the cash in your physical wallet.\n"
168"have to worry about cryto-currency related value fluctuations. Banking " 170"Taler is not a crypto-currency, so you do not have\n"
169"with Taler is subject to the usual government protections for financial " 171"to worry about cryto-currency related value\n"
172"fluctuations. Banking with Taler is subject to the\n"
173"usual government protections for financial\n"
170"services." 174"services."
171msgstr "" 175msgstr ""
172 176
@@ -177,8 +181,9 @@ msgstr ""
177#: citizens.html.j2:81 181#: citizens.html.j2:81
178msgid "" 182msgid ""
179"We currently provide a <a href=\"wallet.html\">wallet browser " 183"We currently provide a <a href=\"wallet.html\">wallet browser "
180"extension</a> for Chromium, Chrome, Firefox, Opera and Edge. Wallets for " 184"extension</a> for Chromium, Chrome, Firefox, Opera\n"
181"mobile phones and other platforms will be available in the future." 185"and Edge. Wallets for mobile phones and other platforms will be "
186"available in the future.\n"
182msgstr "" 187msgstr ""
183 188
184#: citizens.html.j2:88 189#: citizens.html.j2:88
@@ -188,7 +193,7 @@ msgstr ""
188#: citizens.html.j2:90 193#: citizens.html.j2:90
189msgid "" 194msgid ""
190"You can see how Taler works in practice by visiting our <a " 195"You can see how Taler works in practice by visiting our <a "
191"href=\"https://demo.taler.net\">demo page</a>." 196"href=\"https://demo.taler.net\">demo page</a>.\n"
192msgstr "" 197msgstr ""
193 198
194#: citizens.html.j2:103 199#: citizens.html.j2:103
@@ -196,32 +201,39 @@ msgid "The Taler Wallet for customers"
196msgstr "" 201msgstr ""
197 202
198#: citizens.html.j2:105 203#: citizens.html.j2:105
199msgid "Customers interact with the Taler system using the Taler wallet:" 204msgid ""
205"Customers interact with the Taler system using\n"
206"the Taler wallet:"
200msgstr "" 207msgstr ""
201 208
202#: citizens.html.j2:110 209#: citizens.html.j2:110
203msgid "" 210msgid ""
204"To <b>withdraw</b> electronic coins, the customer transfers funds from " 211"To <b>withdraw</b> electronic coins, the customer\n"
205"his bank account to the Taler payment service provider (the exchange). " 212"transfers funds from his bank account to the Taler\n"
206"The wire transfer subject must match a code identifying the customer's " 213"payment service provider (the exchange). The wire\n"
207"wallet. After the wire transfer is complete, the wallet will " 214"transfer subject must match a code identifying the\n"
208"automatically withdraw the coins from the exchange." 215"customer's wallet. After the wire transfer is\n"
216"complete, the wallet will automatically withdraw the\n"
217"coins from the exchange."
209msgstr "" 218msgstr ""
210 219
211#: citizens.html.j2:118 220#: citizens.html.j2:118
212msgid "" 221msgid ""
213"To <b>spend</b> electronic coins, a merchant must cause the wallet to " 222"To <b>spend</b> electronic coins, a merchant must\n"
214"display a proposal for some purchase. The wallet will ask the customer " 223"cause the wallet to display a proposal for some\n"
215"for one-click confirmation. Payment is then instant. Transaction " 224"purchase. The wallet will ask the customer for\n"
216"histories and digitally signed contracts can be preserved by the wallet." 225"one-click confirmation. Payment is then instant.\n"
226"Transaction histories and digitally signed contracts\n"
227"can be preserved by the wallet."
217msgstr "" 228msgstr ""
218 229
219#: citizens.html.j2:125 230#: citizens.html.j2:125
220msgid "" 231msgid ""
221"The customer can use the wallet to <b>review</b> his balance. The wallet " 232"The customer can use the wallet to <b>review</b> his\n"
222"can contain different currencies, and may be shared across devices. " 233"balance. The wallet can contain different\n"
223"Customers can make backups of the wallet to secure its contents against " 234"currencies, and may be shared across\n"
224"hardware failures." 235"devices. Customers can make backups of the wallet to\n"
236"secure its contents against hardware failures."
225msgstr "" 237msgstr ""
226 238
227#: contact.html.j2:6 239#: contact.html.j2:6
@@ -234,10 +246,12 @@ msgstr ""
234 246
235#: contact.html.j2:15 247#: contact.html.j2:15
236msgid "" 248msgid ""
237"An archived, public mailing list for GNU Taler is hosted at <a " 249"An archived, public mailing list for GNU Taler is\n"
250"hosted at\n"
251"<a "
238"href=\"https://lists.gnu.org/mailman/listinfo/taler\">https://lists.gnu.org/mailman/listinfo/taler</a>." 252"href=\"https://lists.gnu.org/mailman/listinfo/taler\">https://lists.gnu.org/mailman/listinfo/taler</a>."
239" You can send messages to the list at <a " 253" You can send messages to the list\n"
240"href=\"mailto:taler@gnu.org\">taler@gnu.org</a>." 254"at <a href=\"mailto:taler@gnu.org\">taler@gnu.org</a>.\n"
241msgstr "" 255msgstr ""
242 256
243#: contact.html.j2:25 257#: contact.html.j2:25
@@ -246,8 +260,9 @@ msgstr ""
246 260
247#: contact.html.j2:27 261#: contact.html.j2:27
248msgid "" 262msgid ""
249"Team members are generally reachable at <tt>LASTNAME@taler.net</tt>. All " 263"Team members are generally reachable at\n"
250"of us support receiving GnuPG encrypted e-mails." 264"<tt>LASTNAME@taler.net</tt>. All of us\n"
265"support receiving GnuPG encrypted e-mails.\n"
251msgstr "" 266msgstr ""
252 267
253#: contact.html.j2:36 268#: contact.html.j2:36
@@ -256,10 +271,11 @@ msgstr ""
256 271
257#: contact.html.j2:38 272#: contact.html.j2:38
258msgid "" 273msgid ""
259"We track open feature requests and bugs in our <a " 274"We track open feature requests and bugs in our\n"
260"href=\"https://gnunet.org/bugs/\">Bug tracker</a>, which is shared with " 275"<a href=\"https://gnunet.org/bugs/\">Bug tracker</a>,\n"
261"the GNUnet project. You can also report bugs or feature requests to the " 276"which is shared with the GNUnet project.\n"
262"mailing list." 277"You can also report bugs or feature requests to the\n"
278"mailing list.\n"
263msgstr "" 279msgstr ""
264 280
265#: contact.html.j2:49 281#: contact.html.j2:49
@@ -268,39 +284,8 @@ msgstr ""
268 284
269#: contact.html.j2:51 285#: contact.html.j2:51
270msgid "" 286msgid ""
271"For non-technical commercial requests, please contact <tt>ceo AT " 287"For non-technical commercial requests, please contact\n"
272"taler.net</tt>." 288"<tt>ceo AT taler.net</tt>.\n"
273msgstr ""
274
275#: copyright.html.j2:6
276msgid "Copyright Assignment"
277msgstr ""
278
279#: copyright.html.j2:8
280msgid ""
281"<p>Contributors to GNU Taler with Git access must sign the <a "
282"href=\"pdf/copyright.pdf\">copyright assignment</a> to ensure that the <a"
283" href=\"https://gnunet.org/git/gnunet-"
284"ev.git/tree/gnunet_taler_agreement.tex\">GNUnet e.V. --- Taler Systems SA"
285" agreement on licensing and collaborative development</a> of the GNUnet "
286"and GNU Taler projects is satisfied.</p>"
287msgstr ""
288
289#: copyright.html.j2:17
290msgid ""
291"<p>The agreements ensure that the code will continue to be made available"
292" under free software licenses, but gives developers the freedom to move "
293"code between GNUnet and GNU Taler without worrying about licenses and the"
294" company the ability to dual-license (for example, so that we can "
295"distribute via App-stores that are hostile to free software).</p>"
296msgstr ""
297
298#: copyright.html.j2:25
299msgid ""
300"<p>Minor contributions (basically, anyone without Git access) do not "
301"require copyright assignment. Pseudonymous contributions are accepted, in"
302" this case simply sign the agreement with your pseudonym. Scanned copies "
303"are sufficient, but snail mail is preferred.</p>"
304msgstr "" 289msgstr ""
305 290
306#: developers.html.j2:5 291#: developers.html.j2:5
@@ -313,14 +298,17 @@ msgstr ""
313 298
314#: developers.html.j2:15 299#: developers.html.j2:15
315msgid "" 300msgid ""
316"GNU Taler is free software implementing an open protocol. Anybody is " 301"GNU Taler is free software implementing an open\n"
317"welcome to integrate our reference implementation into their " 302"protocol. Anybody is welcome to integrate our reference\n"
318"applications. Different components of Taler are being made available " 303"implementation into their applications. Different\n"
319"under different licenses. The Affero GPLv3+ is used for the exchange, the" 304"components of Taler are being made available under\n"
320" LGPLv3+ is used for reference code demonstrating integration with " 305"different licenses. The Affero GPLv3+ is used for the\n"
321"merchant platforms, and licenses like GPLv3+ are used for wallets and " 306"exchange, the LGPLv3+ is used for reference code\n"
322"related customer-facing software. We are open for constructive " 307"demonstrating integration with merchant platforms, and\n"
323"suggestions for maximizing the adoption of this payment platform." 308"licenses like GPLv3+ are used for\n"
309"wallets and related customer-facing software. We are\n"
310"open for constructive suggestions for maximizing the\n"
311"adoption of this payment platform.\n"
324msgstr "" 312msgstr ""
325 313
326#: developers.html.j2:32 314#: developers.html.j2:32
@@ -329,14 +317,18 @@ msgstr ""
329 317
330#: developers.html.j2:35 318#: developers.html.j2:35
331msgid "" 319msgid ""
332"Taler is designed to work on the Internet. To ensure that Taler payments " 320"Taler is designed to work on the Internet. To\n"
333"can work with restrictive network setups, Taler uses a RESTful protocol " 321"ensure that Taler payments can work with\n"
334"over HTTP or HTTPS. Taler's security does not depend upon the use of " 322"restrictive network setups, Taler uses a RESTful\n"
335"HTTPS, but obviously merchants may choose to offer HTTPS for consistency " 323"protocol over HTTP or HTTPS. Taler's security does\n"
336"and because it generally is better for privacy compared to HTTP. Taler " 324"not depend upon the use of HTTPS, but obviously\n"
337"uses JSON to encode structure data, making it easy to integrate Taler " 325"merchants may choose to offer HTTPS for consistency\n"
338"with existing Web applications. Taler's protocol is documented in detail " 326"and because it generally is better for privacy\n"
339"at <a href=\"https://api.taler.net/\">api.taler.net</a>." 327"compared to HTTP. Taler uses JSON to encode\n"
328"structure data, making it easy to integrate Taler\n"
329"with existing Web applications. Taler's protocol\n"
330"is documented in\n"
331"detail at <a href=\"https://api.taler.net/\">api.taler.net</a>.\n"
340msgstr "" 332msgstr ""
341 333
342#: developers.html.j2:58 334#: developers.html.j2:58
@@ -345,13 +337,15 @@ msgstr ""
345 337
346#: developers.html.j2:61 338#: developers.html.j2:61
347msgid "" 339msgid ""
348"Taler is currently primarily developed by a research team at <a " 340"Taler is currently primarily developed by a\n"
349"href=\"http://www.inria.fr/\">Inria</a> and <a " 341"research team at <a href=\"http://www.inria.fr/\">Inria</a> and\n"
350"href=\"https://gnunet.org/\">GNUnet</a>. However, contributions from " 342"<a href=\"https://gnunet.org/\">GNUnet</a>. However,\n"
351"anyone are welcome. Our Git repositories can be cloned using the Git and " 343"contributions from anyone are welcome. Our Git\n"
352"HTTP access methods against <tt>git.taler.net</tt> with the name of the " 344"repositories can be cloned using the Git and HTTP\n"
353"respective repository. A list of repositories can be found in our <a " 345"access methods against <tt>git.taler.net</tt> with\n"
354"href=\"https://git.taler.net/\">GitWeb</a>." 346"the name of the respective repository. A list of\n"
347"repositories can be found in\n"
348"our <a href=\"https://git.taler.net/\">GitWeb</a>.\n"
355msgstr "" 349msgstr ""
356 350
357#: developers.html.j2:75 351#: developers.html.j2:75
@@ -360,10 +354,11 @@ msgstr ""
360 354
361#: developers.html.j2:78 355#: developers.html.j2:78
362msgid "" 356msgid ""
363"In addition to this website, the <a " 357"In addition to this website, the <a\n"
364"href=\"https://git.taler.net/\">documented code</a> and the <a " 358"href=\"https://git.taler.net/\">documented code</a> and\n"
365"href=\"https://api.taler.net/\">API documentation</a>. Technical papers " 359"the <a href=\"https://api.taler.net/\">API\n"
366"can be found in our <a href=\"bibliography.html\">bibliography</a>." 360"documentation</a>. Technical papers can be found in\n"
361"our <a href=\"bibliography.html\">bibliography</a>.\n"
367msgstr "" 362msgstr ""
368 363
369#: developers.html.j2:88 364#: developers.html.j2:88
@@ -372,9 +367,11 @@ msgstr ""
372 367
373#: developers.html.j2:91 368#: developers.html.j2:91
374msgid "" 369msgid ""
375"We have a mailing list for developer discussions. You can subscribe to or" 370"We have a mailing list for developer discussions.\n"
376" read the list archive at <a " 371"You can subscribe to or read the list archive at\n"
372"<a "
377"href=\"http://lists.gnu.org/mailman/listinfo/taler\">http://lists.gnu.org/mailman/listinfo/taler</a>." 373"href=\"http://lists.gnu.org/mailman/listinfo/taler\">http://lists.gnu.org/mailman/listinfo/taler</a>."
374"\n"
378msgstr "" 375msgstr ""
379 376
380#: developers.html.j2:101 377#: developers.html.j2:101
@@ -383,9 +380,10 @@ msgstr ""
383 380
384#: developers.html.j2:104 381#: developers.html.j2:104
385msgid "" 382msgid ""
386"We have <a href=\"https://buildbot.net/\">Buildbot</a> automation tests " 383"We have <a href=\"https://buildbot.net/\">Buildbot</a>\n"
387"to detect regressions and check for portability at <a " 384"automation tests to detect regressions and check for\n"
388"href=\"https://buildbot.taler.net/\">buildbot.taler.net</a>." 385"portability at <a\n"
386"href=\"https://buildbot.taler.net/\">buildbot.taler.net</a>.\n"
389msgstr "" 387msgstr ""
390 388
391#: developers.html.j2:113 389#: developers.html.j2:113
@@ -394,9 +392,11 @@ msgstr ""
394 392
395#: developers.html.j2:116 393#: developers.html.j2:116
396msgid "" 394msgid ""
397"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\">LCOV</a> " 395"We use\n"
398"to analyze the code coverage of our tests, the results are available at " 396"<a href=\"http://ltp.sourceforge.net/coverage/lcov.php\">LCOV</a>\n"
399"<a href=\"https://lcov.taler.net/\">lcov.taler.net</a>." 397"to analyze the code coverage of our tests, the\n"
398"results are available\n"
399"at <a href=\"https://lcov.taler.net/\">lcov.taler.net</a>.\n"
400msgstr "" 400msgstr ""
401 401
402#: developers.html.j2:126 402#: developers.html.j2:126
@@ -405,9 +405,11 @@ msgstr ""
405 405
406#: developers.html.j2:129 406#: developers.html.j2:129
407msgid "" 407msgid ""
408"We use <a href=\"https://gnunet.org/gauger\">Gauger</a> for performance " 408"We\n"
409"regression analysis of the exchange backend at <a " 409"use <a href=\"https://gnunet.org/gauger\">Gauger</a>\n"
410"href=\"https://gauger.taler.net/\">gauger.taler.net</a>." 410"for performance regression analysis of the exchange\n"
411"backend\n"
412"at <a href=\"https://gauger.taler.net/\">gauger.taler.net</a>.\n"
411msgstr "" 413msgstr ""
412 414
413#: developers.html.j2:145 415#: developers.html.j2:145
@@ -416,88 +418,120 @@ msgstr ""
416 418
417#: developers.html.j2:148 419#: developers.html.j2:148
418msgid "" 420msgid ""
419"The Taler system consists of protocols executed among a number of actors " 421"The Taler system consists of protocols executed among\n"
420"as illustrated in the illustration on the right. Typical transactions " 422"a number of actors as illustrated in the illustration on the right.\n"
421"involve the following steps:" 423"Typical transactions involve the following steps:\n"
422msgstr "" 424msgstr ""
423 425
424#: developers.html.j2:158 426#: developers.html.j2:158
425msgid "" 427msgid ""
426"A customer instructs his <b>bank</b> to transfer funds from his account " 428"A customer instructs his <b>bank</b> to\n"
427"to the Taler exchange (top left). In the subject of the transaction, he " 429"transfer funds from his account to the Taler\n"
428"includes an authentication token from his electronic <b>wallet</b>. In " 430"exchange (top left). In the subject of the\n"
429"Taler terminology, the customer creates a reserve at the exchange." 431"transaction, he includes an authentication\n"
432"token from his electronic <b>wallet</b>. In\n"
433"Taler terminology, the customer creates a\n"
434"reserve at the exchange.\n"
430msgstr "" 435msgstr ""
431 436
432#: developers.html.j2:170 437#: developers.html.j2:170
433msgid "" 438msgid ""
434"Once the exchange has received the wire transfer, it allows the " 439"Once the exchange has received the wire\n"
435"customer's electronic wallet to <b>withdraw</b> electronic coins. The " 440"transfer, it allows the customer's electronic\n"
436"electronic coins are digital representations of the original currency " 441"wallet to <b>withdraw</b> electronic coins.\n"
437"from the transfer. It is important to note that the exchange does not " 442"The electronic coins are digital\n"
438"learn the &quot;serial numbers&quot; of the coins created in this " 443"representations of the original currency from\n"
439"process, so it cannot tell later which customer purchased what at which " 444"the transfer. It is important to note that the\n"
440"merchant. The use of Taler does not change the currency or the total " 445"exchange does not learn the &quot;serial\n"
441"value of the funds (except for fees which the exchange may charge for the" 446"numbers&quot; of the coins created in this\n"
442" service)." 447"process, so it cannot tell later which customer\n"
448"purchased what at which merchant. The use of\n"
449"Taler does not change the currency or the total\n"
450"value of the funds (except for fees which the\n"
451"exchange may charge for the service).\n"
443msgstr "" 452msgstr ""
444 453
445#: developers.html.j2:188 454#: developers.html.j2:188
446msgid "" 455msgid ""
447"Once the customer has the digital coins in his wallet, the wallet can be " 456"Once the customer has the digital coins in his\n"
448"used to <b>spend</b> the coins with merchant portals that support the " 457"wallet, the wallet can be used to <b>spend</b>\n"
449"Taler payment system and accept the respective exchange as a business " 458"the coins with merchant portals that support\n"
450"partner (bottom arrow). This creates a digital contract signed by the " 459"the Taler payment system and accept the\n"
451"customer's coins and the merchant. If necessary, the customer can later " 460"respective exchange as a business partner\n"
452"use this digitally signed contract in a court of law to prove the exact " 461"(bottom arrow). This creates a digital contract\n"
453"terms of the contract and that he paid the respective amount. The " 462"signed by the customer's coins and the\n"
454"customer does not learn the banking details of the merchant, and Taler " 463"merchant. If necessary, the customer can later\n"
455"does not require the merchant to learn the identity of the customer. " 464"use this digitally signed contract in a court\n"
456"Naturally, the customer can spend any fraction of his digital coins (the " 465"of law to prove the exact terms of the contract\n"
457"system takes care of customers getting change)." 466"and that he paid the respective amount. The\n"
467"customer does not learn the banking details of\n"
468"the merchant, and Taler does not require the\n"
469"merchant to learn the identity of the\n"
470"customer. Naturally, the customer can spend any\n"
471"fraction of his digital coins (the system takes\n"
472"care of customers getting change).\n"
458msgstr "" 473msgstr ""
459 474
460#: developers.html.j2:210 475#: developers.html.j2:210
461msgid "" 476msgid ""
462"Merchants receiving digital coins <b>deposit</b> the respective claims " 477"Merchants receiving digital\n"
463"that resulted from the contract signing with the customer at the exchange" 478"coins <b>deposit</b> the respective claims\n"
464" to redeem the coins. The deposit step does not reveal the details of the" 479"that resulted from the contract signing with\n"
465" contract between the customer and the merchant or the identity of the " 480"the customer at the exchange to redeem the\n"
466"customer to the exchange in any way. However, the exchange does learn the" 481"coins. The deposit step does not reveal the\n"
467" identity of the merchant via the provided bank routing information. The " 482"details of the contract between the customer\n"
468"merchant can, for example when compelled by the state for taxation, " 483"and the merchant or the identity of the\n"
469"provide information linking the individual deposit to the respective " 484"customer to the exchange in any way. However,\n"
470"contract signed by the customer. Thus, the exchange's database allows the" 485"the exchange does learn the identity of the\n"
471" state to enforce that merchants pay applicable taxes (and do not engage " 486"merchant via the provided bank routing\n"
472"in illegal contracts)." 487"information. The merchant can, for example\n"
488"when compelled by the state for taxation,\n"
489"provide information linking the individual\n"
490"deposit to the respective contract signed by\n"
491"the customer. Thus, the exchange's database\n"
492"allows the state to enforce that merchants pay\n"
493"applicable taxes (and do not engage in illegal\n"
494"contracts).\n"
473msgstr "" 495msgstr ""
474 496
475#: developers.html.j2:233 497#: developers.html.j2:233
476msgid "" 498msgid ""
477"Finally, the exchange transfers funds corresponding to the digital coins " 499"Finally, the exchange transfers funds\n"
478"redeemed by the merchants to the merchant's <b>bank</b> account. The " 500"corresponding to the digital coins redeemed by\n"
479"exchange may combine multiple small transactions into one larger bank " 501"the merchants to the merchant's <b>bank</b>\n"
480"transfer. The merchant can query the exchange about the relationship " 502"account. The exchange may combine multiple\n"
481"between the bank transfers and the individual claims that were deposited." 503"small transactions into one larger bank\n"
504"transfer. The merchant can query the exchange\n"
505"about the relationship between the bank\n"
506"transfers and the individual claims that were\n"
507"deposited.\n"
482msgstr "" 508msgstr ""
483 509
484#: developers.html.j2:247 510#: developers.html.j2:247
485msgid "" 511msgid ""
486"Most importantly, the exchange keeps cryptographic proofs that allow it " 512"Most importantly, the exchange keeps\n"
487"to demonstrate that it is operating correctly to third parties. The " 513"cryptographic proofs that allow it to\n"
488"system requires an external <b>auditor</b>, such as a government-" 514"demonstrate that it is operating correctly to\n"
489"appointed financial regulatory body, to frequently verify the exchange's " 515"third parties. The system requires an\n"
490"databases and check that its bank balance matches the total value of the " 516"external <b>auditor</b>, such as a\n"
491"remaining coins in circulation." 517"government-appointed financial regulatory body,\n"
518"to frequently verify the exchange's databases\n"
519"and check that its bank balance matches the\n"
520"total value of the remaining coins in\n"
521"circulation.\n"
492msgstr "" 522msgstr ""
493 523
494#: developers.html.j2:262 524#: developers.html.j2:262
495msgid "" 525msgid ""
496"Without the auditor, the exchange operators could embezzle funds they are" 526"Without the auditor, the exchange operators\n"
497" holding in reserve. Customers and merchants cannot cheat each other or " 527"could embezzle funds they are holding in\n"
498"the exchange. If any party's computers are compromised, the financial " 528"reserve. Customers and merchants cannot cheat\n"
499"damage is limited to the respective party and proportional to the funds " 529"each other or the exchange. If any party's\n"
500"they have in circulation during the period of the compromise." 530"computers are compromised, the financial damage\n"
531"is limited to the respective party and\n"
532"proportional to the funds they have in\n"
533"circulation during the period of the\n"
534"compromise.\n"
501msgstr "" 535msgstr ""
502 536
503#: faq.html.j2:5 537#: faq.html.j2:5
@@ -506,17 +540,17 @@ msgstr ""
506 540
507#: faq.html.j2:6 541#: faq.html.j2:6
508msgid "" 542msgid ""
509"<p>Taler does not use any Blockchain technology or Bitcoin directly. " 543"<p>Taler does not use any Blockchain technology or Bitcoin directly.\n"
510"Taler is not based on proof-of-work or any other distributed consensus " 544"Taler is not based on proof-of-work or any other distributed consensus\n"
511"mechanism. Instead Taler is based on blind signatures.</p>" 545"mechanism. Instead Taler is based on blind signatures.</p>\n"
512msgstr "" 546msgstr ""
513 547
514#: faq.html.j2:11 548#: faq.html.j2:11
515msgid "" 549msgid ""
516"<p>It would be possible, however, to withdraw coins denominated in " 550"<p>It would be possible, however, to withdraw coins denominated in\n"
517"Bitcoin into a Taler wallet (with an appropriate exchange), which would " 551"Bitcoin into a Taler wallet (with an appropriate exchange), which\n"
518"give some benefits over plain Bitcoin, such as instant confirmation " 552"would give some benefits over plain Bitcoin, such as instant\n"
519"times.</p>" 553"confirmation times.</p>\n"
520msgstr "" 554msgstr ""
521 555
522#: faq.html.j2:18 556#: faq.html.j2:18
@@ -525,9 +559,9 @@ msgstr ""
525 559
526#: faq.html.j2:19 560#: faq.html.j2:19
527msgid "" 561msgid ""
528"<p>Your wallet stores digital coins and thus ultimately your computer " 562"<p>Your wallet stores digital coins and thus ultimately your computer\n"
529"holds your balance. The exchange keeps funds matching all unspent coins " 563"holds your balance. The exchange keeps funds matching all unspent\n"
530"in an escrow bank account.</p>" 564"coins in an escrow bank account.</p>\n"
531msgstr "" 565msgstr ""
532 566
533#: faq.html.j2:25 567#: faq.html.j2:25
@@ -536,16 +570,16 @@ msgstr ""
536 570
537#: faq.html.j2:26 571#: faq.html.j2:26
538msgid "" 572msgid ""
539"<p>Since the digital coins of value in your wallet are anonymized, the " 573"<p>Since the digital coins of value in your wallet are anonymized, the\n"
540"exchange can not assist you in recovering a lost or stolen wallet. Just " 574"exchange can not assist you in recovering a lost or stolen wallet.\n"
541"like with a physical wallet for cash, you are responsible for keeping it " 575"Just like with a physical wallet for cash, you are responsible for\n"
542"safe.</p>" 576"keeping it safe.</p>\n"
543msgstr "" 577msgstr ""
544 578
545#: faq.html.j2:32 579#: faq.html.j2:32
546msgid "" 580msgid ""
547"<p>The risk of losing a wallet can be mitigated by making backups or " 581"<p>The risk of losing a wallet can be mitigated by making backups or\n"
548"keeping the balance reasonably low.</p>" 582"keeping the balance reasonably low.</p>\n"
549msgstr "" 583msgstr ""
550 584
551#: faq.html.j2:37 585#: faq.html.j2:37
@@ -554,9 +588,9 @@ msgstr ""
554 588
555#: faq.html.j2:38 589#: faq.html.j2:38
556msgid "" 590msgid ""
557"<p>In case of a compromise of one of your devices, an attacker can spend " 591"<p>In case of a compromise of one of your devices, an attacker can\n"
558"coins from your wallet. Checking your balance might reveal to you that " 592"spend coins from your wallet. Checking your balance might reveal\n"
559"your device has been compromised.</p>" 593"to you that your device has been compromised.</p>\n"
560msgstr "" 594msgstr ""
561 595
562#: faq.html.j2:44 596#: faq.html.j2:44
@@ -565,15 +599,15 @@ msgstr ""
565 599
566#: faq.html.j2:45 600#: faq.html.j2:45
567msgid "" 601msgid ""
568"<p>If your friend provides goods or services for you in exchange for a " 602"<p>If your friend provides goods or services for you in exchange for a\n"
569"payment, they can easily set up a Taler merchant and receive the payment " 603"payment, they can easily set up a Taler merchant and receive the\n"
570"in their bank account.</p>" 604"payment in their bank account.</p>\n"
571msgstr "" 605msgstr ""
572 606
573#: faq.html.j2:50 607#: faq.html.j2:50
574msgid "" 608msgid ""
575"<p>Future versions of the Taler wallet may allow exchanging coins among " 609"<p>Future versions of the Taler wallet may allow exchanging coins\n"
576"friends directly as well.</p>" 610"among friends directly as well.</p>\n"
577msgstr "" 611msgstr ""
578 612
579#: faq.html.j2:56 613#: faq.html.j2:56
@@ -582,12 +616,12 @@ msgstr ""
582 616
583#: faq.html.j2:57 617#: faq.html.j2:57
584msgid "" 618msgid ""
585"<p>Taler wallets can store digital coins corresponding to multiple " 619"<p>Taler wallets can store digital coins corresponding to multiple\n"
586"different currencies such as the Euro, US Dollars or Bitcoins.</p>" 620"different currencies such as the Euro, US Dollars or Bitcoins.</p>\n"
587msgstr "" 621msgstr ""
588 622
589#: faq.html.j2:61 623#: faq.html.j2:61
590msgid "<p>Taler currently does not offer conversion between currencies.</p>" 624msgid "<p>Taler currently does not offer conversion between currencies.</p>\n"
591msgstr "" 625msgstr ""
592 626
593#: faq.html.j2:65 627#: faq.html.j2:65
@@ -596,11 +630,12 @@ msgstr ""
596 630
597#: faq.html.j2:66 631#: faq.html.j2:66
598msgid "" 632msgid ""
599"<p>Your wallet stores digital coins that are <a " 633"<p>Your wallet stores digital coins that are <a\n"
600"href=\"https://en.wikipedia.org/wiki/Blind_signature\">blindly signed</a>" 634"href=\"https://en.wikipedia.org/wiki/Blind_signature\">blindly\n"
601" by an exchange. The use of a blind signature protects your privacy as it" 635"signed</a> by an exchange. The use of a blind signature protects your\n"
602" prevents the exchange from knowing which coin it signed for which " 636"privacy as it prevents the exchange from knowing which coin it signed\n"
603"customer.</p>" 637"for which customer.</p>\n"
638"\n"
604msgstr "" 639msgstr ""
605 640
606#: glossary.html.j2:6 641#: glossary.html.j2:6
@@ -610,7 +645,7 @@ msgstr ""
610#: glossary.html.j2:8 645#: glossary.html.j2:8
611msgid "" 646msgid ""
612"trusted third party that verifies that the `exchange` is operating " 647"trusted third party that verifies that the `exchange` is operating "
613"correctly" 648"correctly\n"
614msgstr "" 649msgstr ""
615 650
616#: glossary.html.j2:12 651#: glossary.html.j2:12
@@ -620,7 +655,7 @@ msgstr ""
620#: glossary.html.j2:14 655#: glossary.html.j2:14
621msgid "" 656msgid ""
622"traditional financial service provider who offers wire `transfers` " 657"traditional financial service provider who offers wire `transfers` "
623"between accounts" 658"between accounts\n"
624msgstr "" 659msgstr ""
625 660
626#: glossary.html.j2:18 661#: glossary.html.j2:18
@@ -630,7 +665,7 @@ msgstr ""
630#: glossary.html.j2:20 665#: glossary.html.j2:20
631msgid "" 666msgid ""
632"coins are individual token representing a certain amount of value, also " 667"coins are individual token representing a certain amount of value, also "
633"known as the `denomination` of the coin" 668"known as the `denomination` of the coin\n"
634msgstr "" 669msgstr ""
635 670
636#: glossary.html.j2:24 671#: glossary.html.j2:24
@@ -638,7 +673,7 @@ msgid "contract"
638msgstr "" 673msgstr ""
639 674
640#: glossary.html.j2:26 675#: glossary.html.j2:26
641msgid "the proposal signed by the wallet." 676msgid "the proposal signed by the wallet.\n"
642msgstr "" 677msgstr ""
643 678
644#: glossary.html.j2:30 679#: glossary.html.j2:30
@@ -648,7 +683,7 @@ msgstr ""
648#: glossary.html.j2:32 683#: glossary.html.j2:32
649msgid "" 684msgid ""
650"unit of currency, specifies both the currency and the face value of a " 685"unit of currency, specifies both the currency and the face value of a "
651"`coin`" 686"`coin`\n"
652msgstr "" 687msgstr ""
653 688
654#: glossary.html.j2:36 689#: glossary.html.j2:36
@@ -658,7 +693,7 @@ msgstr ""
658#: glossary.html.j2:38 693#: glossary.html.j2:38
659msgid "" 694msgid ""
660"RSA key used by the exchange to certify that a given `coin` is valid and " 695"RSA key used by the exchange to certify that a given `coin` is valid and "
661"of a particular `denomination`" 696"of a particular `denomination`\n"
662msgstr "" 697msgstr ""
663 698
664#: glossary.html.j2:42 699#: glossary.html.j2:42
@@ -669,7 +704,7 @@ msgstr ""
669msgid "" 704msgid ""
670"operation by which a merchant passes coins to an exchange, expecting the " 705"operation by which a merchant passes coins to an exchange, expecting the "
671"exchange to credit his `bank` account in the future using a wire " 706"exchange to credit his `bank` account in the future using a wire "
672"`transfer`" 707"`transfer`\n"
673msgstr "" 708msgstr ""
674 709
675#: glossary.html.j2:48 710#: glossary.html.j2:48
@@ -681,7 +716,7 @@ msgid ""
681"a `coin` is dirty if its public key may be known to an entity other than " 716"a `coin` is dirty if its public key may be known to an entity other than "
682"the customer, thereby creating the danger of some entity being able to " 717"the customer, thereby creating the danger of some entity being able to "
683"link multiple transactions of coin's owner if the coin is not refreshed " 718"link multiple transactions of coin's owner if the coin is not refreshed "
684"first" 719"first\n"
685msgstr "" 720msgstr ""
686 721
687#: glossary.html.j2:54 722#: glossary.html.j2:54
@@ -690,8 +725,8 @@ msgstr ""
690 725
691#: glossary.html.j2:56 726#: glossary.html.j2:56
692msgid "" 727msgid ""
693"Taler's payment service provider. Issues eletronic `coins` during " 728"Taler's payment service provider. Issues eletronic `coins` during "
694"`withdrawal` and redeems them when they are `deposited` by merchants." 729"`withdrawal` and redeems them when they are `deposited` by merchants.\n"
695msgstr "" 730msgstr ""
696 731
697#: glossary.html.j2:60 732#: glossary.html.j2:60
@@ -699,7 +734,7 @@ msgid "extension"
699msgstr "" 734msgstr ""
700 735
701#: glossary.html.j2:62 736#: glossary.html.j2:62
702msgid "implementation of a `wallet` for browsers" 737msgid "implementation of a `wallet` for browsers\n"
703msgstr "" 738msgstr ""
704 739
705#: glossary.html.j2:66 740#: glossary.html.j2:66
@@ -707,7 +742,7 @@ msgid "fresh coin"
707msgstr "" 742msgstr ""
708 743
709#: glossary.html.j2:68 744#: glossary.html.j2:68
710msgid "a `coin` is fresh if its public key is only known to the customer" 745msgid "a `coin` is fresh if its public key is only known to the customer\n"
711msgstr "" 746msgstr ""
712 747
713#: glossary.html.j2:72 748#: glossary.html.j2:72
@@ -717,7 +752,7 @@ msgstr ""
717#: glossary.html.j2:74 752#: glossary.html.j2:74
718msgid "" 753msgid ""
719"offline key used by the exchange to certify denomination keys and message" 754"offline key used by the exchange to certify denomination keys and message"
720" signing keys" 755" signing keys\n"
721msgstr "" 756msgstr ""
722 757
723#: glossary.html.j2:78 758#: glossary.html.j2:78
@@ -725,7 +760,7 @@ msgid "message signing key"
725msgstr "" 760msgstr ""
726 761
727#: glossary.html.j2:80 762#: glossary.html.j2:80
728msgid "key used by the exchange to sign online messages, other than coins" 763msgid "key used by the exchange to sign online messages, other than coins\n"
729msgstr "" 764msgstr ""
730 765
731#: glossary.html.j2:84 766#: glossary.html.j2:84
@@ -735,11 +770,15 @@ msgstr ""
735#: glossary.html.j2:86 770#: glossary.html.j2:86
736msgid "" 771msgid ""
737"specification of the details of a transaction, specifies the payment " 772"specification of the details of a transaction, specifies the payment "
738"obligations for the customer (i.e. the amount), the deliverables of the " 773"obligations\n"
739"merchant and other related information, such as deadlines or locations; " 774"for the customer (i.e. the amount), the deliverables of the merchant and "
740"However, it lacks some information that the backend is supposed to " 775"other\n"
741"provide. In other words, after the backend adds the missing information " 776"related information, such as deadlines or locations; However, it lacks "
742"to the offer and signs it, it becomes a proposal." 777"some\n"
778"information that the backend is supposed to provide.\n"
779"In other words, after the backend adds the missing information to the "
780"offer and\n"
781"signs it, it becomes a proposal.\n"
743msgstr "" 782msgstr ""
744 783
745#: glossary.html.j2:95 784#: glossary.html.j2:95
@@ -747,7 +786,7 @@ msgid "owner"
747msgstr "" 786msgstr ""
748 787
749#: glossary.html.j2:97 788#: glossary.html.j2:97
750msgid "a `coin` is owned by the entity that knows the private key of the coin" 789msgid "a `coin` is owned by the entity that knows the private key of the coin\n"
751msgstr "" 790msgstr ""
752 791
753#: glossary.html.j2:101 792#: glossary.html.j2:101
@@ -757,7 +796,7 @@ msgstr ""
757#: glossary.html.j2:103 796#: glossary.html.j2:103
758msgid "" 797msgid ""
759"message that cryptographically demonstrates that a particular claim is " 798"message that cryptographically demonstrates that a particular claim is "
760"correct" 799"correct\n"
761msgstr "" 800msgstr ""
762 801
763#: glossary.html.j2:107 802#: glossary.html.j2:107
@@ -765,7 +804,7 @@ msgid "proposal"
765msgstr "" 804msgstr ""
766 805
767#: glossary.html.j2:109 806#: glossary.html.j2:109
768msgid "a sketch that has been completed and signed by the merchant backend." 807msgid "a sketch that has been completed and signed by the merchant backend.\n"
769msgstr "" 808msgstr ""
770 809
771#: glossary.html.j2:113 810#: glossary.html.j2:113
@@ -776,7 +815,7 @@ msgstr ""
776msgid "" 815msgid ""
777"funds set aside for future use; either the balance of a customer at the " 816"funds set aside for future use; either the balance of a customer at the "
778"exchange ready for `withdrawal`, or the funds kept in the exchange's bank" 817"exchange ready for `withdrawal`, or the funds kept in the exchange's bank"
779" account to cover obligations from coins in circulation" 818" account to cover obligations from coins in circulation\n"
780msgstr "" 819msgstr ""
781 820
782#: glossary.html.j2:119 821#: glossary.html.j2:119
@@ -786,7 +825,7 @@ msgstr ""
786#: glossary.html.j2:121 825#: glossary.html.j2:121
787msgid "" 826msgid ""
788"operation by which a `dirty` `coin` is converted into one or more `fresh`" 827"operation by which a `dirty` `coin` is converted into one or more `fresh`"
789" coins" 828" coins\n"
790msgstr "" 829msgstr ""
791 830
792#: glossary.html.j2:125 831#: glossary.html.j2:125
@@ -797,7 +836,7 @@ msgstr ""
797msgid "" 836msgid ""
798"operation by which a merchant steps back from the right to funds that he " 837"operation by which a merchant steps back from the right to funds that he "
799"obtained from a `deposit` operation, giving the right to the funds back " 838"obtained from a `deposit` operation, giving the right to the funds back "
800"to the customer" 839"to the customer\n"
801msgstr "" 840msgstr ""
802 841
803#: glossary.html.j2:131 842#: glossary.html.j2:131
@@ -808,7 +847,7 @@ msgstr ""
808msgid "" 847msgid ""
809"users can share ownership of a `coin` by sharing access to the coin's " 848"users can share ownership of a `coin` by sharing access to the coin's "
810"private key, thereby allowing all co-owners to spend the coin at any " 849"private key, thereby allowing all co-owners to spend the coin at any "
811"time." 850"time.\n"
812msgstr "" 851msgstr ""
813 852
814#: glossary.html.j2:137 853#: glossary.html.j2:137
@@ -816,7 +855,7 @@ msgid "signing key"
816msgstr "" 855msgstr ""
817 856
818#: glossary.html.j2:139 857#: glossary.html.j2:139
819msgid "see message signing key." 858msgid "see message signing key.\n"
820msgstr "" 859msgstr ""
821 860
822#: glossary.html.j2:143 861#: glossary.html.j2:143
@@ -826,7 +865,7 @@ msgstr ""
826#: glossary.html.j2:145 865#: glossary.html.j2:145
827msgid "" 866msgid ""
828"operation by which a customer gives a merchant the right to `deposit` " 867"operation by which a customer gives a merchant the right to `deposit` "
829"coins in return for merchandise" 868"coins in return for merchandise\n"
830msgstr "" 869msgstr ""
831 870
832#: glossary.html.j2:149 871#: glossary.html.j2:149
@@ -834,7 +873,7 @@ msgid "transfer"
834msgstr "" 873msgstr ""
835 874
836#: glossary.html.j2:151 875#: glossary.html.j2:151
837msgid "method of sending funds between `bank` accounts" 876msgid "method of sending funds between `bank` accounts\n"
838msgstr "" 877msgstr ""
839 878
840#: glossary.html.j2:155 879#: glossary.html.j2:155
@@ -844,7 +883,7 @@ msgstr ""
844#: glossary.html.j2:157 883#: glossary.html.j2:157
845msgid "" 884msgid ""
846"method by which ownership is exclusively transferred from one entity to " 885"method by which ownership is exclusively transferred from one entity to "
847"another" 886"another\n"
848msgstr "" 887msgstr ""
849 888
850#: glossary.html.j2:161 889#: glossary.html.j2:161
@@ -852,7 +891,7 @@ msgid "transaction id"
852msgstr "" 891msgstr ""
853 892
854#: glossary.html.j2:163 893#: glossary.html.j2:163
855msgid "unique number by which a merchant identifies a `transaction`" 894msgid "unique number by which a merchant identifies a `transaction`\n"
856msgstr "" 895msgstr ""
857 896
858#: glossary.html.j2:167 897#: glossary.html.j2:167
@@ -862,7 +901,7 @@ msgstr ""
862#: glossary.html.j2:169 901#: glossary.html.j2:169
863msgid "" 902msgid ""
864"software running on a customer's computer; withdraws, stores and spends " 903"software running on a customer's computer; withdraws, stores and spends "
865"coins" 904"coins\n"
866msgstr "" 905msgstr ""
867 906
868#: glossary.html.j2:173 907#: glossary.html.j2:173
@@ -870,7 +909,7 @@ msgid "wire transfer"
870msgstr "" 909msgstr ""
871 910
872#: glossary.html.j2:175 911#: glossary.html.j2:175
873msgid "see `transfer`" 912msgid "see `transfer`\n"
874msgstr "" 913msgstr ""
875 914
876#: glossary.html.j2:179 915#: glossary.html.j2:179
@@ -880,7 +919,7 @@ msgstr ""
880#: glossary.html.j2:181 919#: glossary.html.j2:181
881msgid "" 920msgid ""
882"subject of a wire `transfer`; usually a random string to uniquely " 921"subject of a wire `transfer`; usually a random string to uniquely "
883"identify the `transfer`" 922"identify the `transfer`\n"
884msgstr "" 923msgstr ""
885 924
886#: glossary.html.j2:185 925#: glossary.html.j2:185
@@ -890,7 +929,7 @@ msgstr ""
890#: glossary.html.j2:187 929#: glossary.html.j2:187
891msgid "" 930msgid ""
892"operation by which a `wallet` can convert funds from a reserve to fresh " 931"operation by which a `wallet` can convert funds from a reserve to fresh "
893"coins" 932"coins\n"
894msgstr "" 933msgstr ""
895 934
896#: governments.html.j2:6 935#: governments.html.j2:6
@@ -899,12 +938,13 @@ msgstr ""
899 938
900#: governments.html.j2:8 939#: governments.html.j2:8
901msgid "" 940msgid ""
902"Taler provides accountability to ensure business operate legally, while " 941"Taler provides accountability to ensure business operate\n"
903"also respecting civil liberties of citizens. Taler is a payment system " 942"legally, while also respecting civil liberties of\n"
904"based on open standards and free software. Taler needs governments as " 943"citizens. Taler is a payment system based on\n"
905"they set a financial framework and act as trusted regulators. Taler " 944"open standards and free software. Taler needs\n"
906"contributes to digital sovereignty in the critical financial " 945"governments as they set a financial framework and act as\n"
907"infrastructure." 946"trusted regulators. Taler contributes to digital\n"
947"sovereignty in the critical financial infrastructure.\n"
908msgstr "" 948msgstr ""
909 949
910#: governments.html.j2:25 index.html.j2:71 950#: governments.html.j2:25 index.html.j2:71
@@ -913,44 +953,51 @@ msgstr ""
913 953
914#: governments.html.j2:28 954#: governments.html.j2:28
915msgid "" 955msgid ""
916"Taler was built with the goal of fighting corruption and supporting " 956"Taler was built with the goal of fighting corruption and\n"
917"taxation. With Taler, the receiver of any form of payment is easily " 957"supporting taxation. With Taler, the receiver of any\n"
918"identified by the government, and the merchant can be compelled to " 958"form of payment is easily identified by the government,\n"
919"provide the contract that was accepted by the customer. Governments can " 959"and the merchant can be compelled to provide the contract\n"
920"use this data to tax businesses and individuals based on their income, " 960"that was accepted by the customer. Governments can use\n"
921"making tax evasion and black markets less viable." 961"this data to tax businesses and individuals based on\n"
962"their income, making tax evasion and black markets less\n"
963"viable.\n"
922msgstr "" 964msgstr ""
923 965
924#: governments.html.j2:41 966#: governments.html.j2:41
925msgid "" 967msgid ""
926"Thus, despite offering anonymity for citizens spending digital cash to " 968"Thus, despite offering anonymity for citizens spending\n"
927"buy goods and services, Taler also ensures that the state can observe " 969"digital cash to buy goods and services, Taler also\n"
928"incoming funds. This can be used to ensure businesses engage only in " 970"ensures that the state can observe incoming funds. This\n"
929"legal activities, and do not evade income tax, sales tax or value-added " 971"can be used to ensure businesses engage only in legal\n"
930"tax. However, this observational capability does not extend to the " 972"activities, and do not evade income tax, sales tax or\n"
931"immediate personal domain. In particular, monitoring does not cover " 973"value-added tax. However, this observational capability\n"
932"shared access to funds with trusted friends and family, or synchronizing " 974"does not extend to the immediate personal domain. In\n"
933"wallets across multiple devices." 975"particular, monitoring does not cover shared access to\n"
976"funds with trusted friends and family, or synchronizing\n"
977"wallets across multiple devices.\n"
934msgstr "" 978msgstr ""
935 979
936#: governments.html.j2:61 980#: governments.html.j2:61
937msgid "" 981msgid ""
938"Taler's payments are cryptographically secured. Thus, customers, " 982"Taler's payments are cryptographically secured. Thus,\n"
939"merchants and the Taler payment service provider (the exchange) can " 983"customers, merchants and the Taler payment service provider\n"
940"mathematically demonstrate their lawful behavior in court in case of " 984"(the exchange) can mathematically\n"
941"disputes. Financial damages are strictly limited, improving economic " 985"demonstrate their lawful behavior in court in case of\n"
942"security for individuals, merchants, the exchange and the state." 986"disputes. Financial damages are strictly limited,\n"
987"improving economic security for individuals, merchants,\n"
988"the exchange and the state.\n"
943msgstr "" 989msgstr ""
944 990
945#: governments.html.j2:73 991#: governments.html.j2:73
946msgid "" 992msgid ""
947"As a payment service provider, the Taler exchange is subject to financial" 993"As a payment service provider, the Taler exchange is\n"
948" regulation. Financial regulation and regular audits are critical to " 994"subject to financial regulation. Financial regulation and\n"
949"establish trust. In particular, the Taler design mandates the existence " 995"regular audits are critical to establish trust. In\n"
950"of an independent auditor who checks cryptographic proofs that accumulate" 996"particular, the Taler design mandates the existence of an\n"
951" at the exchange to ensure that the escrow account is managed honestly. " 997"independent auditor who checks cryptographic proofs that\n"
952"This ensures that the exchange does not threaten the economy due to " 998"accumulate at the exchange to ensure that the escrow\n"
953"fraud." 999"account is managed honestly. This ensures that the\n"
1000"exchange does not threaten the economy due to fraud.\n"
954msgstr "" 1001msgstr ""
955 1002
956#: governments.html.j2:88 index.html.j2:97 1003#: governments.html.j2:88 index.html.j2:97
@@ -959,9 +1006,10 @@ msgstr ""
959 1006
960#: governments.html.j2:91 1007#: governments.html.j2:91
961msgid "" 1008msgid ""
962"Taler is free software implementing an open protocol standard. Thus, " 1009"Taler is free software implementing an open protocol\n"
963"Taler will enable competition and avoid the monopolization of payment " 1010"standard. Thus, Taler will enable competition and avoid\n"
964"systems that threatens global political and financial stability today." 1011"the monopolization of payment systems that threatens\n"
1012"global political and financial stability today.\n"
965msgstr "" 1013msgstr ""
966 1014
967#: governments.html.j2:101 1015#: governments.html.j2:101
@@ -970,9 +1018,11 @@ msgstr ""
970 1018
971#: governments.html.j2:104 1019#: governments.html.j2:104
972msgid "" 1020msgid ""
973"Taler has an efficient design. Unlike Blockchain-based payment systems, " 1021"Taler has an efficient design. Unlike\n"
974"such as Bitcoin, Taler will not threaten the availability of national " 1022"Blockchain-based payment systems, such as Bitcoin,\n"
975"electric grids or (significantly) contribute to environmental pollution." 1023"Taler will not threaten the availability of\n"
1024"national electric grids or (significantly)\n"
1025"contribute to environmental pollution.\n"
976msgstr "" 1026msgstr ""
977 1027
978#: governments.html.j2:120 1028#: governments.html.j2:120
@@ -1025,36 +1075,41 @@ msgstr ""
1025 1075
1026#: governments.html.j2:140 1076#: governments.html.j2:140
1027msgid "" 1077msgid ""
1028"Taler assumes governments can observe traditional wire transfers entering" 1078"Taler assumes governments can observe traditional wire transfers\n"
1029" and leaving the Taler payment system. Starting with the wire transfers, " 1079"entering and leaving the Taler payment system. Starting with the\n"
1030"governments can obtain:" 1080"wire transfers, governments can obtain:\n"
1031msgstr "" 1081msgstr ""
1032 1082
1033#: governments.html.j2:148 1083#: governments.html.j2:148
1034msgid "" 1084msgid ""
1035"The total amount of digital currency withdrawn by a customer. The " 1085"The total amount of digital currency withdrawn by a\n"
1036"government can impose limits on how much digital cash a customer can " 1086"customer. The government can impose limits on how much\n"
1037"withdraw within a given time frame." 1087"digital cash a customer can withdraw within a\n"
1088"given time frame.\n"
1038msgstr "" 1089msgstr ""
1039 1090
1040#: governments.html.j2:157 1091#: governments.html.j2:157
1041msgid "The income received by any merchant via the Taler system." 1092msgid ""
1093"The income received by any merchant via the Taler\n"
1094"system.\n"
1042msgstr "" 1095msgstr ""
1043 1096
1044#: governments.html.j2:164 1097#: governments.html.j2:164
1045msgid "" 1098msgid ""
1046"The exact details of the underlying contract that was signed between " 1099"The exact details of the underlying contract that was\n"
1047"customer and merchant. However, this information would typically not " 1100"signed between customer and merchant. However, this\n"
1048"include the identity of the customer." 1101"information would typically not include the identity\n"
1102"of the customer.\n"
1049msgstr "" 1103msgstr ""
1050 1104
1051#: governments.html.j2:174 1105#: governments.html.j2:174
1052msgid "" 1106msgid ""
1053"The amounts of digital coins legitimately withdrawn by customers from the" 1107"The amounts of digital coins legitimately withdrawn\n"
1054" exchange, the value of non-redeemed digital coins in customer's wallets," 1108"by customers from the exchange, the value of\n"
1055" the value and corresponding wire details of deposit operations performed" 1109"non-redeemed digital coins in customer's wallets, the\n"
1056" by merchants with the exchange, and the income of the exchange from " 1110"value and corresponding wire details of deposit\n"
1057"transaction fees." 1111"operations performed by merchants with the exchange,\n"
1112"and the income of the exchange from transaction fees.\n"
1058msgstr "" 1113msgstr ""
1059 1114
1060#: index.html.j2:10 1115#: index.html.j2:10
@@ -1063,12 +1118,12 @@ msgstr ""
1063 1118
1064#: index.html.j2:13 1119#: index.html.j2:13
1065msgid "" 1120msgid ""
1066"GNU Taler is an electronic payment system under development at <a " 1121"GNU Taler is an electronic payment system under development at\n"
1067"href=\"http://www.inria.fr/\">Inria</a>. We expect to make it operational" 1122"<a href=\"http://www.inria.fr/\">Inria</a>. We expect to make it\n"
1068" in 2017. You can learn about Taler on this website, try the <a " 1123"operational in 2017. You can learn about Taler on this website,\n"
1069"href=\"https://demo.taler.net\">demo</a> and look at our <a " 1124"try the <a href=\"https://demo.taler.net\">demo</a> and look at\n"
1070"href=\"https://docs.taler.net\">developer</a> and <a " 1125"our <a href=\"https://docs.taler.net\">developer</a> and <a\n"
1071"href=\"https://api.taler.net\">API</a> documentation." 1126"href=\"https://api.taler.net\">API</a> documentation.\n"
1072msgstr "" 1127msgstr ""
1073 1128
1074#: index.html.j2:29 1129#: index.html.j2:29
@@ -1077,48 +1132,53 @@ msgstr ""
1077 1132
1078#: index.html.j2:32 1133#: index.html.j2:32
1079msgid "" 1134msgid ""
1080"Taler is easy to integrate with existing Web applications. Payments are " 1135"Taler is easy to integrate with existing Web\n"
1081"cryptographically secured and are confirmed within milliseconds with " 1136"applications. Payments are cryptographically\n"
1082"extremely low transaction costs." 1137"secured and are confirmed within milliseconds with\n"
1138"extremely low transaction costs.\n"
1083msgstr "" 1139msgstr ""
1084 1140
1085#: index.html.j2:45 1141#: index.html.j2:45
1086msgid "" 1142msgid ""
1087"Taler does not introduce a new currency. Taler uses a digital wallet " 1143"Taler does not introduce a new currency. Taler\n"
1088"storing coins and payment service providers with escrow accounts in " 1144"uses a digital wallet storing coins and payment service\n"
1089"existing currencies. Thus, Taler's cryptographic coins correspond to " 1145"providers with escrow accounts in existing currencies.\n"
1090"existing currencies, such as US Dollars, Euros or even Bitcoins." 1146"Thus, Taler's cryptographic coins correspond to existing\n"
1147"currencies, such as US Dollars, Euros or even Bitcoins.\n"
1091msgstr "" 1148msgstr ""
1092 1149
1093#: index.html.j2:59 1150#: index.html.j2:59
1094msgid "" 1151msgid ""
1095"By design Taler does not suffer from many classes of security problems " 1152"By design Taler does not suffer from many classes\n"
1096"such as phishing or counterfeit. Thanks to its security features, Taler " 1153"of security problems such as phishing or counterfeit.\n"
1097"never rejects a legitimate customer due to a fraud-detection false " 1154"Thanks to its security features, Taler never rejects a legitimate\n"
1098"positive." 1155"customer due to a fraud-detection false positive.\n"
1099msgstr "" 1156msgstr ""
1100 1157
1101#: index.html.j2:74 1158#: index.html.j2:74
1102msgid "" 1159msgid ""
1103"When using Taler, merchant's revenue is transparent for tax collection " 1160"When using Taler, merchant's revenue is transparent for tax\n"
1104"authorities. Unlike cash and most digital currencies, Taler helps prevent" 1161"collection authorities. Unlike cash and most digital currencies,\n"
1105" black markets. Taler is not suitable for illegal activities." 1162"Taler helps prevent black markets. Taler is not suitable for\n"
1163"illegal activities.\n"
1106msgstr "" 1164msgstr ""
1107 1165
1108#: index.html.j2:86 1166#: index.html.j2:86
1109msgid "" 1167msgid ""
1110"When you pay with Taler, your identity does not have to be revealed. Just" 1168"When you pay with Taler, your identity does not\n"
1111" like payments in cash, nobody else can track how you spent your " 1169"have to be revealed. Just like\n"
1112"electronic money. However, you obtain a legally valid proof of payment." 1170"payments in cash, nobody else can track how you\n"
1171"spent your electronic money. However, you obtain a\n"
1172"legally valid proof of payment.\n"
1113msgstr "" 1173msgstr ""
1114 1174
1115#: index.html.j2:100 1175#: index.html.j2:100
1116msgid "" 1176msgid ""
1117"Taler provides protocols and reference implementations that in principle " 1177"Taler provides protocols and reference implementations that in\n"
1118"enables anybody to run their own payment infrastructure, be it " 1178"principle enables anybody to run their own payment infrastructure,\n"
1119"individuals, organizations or whole countries. Since the reference " 1179"be it individuals, organizations or whole countries. Since the\n"
1120"implementation is a <a href=\"http://www.gnu.org/\">GNU</a> package, it " 1180"reference implementation is a <a href=\"http://www.gnu.org/\">GNU</a>\n"
1121"will always remain free software." 1181"package, it will always remain free software.\n"
1122msgstr "" 1182msgstr ""
1123 1183
1124#: index.html.j2:117 1184#: index.html.j2:117
@@ -1127,12 +1187,12 @@ msgstr ""
1127 1187
1128#: index.html.j2:118 1188#: index.html.j2:118
1129msgid "" 1189msgid ""
1130"<p>To pay with Taler, customers install an electronic wallet on their " 1190"<p>To pay with Taler, customers install an electronic wallet\n"
1131"device. Before the first payment, the wallet's balance must be charged in" 1191"on their device. Before the first payment, the wallet's balance must\n"
1132" the desired currency by some other means of payment.</p> <p>Once the " 1192"be charged in the desired currency by some other means of payment.</p>\n"
1133"wallet is charged, payments on websites take only one click, are never " 1193"<p>Once the wallet is charged, payments on websites take only one click,\n"
1134"falsely rejected by fraud detection and do not pose any risk of phishing " 1194"are never falsely rejected by fraud detection and do not pose any risk\n"
1135"or identity theft.</p>" 1195"of phishing or identity theft.</p>\n"
1136msgstr "" 1196msgstr ""
1137 1197
1138#: index.html.j2:128 1198#: index.html.j2:128
@@ -1141,11 +1201,11 @@ msgstr ""
1141 1201
1142#: index.html.j2:129 1202#: index.html.j2:129
1143msgid "" 1203msgid ""
1144"<p>To receive Taler payments, a merchant needs a bank account in the " 1204"<p>To receive Taler payments, a merchant needs a bank account\n"
1145"desired currency. We provide supporting software in various programming " 1205"in the desired currency. We provide supporting software\n"
1146"languages to make the integration painless. The merchant's backend for " 1206"in various programming languages to make the integration painless.\n"
1147"Taler transaction processing can run on the merchant's premises or be " 1207"The merchant's backend for Taler transaction processing can run\n"
1148"hosted by a third party.</p>" 1208"on the merchant's premises or be hosted by a third party.</p>\n"
1149msgstr "" 1209msgstr ""
1150 1210
1151#: index.html.j2:145 1211#: index.html.j2:145
@@ -1162,8 +1222,10 @@ msgstr ""
1162 1222
1163#: investors.html.j2:9 1223#: investors.html.j2:9
1164msgid "" 1224msgid ""
1165"We have created a company, Taler Systems SA in Luxembourg.<br> Please " 1225"We have created a company, Taler Systems SA in\n"
1166"contact <tt>invest@taler.net</tt> if you want to invest in Taler." 1226"Luxembourg.<br>\n"
1227"Please contact <tt>invest@taler.net</tt>\n"
1228"if you want to invest in Taler.\n"
1167msgstr "" 1229msgstr ""
1168 1230
1169#: investors.html.j2:24 1231#: investors.html.j2:24
@@ -1173,17 +1235,20 @@ msgstr ""
1173#: investors.html.j2:27 1235#: investors.html.j2:27
1174msgid "" 1236msgid ""
1175"Our <a href=\"about.html\">team</a> combines world-class business " 1237"Our <a href=\"about.html\">team</a> combines world-class business "
1176"leaders, cryptographers, software engineers, civil-rights activists and " 1238"leaders,\n"
1177"academics. We are unified by a vision of how payments should work and the" 1239"cryptographers, software engineers, civil-rights\n"
1178" goal of imposing this vision upon the world." 1240"activists and academics. We are unified by a vision\n"
1241"of how payments should work and the goal of\n"
1242"imposing this vision upon the world.\n"
1179msgstr "" 1243msgstr ""
1180 1244
1181#: investors.html.j2:37 1245#: investors.html.j2:37
1182msgid "" 1246msgid ""
1183"We are currently supported by <a href=\"http://www.inria.fr/\">Inria</a>," 1247"We are currently supported by <a href=\"http://www.inria.fr/\">Inria</a>,"
1184" the French national institute for research in informatics and " 1248" the French\n"
1249"national institute for research in informatics and\n"
1185"automation, and the <a href=\"https://renewablefreedom.org/\">Renewable " 1250"automation, and the <a href=\"https://renewablefreedom.org/\">Renewable "
1186"Freedom Foundation</a>." 1251"Freedom Foundation</a>.\n"
1187msgstr "" 1252msgstr ""
1188 1253
1189#: investors.html.j2:45 1254#: investors.html.j2:45
@@ -1193,13 +1258,16 @@ msgstr ""
1193#: investors.html.j2:48 1258#: investors.html.j2:48
1194msgid "" 1259msgid ""
1195"All transactions in Taler are secured using <a " 1260"All transactions in Taler are secured using <a "
1196"href=\"bibliography.html\">modern cryptography</a> and trust in all " 1261"href=\"bibliography.html\">modern\n"
1197"parties is minimized. Financial damage is bounded (for customers, " 1262"cryptography</a> and trust in all parties is\n"
1198"merchants and the exchange) even in the case that systems are compromised" 1263"minimized. Financial damage is bounded (for\n"
1199" and private keys are stolen. Databases can be audited for consistency, " 1264"customers, merchants and the exchange) even in the\n"
1200"resulting in either the detection of compromised systems or the " 1265"case that systems are compromised and private keys\n"
1201"demonstration that participants were honest. Actual transaction costs are" 1266"are stolen. Databases can be audited for\n"
1202" fractions of a cent." 1267"consistency, resulting in either the detection of\n"
1268"compromised systems or the demonstration that\n"
1269"participants were honest. Actual transaction costs\n"
1270"are fractions of a cent.\n"
1203msgstr "" 1271msgstr ""
1204 1272
1205#: investors.html.j2:63 1273#: investors.html.j2:63
@@ -1208,13 +1276,15 @@ msgstr ""
1208 1276
1209#: investors.html.j2:66 1277#: investors.html.j2:66
1210msgid "" 1278msgid ""
1211"The scalable business model for Taler is the operation of the payment " 1279"The scalable business model for Taler is the operation\n"
1212"service provider, which converts money from traditional payment systems " 1280"of the payment service provider, which converts money from\n"
1213"(MasterCard, SEPA, UPI, Visa, Bitcoin, ACH, SWIFT, etc.) to anonymous " 1281"traditional payment systems (MasterCard, SEPA, UPI,\n"
1214"electronic coins in the same currency. The customer can then redeem the " 1282"Visa, Bitcoin, ACH, SWIFT, etc.) to anonymous\n"
1215"electronic coins at a merchant, who can exchange them for money " 1283"electronic coins in the same currency. The customer\n"
1216"represented using traditional payment systems at the exchange. The " 1284"can then redeem the electronic coins at a merchant,\n"
1217"exchange charges fees to facilitate the transactions." 1285"who can exchange them for money represented using\n"
1286"traditional payment systems at the exchange. The\n"
1287"exchange charges fees to facilitate the transactions.\n"
1218msgstr "" 1288msgstr ""
1219 1289
1220#: investors.html.j2:85 1290#: investors.html.j2:85
@@ -1227,10 +1297,10 @@ msgstr ""
1227 1297
1228#: investors.html.j2:110 1298#: investors.html.j2:110
1229msgid "" 1299msgid ""
1230"The payment service operator runs the <em>Taler exchange</em>. The " 1300"The payment service operator runs the <em>Taler exchange</em>.\n"
1231"exchange charges <b>transaction fees</b> to customers or merchants. Its " 1301"The exchange charges <b>transaction fees</b> to customers or merchants.\n"
1232"operational expenses are from wire transfers with the banking system and " 1302"Its operational expenses are from wire transfers with the banking\n"
1233"the operation of the computing infrastructure." 1303"system and the operation of the computing infrastructure.\n"
1234msgstr "" 1304msgstr ""
1235 1305
1236#: investors.html.j2:120 1306#: investors.html.j2:120
@@ -1265,10 +1335,11 @@ msgstr ""
1265 1335
1266#: merchants.html.j2:8 1336#: merchants.html.j2:8
1267msgid "" 1337msgid ""
1268"Taler is a cost-effective electronic payment system which provides you " 1338"Taler is a cost-effective electronic payment system\n"
1269"with cryptographic proof that the payment worked correctly within " 1339"which provides you with cryptographic proof that\n"
1270"milliseconds. Your Web customers pay with previously unknown levels of " 1340"the payment worked correctly within milliseconds.\n"
1271"convenience without risk of fraud." 1341"Your Web customers pay with previously unknown\n"
1342"levels of convenience without risk of fraud.\n"
1272msgstr "" 1343msgstr ""
1273 1344
1274#: merchants.html.j2:22 1345#: merchants.html.j2:22
@@ -1277,32 +1348,39 @@ msgstr ""
1277 1348
1278#: merchants.html.j2:25 1349#: merchants.html.j2:25
1279msgid "" 1350msgid ""
1280"Processing transactions with Taler is fast, allowing you to confirm the " 1351"Processing transactions with Taler is fast,\n"
1281"transaction with your customer virtually immediately. Your customers will" 1352"allowing you to confirm the transaction with your\n"
1282" appreciate that they do not have to type in credit card information and " 1353"customer virtually immediately. Your customers\n"
1283"play the &quot;verified by&quot; game. By making payments significantly " 1354"will appreciate that they do not have to type in\n"
1284"more convenient for your customers, you may be able to use Taler for " 1355"credit card information and play the &quot;verified\n"
1285"small transactions that would not work with credit card payments due to " 1356"by&quot; game. By making payments significantly\n"
1286"the mental overhead for customers." 1357"more convenient for your customers, you may be able\n"
1358"to use Taler for small transactions that would not\n"
1359"work with credit card payments due to the mental\n"
1360"overhead for customers.\n"
1287msgstr "" 1361msgstr ""
1288 1362
1289#: merchants.html.j2:44 1363#: merchants.html.j2:44
1290msgid "" 1364msgid ""
1291"You will have cryptographic proof of payment from the Taler payment " 1365"You will have cryptographic proof of payment from the\n"
1292"service provider. With Taler you never handle sensitive customer account " 1366"Taler payment service provider. With Taler you never\n"
1293"information and thus do not have to undergo any particular security " 1367"handle sensitive customer account information and thus\n"
1294"audits (such as PCI DSS). Your systems will have customer contracts with " 1368"do not have to undergo any particular security audits\n"
1295"qualified signatures for all transactions which you can use in court in " 1369"(such as PCI DSS). Your systems will have customer\n"
1296"case of disputes." 1370"contracts with qualified signatures for all\n"
1371"transactions which you can use in court in case of\n"
1372"disputes.\n"
1297msgstr "" 1373msgstr ""
1298 1374
1299#: merchants.html.j2:61 1375#: merchants.html.j2:61
1300msgid "" 1376msgid ""
1301"Taler is free software, and you can use the liberally-licensed reference " 1377"Taler is free software, and you can use the\n"
1302"code as a starting point to integrate Taler into your services. To use " 1378"liberally-licensed reference code as a starting\n"
1303"Taler, you do not need to pay license fees, and the free software " 1379"point to integrate Taler into your services. To use\n"
1304"development model will ensure that you can select from many competing " 1380"Taler, you do not need to pay license fees, and the\n"
1305"integrators for support." 1381"free software development model will ensure that\n"
1382"you can select from many competing integrators for\n"
1383"support.\n"
1306msgstr "" 1384msgstr ""
1307 1385
1308#: merchants.html.j2:76 1386#: merchants.html.j2:76
@@ -1311,10 +1389,11 @@ msgstr ""
1311 1389
1312#: merchants.html.j2:79 1390#: merchants.html.j2:79
1313msgid "" 1391msgid ""
1314"Taler is uses efficient cryptographic constructions with low bandwidth " 1392"Taler is uses efficient cryptographic constructions with low\n"
1315"and storage requirements. Combined with Taler's strong security which " 1393"bandwidth and storage requirements. Combined with Taler's strong\n"
1316"makes fraud impossible, Taler payment service providers can operate with " 1394"security which makes fraud impossible, Taler payment service\n"
1317"very low overhead and thus offer low transaction fees." 1395"providers can operate with very low overhead and\n"
1396"thus offer low transaction fees.\n"
1318msgstr "" 1397msgstr ""
1319 1398
1320#: merchants.html.j2:89 1399#: merchants.html.j2:89
@@ -1323,9 +1402,10 @@ msgstr ""
1323 1402
1324#: merchants.html.j2:92 1403#: merchants.html.j2:92
1325msgid "" 1404msgid ""
1326"Taler can be used for different currencies (such as Euros, US Dollars or " 1405"Taler can be used for different currencies (such as\n"
1327"Bitcoins) and any amount, limited only by applicable regulatation and " 1406"Euros, US Dollars or Bitcoins) and any amount, limited\n"
1328"what denominations the payment service provider supports." 1407"only by applicable regulatation and what denominations\n"
1408"the payment service provider supports.\n"
1329msgstr "" 1409msgstr ""
1330 1410
1331#: merchants.html.j2:101 1411#: merchants.html.j2:101
@@ -1334,10 +1414,11 @@ msgstr ""
1334 1414
1335#: merchants.html.j2:104 1415#: merchants.html.j2:104
1336msgid "" 1416msgid ""
1337"Taler prevents tax evasion and money laundering. Taler's protocols are " 1417"Taler prevents tax evasion and money laundering.\n"
1338"efficient and do not use wasteful proof-of-work calculations. Taler " 1418"Taler's protocols are efficient and do not use wasteful\n"
1339"encourages transparency by providing an open standard and free software " 1419"proof-of-work calculations. Taler encourages\n"
1340"reference implementations." 1420"transparency by providing an open standard and free\n"
1421"software reference implementations.\n"
1341msgstr "" 1422msgstr ""
1342 1423
1343#: merchants.html.j2:119 1424#: merchants.html.j2:119
@@ -1366,25 +1447,28 @@ msgstr ""
1366 1447
1367#: merchants.html.j2:147 1448#: merchants.html.j2:147
1368msgid "" 1449msgid ""
1369"The backend <b>signs</b> and <b>stores</b> the complete terms of offers " 1450"The backend <b>signs</b> and <b>stores</b> the\n"
1370"made by the merchant to customers. For this, the merchant's frontend " 1451"complete terms of offers made by the merchant to customers.\n"
1371"needs to give the customer's order in a JSON format to the backend." 1452"For this, the merchant's frontend needs to give the\n"
1453"customer's order in a JSON format to the backend.\n"
1372msgstr "" 1454msgstr ""
1373 1455
1374#: merchants.html.j2:156 1456#: merchants.html.j2:156
1375msgid "" 1457msgid ""
1376"The backend <b>validates</b> payments received from the wallet and " 1458"The backend <b>validates</b> payments received from\n"
1377"<b>executes</b> them with the Taler payment service provider (the " 1459"the wallet and <b>executes</b> them with the Taler\n"
1378"exchange). For this, the merchant's frontend must pass the payment " 1460"payment service provider (the exchange). For this,\n"
1379"request through to the Taler backend and check the HTTP status code that " 1461"the merchant's frontend must pass the payment\n"
1380"is returned." 1462"request through to the Taler backend and check the\n"
1463"HTTP status code that is returned.\n"
1381msgstr "" 1464msgstr ""
1382 1465
1383#: merchants.html.j2:167 1466#: merchants.html.j2:167
1384msgid "" 1467msgid ""
1385"The backend can <b>list</b> completed transactions and <b>map</b> wire " 1468"The backend can <b>list</b> completed transactions\n"
1386"transfers to sets of business transactions, including the exact terms of " 1469"and <b>map</b> wire transfers to sets of business\n"
1387"each contract." 1470"transactions, including the exact terms of each\n"
1471"contract.\n"
1388msgstr "" 1472msgstr ""
1389 1473
1390#: press.html.j2:4 1474#: press.html.j2:4
@@ -1606,1001 +1690,3 @@ msgstr ""
1606#~ msgid "Low Fees" 1690#~ msgid "Low Fees"
1607#~ msgstr "" 1691#~ msgstr ""
1608 1692
1609#~ msgid ""
1610#~ "Taler largely functions like digital "
1611#~ "cash. You withdraw money from your "
1612#~ "bank account into your electronic "
1613#~ "wallet, and can henceforth spend digital"
1614#~ " cash. The electronic wallet can "
1615#~ "carry multiple currencies. "
1616#~ msgstr ""
1617
1618#~ msgid ""
1619#~ "Taler uses modern cryptography, ensuring "
1620#~ "that there is no counterfeit. Your "
1621#~ "digital wallet is safer than your "
1622#~ "physical wallet. At most, you can "
1623#~ "lose its contents because your computer"
1624#~ " or mobile is irreparably damaged or"
1625#~ " compromised. Unlike a physical wallet,"
1626#~ " you can make backups to secure "
1627#~ "against data loss."
1628#~ msgstr ""
1629
1630#~ msgid ""
1631#~ "You will be able to withdraw money"
1632#~ " to replenish the digital coins in"
1633#~ " your wallet using your credit card"
1634#~ " or wire transfers. Afterwards you "
1635#~ "can pay with one-click using the"
1636#~ " Taler wallet, which optionally keeps "
1637#~ "your transaction history on your "
1638#~ "computer."
1639#~ msgstr ""
1640
1641#~ msgid ""
1642#~ "Coins in your digital wallet will "
1643#~ "be of the same denomination as the"
1644#~ " cash in your physical wallet. Taler"
1645#~ " is not a crypto-currency, so "
1646#~ "you do not have to worry about "
1647#~ "cryto-currency related value fluctuations."
1648#~ " Banking with Taler is subject to"
1649#~ " the usual government protections for "
1650#~ "financial services."
1651#~ msgstr ""
1652
1653#~ msgid ""
1654#~ "We currently provide a <a "
1655#~ "href=\"wallet.html\">wallet browser extension</a> "
1656#~ "for Chromium, Chrome, Firefox, Opera and"
1657#~ " Edge. Wallets for mobile phones and"
1658#~ " other platforms will be available in"
1659#~ " the future. "
1660#~ msgstr ""
1661
1662#~ msgid ""
1663#~ "You can see how Taler works in "
1664#~ "practice by visiting our <a "
1665#~ "href=\"https://demo.taler.net\">demo page</a>. "
1666#~ msgstr ""
1667
1668#~ msgid ""
1669#~ "To <b>withdraw</b> electronic coins, the "
1670#~ "customer transfers funds from his bank"
1671#~ " account to the Taler payment service"
1672#~ " provider (the exchange). The wire "
1673#~ "transfer subject must match a code "
1674#~ "identifying the customer's wallet. After "
1675#~ "the wire transfer is complete, the "
1676#~ "wallet will automatically withdraw the "
1677#~ "coins from the exchange."
1678#~ msgstr ""
1679
1680#~ msgid ""
1681#~ "To <b>spend</b> electronic coins, a "
1682#~ "merchant must cause the wallet to "
1683#~ "display a proposal for some purchase."
1684#~ " The wallet will ask the customer"
1685#~ " for one-click confirmation. Payment "
1686#~ "is then instant. Transaction histories "
1687#~ "and digitally signed contracts can be"
1688#~ " preserved by the wallet."
1689#~ msgstr ""
1690
1691#~ msgid ""
1692#~ "An archived, public mailing list for "
1693#~ "GNU Taler is hosted at <a "
1694#~ "href=\"https://lists.gnu.org/mailman/listinfo/taler\">https://lists.gnu.org/mailman/listinfo/taler</a>."
1695#~ " You can send messages to the "
1696#~ "list at <a "
1697#~ "href=\"mailto:taler@gnu.org\">taler@gnu.org</a>. "
1698#~ msgstr ""
1699
1700#~ msgid ""
1701#~ "Team members are generally reachable at"
1702#~ " <tt>LASTNAME@taler.net</tt>. All of us "
1703#~ "support receiving GnuPG encrypted e-mails. \n"
1704#~ msgstr ""
1705
1706#~ msgid ""
1707#~ "We track open feature requests and "
1708#~ "bugs in our <a "
1709#~ "href=\"https://gnunet.org/bugs/\">Bug tracker</a>, which"
1710#~ " is shared with the GNUnet project."
1711#~ " You can also report bugs or "
1712#~ "feature requests to the mailing list."
1713#~ " "
1714#~ msgstr ""
1715
1716#~ msgid ""
1717#~ "For non-technical commercial requests, "
1718#~ "please contact <tt>ceo AT taler.net</tt>. \n"
1719#~ msgstr ""
1720
1721#~ msgid ""
1722#~ "GNU Taler is free software implementing"
1723#~ " an open protocol. Anybody is welcome"
1724#~ " to integrate our reference implementation"
1725#~ " into their applications. Different "
1726#~ "components of Taler are being made "
1727#~ "available under different licenses. The "
1728#~ "Affero GPLv3+ is used for the "
1729#~ "exchange, the LGPLv3+ is used for "
1730#~ "reference code demonstrating integration with"
1731#~ " merchant platforms, and licenses like "
1732#~ "GPLv3+ are used for wallets and "
1733#~ "related customer-facing software. We "
1734#~ "are open for constructive suggestions "
1735#~ "for maximizing the adoption of this "
1736#~ "payment platform. "
1737#~ msgstr ""
1738
1739#~ msgid ""
1740#~ "Taler is designed to work on the"
1741#~ " Internet. To ensure that Taler "
1742#~ "payments can work with restrictive "
1743#~ "network setups, Taler uses a RESTful "
1744#~ "protocol over HTTP or HTTPS. Taler's "
1745#~ "security does not depend upon the "
1746#~ "use of HTTPS, but obviously merchants"
1747#~ " may choose to offer HTTPS for "
1748#~ "consistency and because it generally is"
1749#~ " better for privacy compared to HTTP."
1750#~ " Taler uses JSON to encode structure"
1751#~ " data, making it easy to integrate"
1752#~ " Taler with existing Web applications. "
1753#~ "Taler's protocol is documented in detail"
1754#~ " at <a "
1755#~ "href=\"https://api.taler.net/\">api.taler.net</a>. "
1756#~ msgstr ""
1757
1758#~ msgid ""
1759#~ "Taler is currently primarily developed "
1760#~ "by a research team at <a "
1761#~ "href=\"http://www.inria.fr/\">Inria</a> and <a "
1762#~ "href=\"https://gnunet.org/\">GNUnet</a>. However, "
1763#~ "contributions from anyone are welcome. "
1764#~ "Our Git repositories can be cloned "
1765#~ "using the Git and HTTP access "
1766#~ "methods against <tt>git.taler.net</tt> with "
1767#~ "the name of the respective repository."
1768#~ " A list of repositories can be "
1769#~ "found in our <a "
1770#~ "href=\"https://git.taler.net/\">GitWeb</a>. "
1771#~ msgstr ""
1772
1773#~ msgid ""
1774#~ "In addition to this website, the "
1775#~ "<a href=\"https://git.taler.net/\">documented code</a> "
1776#~ "and the <a href=\"https://api.taler.net/\">API "
1777#~ "documentation</a>. Technical papers can be"
1778#~ " found in our <a "
1779#~ "href=\"bibliography.html\">bibliography</a>. "
1780#~ msgstr ""
1781
1782#~ msgid ""
1783#~ "We have a mailing list for "
1784#~ "developer discussions. You can subscribe "
1785#~ "to or read the list archive at "
1786#~ "<a "
1787#~ "href=\"http://lists.gnu.org/mailman/listinfo/taler\">http://lists.gnu.org/mailman/listinfo/taler</a>."
1788#~ " "
1789#~ msgstr ""
1790
1791#~ msgid ""
1792#~ "We have <a "
1793#~ "href=\"https://buildbot.net/\">Buildbot</a> automation "
1794#~ "tests to detect regressions and check"
1795#~ " for portability at <a "
1796#~ "href=\"https://buildbot.taler.net/\">buildbot.taler.net</a>. "
1797#~ msgstr ""
1798
1799#~ msgid ""
1800#~ "We use <a "
1801#~ "href=\"http://ltp.sourceforge.net/coverage/lcov.php\">LCOV</a> "
1802#~ "to analyze the code coverage of "
1803#~ "our tests, the results are available "
1804#~ "at <a href=\"https://lcov.taler.net/\">lcov.taler.net</a>."
1805#~ " "
1806#~ msgstr ""
1807
1808#~ msgid ""
1809#~ "We use <a "
1810#~ "href=\"https://gnunet.org/gauger\">Gauger</a> for "
1811#~ "performance regression analysis of the "
1812#~ "exchange backend at <a "
1813#~ "href=\"https://gauger.taler.net/\">gauger.taler.net</a>. "
1814#~ msgstr ""
1815
1816#~ msgid ""
1817#~ "The Taler system consists of protocols"
1818#~ " executed among a number of actors"
1819#~ " as illustrated in the illustration "
1820#~ "on the right. Typical transactions "
1821#~ "involve the following steps: "
1822#~ msgstr ""
1823
1824#~ msgid ""
1825#~ "A customer instructs his <b>bank</b> to"
1826#~ " transfer funds from his account to"
1827#~ " the Taler exchange (top left). In"
1828#~ " the subject of the transaction, he"
1829#~ " includes an authentication token from "
1830#~ "his electronic <b>wallet</b>. In Taler "
1831#~ "terminology, the customer creates a "
1832#~ "reserve at the exchange. "
1833#~ msgstr ""
1834
1835#~ msgid ""
1836#~ "Once the exchange has received the "
1837#~ "wire transfer, it allows the customer's"
1838#~ " electronic wallet to <b>withdraw</b> "
1839#~ "electronic coins. The electronic coins "
1840#~ "are digital representations of the "
1841#~ "original currency from the transfer. It"
1842#~ " is important to note that the "
1843#~ "exchange does not learn the &quot;serial"
1844#~ " numbers&quot; of the coins created "
1845#~ "in this process, so it cannot tell"
1846#~ " later which customer purchased what "
1847#~ "at which merchant. The use of "
1848#~ "Taler does not change the currency "
1849#~ "or the total value of the funds"
1850#~ " (except for fees which the exchange"
1851#~ " may charge for the service). "
1852#~ msgstr ""
1853
1854#~ msgid ""
1855#~ "Once the customer has the digital "
1856#~ "coins in his wallet, the wallet "
1857#~ "can be used to <b>spend</b> the "
1858#~ "coins with merchant portals that support"
1859#~ " the Taler payment system and accept"
1860#~ " the respective exchange as a "
1861#~ "business partner (bottom arrow). This "
1862#~ "creates a digital contract signed by "
1863#~ "the customer's coins and the merchant."
1864#~ " If necessary, the customer can "
1865#~ "later use this digitally signed contract"
1866#~ " in a court of law to prove "
1867#~ "the exact terms of the contract "
1868#~ "and that he paid the respective "
1869#~ "amount. The customer does not learn "
1870#~ "the banking details of the merchant, "
1871#~ "and Taler does not require the "
1872#~ "merchant to learn the identity of "
1873#~ "the customer. Naturally, the customer "
1874#~ "can spend any fraction of his "
1875#~ "digital coins (the system takes care "
1876#~ "of customers getting change). "
1877#~ msgstr ""
1878
1879#~ msgid ""
1880#~ "Merchants receiving digital coins "
1881#~ "<b>deposit</b> the respective claims that "
1882#~ "resulted from the contract signing with"
1883#~ " the customer at the exchange to "
1884#~ "redeem the coins. The deposit step "
1885#~ "does not reveal the details of the"
1886#~ " contract between the customer and "
1887#~ "the merchant or the identity of "
1888#~ "the customer to the exchange in "
1889#~ "any way. However, the exchange does "
1890#~ "learn the identity of the merchant "
1891#~ "via the provided bank routing "
1892#~ "information. The merchant can, for "
1893#~ "example when compelled by the state "
1894#~ "for taxation, provide information linking "
1895#~ "the individual deposit to the respective"
1896#~ " contract signed by the customer. "
1897#~ "Thus, the exchange's database allows the"
1898#~ " state to enforce that merchants pay"
1899#~ " applicable taxes (and do not engage"
1900#~ " in illegal contracts). "
1901#~ msgstr ""
1902
1903#~ msgid ""
1904#~ "Finally, the exchange transfers funds "
1905#~ "corresponding to the digital coins "
1906#~ "redeemed by the merchants to the "
1907#~ "merchant's <b>bank</b> account. The exchange"
1908#~ " may combine multiple small transactions"
1909#~ " into one larger bank transfer. The"
1910#~ " merchant can query the exchange "
1911#~ "about the relationship between the bank"
1912#~ " transfers and the individual claims "
1913#~ "that were deposited. "
1914#~ msgstr ""
1915
1916#~ msgid ""
1917#~ "Most importantly, the exchange keeps "
1918#~ "cryptographic proofs that allow it to"
1919#~ " demonstrate that it is operating "
1920#~ "correctly to third parties. The system"
1921#~ " requires an external <b>auditor</b>, such"
1922#~ " as a government-appointed financial "
1923#~ "regulatory body, to frequently verify "
1924#~ "the exchange's databases and check that"
1925#~ " its bank balance matches the total"
1926#~ " value of the remaining coins in "
1927#~ "circulation. "
1928#~ msgstr ""
1929
1930#~ msgid ""
1931#~ "Without the auditor, the exchange "
1932#~ "operators could embezzle funds they are"
1933#~ " holding in reserve. Customers and "
1934#~ "merchants cannot cheat each other or "
1935#~ "the exchange. If any party's computers"
1936#~ " are compromised, the financial damage "
1937#~ "is limited to the respective party "
1938#~ "and proportional to the funds they "
1939#~ "have in circulation during the period"
1940#~ " of the compromise. "
1941#~ msgstr ""
1942
1943#~ msgid ""
1944#~ "<p>Taler does not use any Blockchain "
1945#~ "technology or Bitcoin directly. Taler is"
1946#~ " not based on proof-of-work or"
1947#~ " any other distributed consensus mechanism."
1948#~ " Instead Taler is based on blind "
1949#~ "signatures.</p> "
1950#~ msgstr ""
1951
1952#~ msgid ""
1953#~ "<p>It would be possible, however, to "
1954#~ "withdraw coins denominated in Bitcoin "
1955#~ "into a Taler wallet (with an "
1956#~ "appropriate exchange), which would give "
1957#~ "some benefits over plain Bitcoin, such"
1958#~ " as instant confirmation times.</p> "
1959#~ msgstr ""
1960
1961#~ msgid ""
1962#~ "<p>Your wallet stores digital coins and"
1963#~ " thus ultimately your computer holds "
1964#~ "your balance. The exchange keeps funds"
1965#~ " matching all unspent coins in an "
1966#~ "escrow bank account.</p> "
1967#~ msgstr ""
1968
1969#~ msgid ""
1970#~ "<p>Since the digital coins of value "
1971#~ "in your wallet are anonymized, the "
1972#~ "exchange can not assist you in "
1973#~ "recovering a lost or stolen wallet. "
1974#~ "Just like with a physical wallet "
1975#~ "for cash, you are responsible for "
1976#~ "keeping it safe.</p> "
1977#~ msgstr ""
1978
1979#~ msgid ""
1980#~ "<p>The risk of losing a wallet can"
1981#~ " be mitigated by making backups or"
1982#~ " keeping the balance reasonably low.</p>"
1983#~ " "
1984#~ msgstr ""
1985
1986#~ msgid ""
1987#~ "<p>In case of a compromise of one"
1988#~ " of your devices, an attacker can "
1989#~ "spend coins from your wallet. Checking"
1990#~ " your balance might reveal to you "
1991#~ "that your device has been "
1992#~ "compromised.</p> "
1993#~ msgstr ""
1994
1995#~ msgid ""
1996#~ "<p>If your friend provides goods or "
1997#~ "services for you in exchange for a"
1998#~ " payment, they can easily set up "
1999#~ "a Taler merchant and receive the "
2000#~ "payment in their bank account.</p> "
2001#~ msgstr ""
2002
2003#~ msgid ""
2004#~ "<p>Future versions of the Taler wallet"
2005#~ " may allow exchanging coins among "
2006#~ "friends directly as well.</p> "
2007#~ msgstr ""
2008
2009#~ msgid ""
2010#~ "<p>Taler wallets can store digital coins"
2011#~ " corresponding to multiple different "
2012#~ "currencies such as the Euro, US "
2013#~ "Dollars or Bitcoins.</p> "
2014#~ msgstr ""
2015
2016#~ msgid "<p>Taler currently does not offer conversion between currencies.</p> "
2017#~ msgstr ""
2018
2019#~ msgid ""
2020#~ "<p>Your wallet stores digital coins that"
2021#~ " are <a "
2022#~ "href=\"https://en.wikipedia.org/wiki/Blind_signature\">blindly "
2023#~ "signed</a> by an exchange. The use "
2024#~ "of a blind signature protects your "
2025#~ "privacy as it prevents the exchange "
2026#~ "from knowing which coin it signed "
2027#~ "for which customer.</p> "
2028#~ msgstr ""
2029
2030#~ msgid ""
2031#~ "trusted third party that verifies that"
2032#~ " the `exchange` is operating correctly \n"
2033#~ msgstr ""
2034
2035#~ msgid ""
2036#~ "traditional financial service provider who "
2037#~ "offers wire `transfers` between accounts \n"
2038#~ msgstr ""
2039
2040#~ msgid ""
2041#~ "coins are individual token representing "
2042#~ "a certain amount of value, also "
2043#~ "known as the `denomination` of the "
2044#~ "coin "
2045#~ msgstr ""
2046
2047#~ msgid "the proposal signed by the wallet. "
2048#~ msgstr ""
2049
2050#~ msgid ""
2051#~ "unit of currency, specifies both the "
2052#~ "currency and the face value of a"
2053#~ " `coin` "
2054#~ msgstr ""
2055
2056#~ msgid ""
2057#~ "RSA key used by the exchange to"
2058#~ " certify that a given `coin` is "
2059#~ "valid and of a particular `denomination`"
2060#~ " "
2061#~ msgstr ""
2062
2063#~ msgid ""
2064#~ "operation by which a merchant passes "
2065#~ "coins to an exchange, expecting the "
2066#~ "exchange to credit his `bank` account"
2067#~ " in the future using a wire "
2068#~ "`transfer` "
2069#~ msgstr ""
2070
2071#~ msgid ""
2072#~ "a `coin` is dirty if its public"
2073#~ " key may be known to an entity"
2074#~ " other than the customer, thereby "
2075#~ "creating the danger of some entity "
2076#~ "being able to link multiple transactions"
2077#~ " of coin's owner if the coin is"
2078#~ " not refreshed first "
2079#~ msgstr ""
2080
2081#~ msgid ""
2082#~ "Taler's payment service provider. Issues "
2083#~ "eletronic `coins` during `withdrawal` and "
2084#~ "redeems them when they are `deposited`"
2085#~ " by merchants. "
2086#~ msgstr ""
2087
2088#~ msgid "implementation of a `wallet` for browsers "
2089#~ msgstr ""
2090
2091#~ msgid "a `coin` is fresh if its public key is only known to the customer "
2092#~ msgstr ""
2093
2094#~ msgid ""
2095#~ "offline key used by the exchange "
2096#~ "to certify denomination keys and message"
2097#~ " signing keys "
2098#~ msgstr ""
2099
2100#~ msgid "key used by the exchange to sign online messages, other than coins "
2101#~ msgstr ""
2102
2103#~ msgid ""
2104#~ "specification of the details of a "
2105#~ "transaction, specifies the payment obligations"
2106#~ " for the customer (i.e. the amount),"
2107#~ " the deliverables of the merchant and"
2108#~ " other related information, such as "
2109#~ "deadlines or locations; However, it "
2110#~ "lacks some information that the backend"
2111#~ " is supposed to provide. In other "
2112#~ "words, after the backend adds the "
2113#~ "missing information to the offer and "
2114#~ "signs it, it becomes a proposal. "
2115#~ msgstr ""
2116
2117#~ msgid "a `coin` is owned by the entity that knows the private key of the coin "
2118#~ msgstr ""
2119
2120#~ msgid ""
2121#~ "message that cryptographically demonstrates "
2122#~ "that a particular claim is correct \n"
2123#~ msgstr ""
2124
2125#~ msgid "a sketch that has been completed and signed by the merchant backend. "
2126#~ msgstr ""
2127
2128#~ msgid ""
2129#~ "funds set aside for future use; "
2130#~ "either the balance of a customer "
2131#~ "at the exchange ready for `withdrawal`,"
2132#~ " or the funds kept in the "
2133#~ "exchange's bank account to cover "
2134#~ "obligations from coins in circulation "
2135#~ msgstr ""
2136
2137#~ msgid ""
2138#~ "operation by which a `dirty` `coin` "
2139#~ "is converted into one or more "
2140#~ "`fresh` coins "
2141#~ msgstr ""
2142
2143#~ msgid ""
2144#~ "operation by which a merchant steps "
2145#~ "back from the right to funds that"
2146#~ " he obtained from a `deposit` "
2147#~ "operation, giving the right to the "
2148#~ "funds back to the customer "
2149#~ msgstr ""
2150
2151#~ msgid ""
2152#~ "users can share ownership of a "
2153#~ "`coin` by sharing access to the "
2154#~ "coin's private key, thereby allowing all"
2155#~ " co-owners to spend the coin at"
2156#~ " any time. "
2157#~ msgstr ""
2158
2159#~ msgid "see message signing key. "
2160#~ msgstr ""
2161
2162#~ msgid ""
2163#~ "operation by which a customer gives "
2164#~ "a merchant the right to `deposit` "
2165#~ "coins in return for merchandise "
2166#~ msgstr ""
2167
2168#~ msgid "method of sending funds between `bank` accounts "
2169#~ msgstr ""
2170
2171#~ msgid ""
2172#~ "method by which ownership is exclusively"
2173#~ " transferred from one entity to "
2174#~ "another "
2175#~ msgstr ""
2176
2177#~ msgid "unique number by which a merchant identifies a `transaction` "
2178#~ msgstr ""
2179
2180#~ msgid ""
2181#~ "software running on a customer's "
2182#~ "computer; withdraws, stores and spends "
2183#~ "coins "
2184#~ msgstr ""
2185
2186#~ msgid "see `transfer` "
2187#~ msgstr ""
2188
2189#~ msgid ""
2190#~ "subject of a wire `transfer`; usually"
2191#~ " a random string to uniquely identify"
2192#~ " the `transfer` "
2193#~ msgstr ""
2194
2195#~ msgid ""
2196#~ "operation by which a `wallet` can "
2197#~ "convert funds from a reserve to "
2198#~ "fresh coins "
2199#~ msgstr ""
2200
2201#~ msgid ""
2202#~ "Taler provides accountability to ensure "
2203#~ "business operate legally, while also "
2204#~ "respecting civil liberties of citizens. "
2205#~ "Taler is a payment system based on"
2206#~ " open standards and free software. "
2207#~ "Taler needs governments as they set "
2208#~ "a financial framework and act as "
2209#~ "trusted regulators. Taler contributes to "
2210#~ "digital sovereignty in the critical "
2211#~ "financial infrastructure. "
2212#~ msgstr ""
2213
2214#~ msgid ""
2215#~ "Taler was built with the goal of"
2216#~ " fighting corruption and supporting "
2217#~ "taxation. With Taler, the receiver of"
2218#~ " any form of payment is easily "
2219#~ "identified by the government, and the"
2220#~ " merchant can be compelled to provide"
2221#~ " the contract that was accepted by"
2222#~ " the customer. Governments can use "
2223#~ "this data to tax businesses and "
2224#~ "individuals based on their income, "
2225#~ "making tax evasion and black markets "
2226#~ "less viable. "
2227#~ msgstr ""
2228
2229#~ msgid ""
2230#~ "Thus, despite offering anonymity for "
2231#~ "citizens spending digital cash to buy"
2232#~ " goods and services, Taler also "
2233#~ "ensures that the state can observe "
2234#~ "incoming funds. This can be used "
2235#~ "to ensure businesses engage only in "
2236#~ "legal activities, and do not evade "
2237#~ "income tax, sales tax or value-"
2238#~ "added tax. However, this observational "
2239#~ "capability does not extend to the "
2240#~ "immediate personal domain. In particular, "
2241#~ "monitoring does not cover shared access"
2242#~ " to funds with trusted friends and"
2243#~ " family, or synchronizing wallets across"
2244#~ " multiple devices. "
2245#~ msgstr ""
2246
2247#~ msgid ""
2248#~ "Taler's payments are cryptographically "
2249#~ "secured. Thus, customers, merchants and "
2250#~ "the Taler payment service provider (the"
2251#~ " exchange) can mathematically demonstrate "
2252#~ "their lawful behavior in court in "
2253#~ "case of disputes. Financial damages are"
2254#~ " strictly limited, improving economic "
2255#~ "security for individuals, merchants, the "
2256#~ "exchange and the state. "
2257#~ msgstr ""
2258
2259#~ msgid ""
2260#~ "As a payment service provider, the "
2261#~ "Taler exchange is subject to financial"
2262#~ " regulation. Financial regulation and "
2263#~ "regular audits are critical to establish"
2264#~ " trust. In particular, the Taler "
2265#~ "design mandates the existence of an "
2266#~ "independent auditor who checks cryptographic"
2267#~ " proofs that accumulate at the "
2268#~ "exchange to ensure that the escrow "
2269#~ "account is managed honestly. This "
2270#~ "ensures that the exchange does not "
2271#~ "threaten the economy due to fraud. \n"
2272#~ msgstr ""
2273
2274#~ msgid ""
2275#~ "Taler is free software implementing an"
2276#~ " open protocol standard. Thus, Taler "
2277#~ "will enable competition and avoid the"
2278#~ " monopolization of payment systems that "
2279#~ "threatens global political and financial "
2280#~ "stability today. "
2281#~ msgstr ""
2282
2283#~ msgid ""
2284#~ "Taler has an efficient design. Unlike"
2285#~ " Blockchain-based payment systems, such "
2286#~ "as Bitcoin, Taler will not threaten "
2287#~ "the availability of national electric "
2288#~ "grids or (significantly) contribute to "
2289#~ "environmental pollution. "
2290#~ msgstr ""
2291
2292#~ msgid ""
2293#~ "Taler assumes governments can observe "
2294#~ "traditional wire transfers entering and "
2295#~ "leaving the Taler payment system. "
2296#~ "Starting with the wire transfers, "
2297#~ "governments can obtain: "
2298#~ msgstr ""
2299
2300#~ msgid ""
2301#~ "The total amount of digital currency "
2302#~ "withdrawn by a customer. The government"
2303#~ " can impose limits on how much "
2304#~ "digital cash a customer can withdraw "
2305#~ "within a given time frame. "
2306#~ msgstr ""
2307
2308#~ msgid "The income received by any merchant via the Taler system. "
2309#~ msgstr ""
2310
2311#~ msgid ""
2312#~ "The exact details of the underlying "
2313#~ "contract that was signed between "
2314#~ "customer and merchant. However, this "
2315#~ "information would typically not include "
2316#~ "the identity of the customer. "
2317#~ msgstr ""
2318
2319#~ msgid ""
2320#~ "The amounts of digital coins "
2321#~ "legitimately withdrawn by customers from "
2322#~ "the exchange, the value of non-"
2323#~ "redeemed digital coins in customer's "
2324#~ "wallets, the value and corresponding "
2325#~ "wire details of deposit operations "
2326#~ "performed by merchants with the "
2327#~ "exchange, and the income of the "
2328#~ "exchange from transaction fees. "
2329#~ msgstr ""
2330
2331#~ msgid ""
2332#~ "GNU Taler is an electronic payment "
2333#~ "system under development at <a "
2334#~ "href=\"http://www.inria.fr/\">Inria</a>. We expect "
2335#~ "to make it operational in 2017. "
2336#~ "You can learn about Taler on this"
2337#~ " website, try the <a "
2338#~ "href=\"https://demo.taler.net\">demo</a> and look at"
2339#~ " our <a href=\"https://docs.taler.net\">developer</a>"
2340#~ " and <a href=\"https://api.taler.net\">API</a> "
2341#~ "documentation. "
2342#~ msgstr ""
2343
2344#~ msgid ""
2345#~ "Taler is easy to integrate with "
2346#~ "existing Web applications. Payments are "
2347#~ "cryptographically secured and are confirmed"
2348#~ " within milliseconds with extremely low "
2349#~ "transaction costs. "
2350#~ msgstr ""
2351
2352#~ msgid ""
2353#~ "Taler does not introduce a new "
2354#~ "currency. Taler uses a digital wallet"
2355#~ " storing coins and payment service "
2356#~ "providers with escrow accounts in "
2357#~ "existing currencies. Thus, Taler's "
2358#~ "cryptographic coins correspond to existing "
2359#~ "currencies, such as US Dollars, Euros"
2360#~ " or even Bitcoins. "
2361#~ msgstr ""
2362
2363#~ msgid ""
2364#~ "By design Taler does not suffer "
2365#~ "from many classes of security problems"
2366#~ " such as phishing or counterfeit. "
2367#~ "Thanks to its security features, Taler"
2368#~ " never rejects a legitimate customer "
2369#~ "due to a fraud-detection false "
2370#~ "positive. "
2371#~ msgstr ""
2372
2373#~ msgid ""
2374#~ "When using Taler, merchant's revenue is"
2375#~ " transparent for tax collection "
2376#~ "authorities. Unlike cash and most "
2377#~ "digital currencies, Taler helps prevent "
2378#~ "black markets. Taler is not suitable"
2379#~ " for illegal activities. "
2380#~ msgstr ""
2381
2382#~ msgid ""
2383#~ "When you pay with Taler, your "
2384#~ "identity does not have to be "
2385#~ "revealed. Just like payments in cash,"
2386#~ " nobody else can track how you "
2387#~ "spent your electronic money. However, "
2388#~ "you obtain a legally valid proof "
2389#~ "of payment. "
2390#~ msgstr ""
2391
2392#~ msgid ""
2393#~ "Taler provides protocols and reference "
2394#~ "implementations that in principle enables "
2395#~ "anybody to run their own payment "
2396#~ "infrastructure, be it individuals, "
2397#~ "organizations or whole countries. Since "
2398#~ "the reference implementation is a <a "
2399#~ "href=\"http://www.gnu.org/\">GNU</a> package, it "
2400#~ "will always remain free software. "
2401#~ msgstr ""
2402
2403#~ msgid ""
2404#~ "<p>To pay with Taler, customers install"
2405#~ " an electronic wallet on their "
2406#~ "device. Before the first payment, the"
2407#~ " wallet's balance must be charged in"
2408#~ " the desired currency by some other"
2409#~ " means of payment.</p> <p>Once the "
2410#~ "wallet is charged, payments on websites"
2411#~ " take only one click, are never "
2412#~ "falsely rejected by fraud detection and"
2413#~ " do not pose any risk of "
2414#~ "phishing or identity theft.</p> "
2415#~ msgstr ""
2416
2417#~ msgid ""
2418#~ "<p>To receive Taler payments, a merchant"
2419#~ " needs a bank account in the "
2420#~ "desired currency. We provide supporting "
2421#~ "software in various programming languages "
2422#~ "to make the integration painless. The"
2423#~ " merchant's backend for Taler transaction"
2424#~ " processing can run on the merchant's"
2425#~ " premises or be hosted by a "
2426#~ "third party.</p> "
2427#~ msgstr ""
2428
2429#~ msgid ""
2430#~ "We have created a company, Taler "
2431#~ "Systems SA in Luxembourg.<br> Please "
2432#~ "contact <tt>invest@taler.net</tt> if you want"
2433#~ " to invest in Taler. "
2434#~ msgstr ""
2435
2436#~ msgid ""
2437#~ "Our <a href=\"about.html\">team</a> combines "
2438#~ "world-class business leaders, cryptographers, "
2439#~ "software engineers, civil-rights activists "
2440#~ "and academics. We are unified by a"
2441#~ " vision of how payments should work"
2442#~ " and the goal of imposing this "
2443#~ "vision upon the world. "
2444#~ msgstr ""
2445
2446#~ msgid ""
2447#~ "We are currently supported by <a "
2448#~ "href=\"http://www.inria.fr/\">Inria</a>, the French "
2449#~ "national institute for research in "
2450#~ "informatics and automation, and the <a"
2451#~ " href=\"https://renewablefreedom.org/\">Renewable Freedom "
2452#~ "Foundation</a>. "
2453#~ msgstr ""
2454
2455#~ msgid ""
2456#~ "All transactions in Taler are secured"
2457#~ " using <a href=\"bibliography.html\">modern "
2458#~ "cryptography</a> and trust in all "
2459#~ "parties is minimized. Financial damage "
2460#~ "is bounded (for customers, merchants and"
2461#~ " the exchange) even in the case "
2462#~ "that systems are compromised and private"
2463#~ " keys are stolen. Databases can be"
2464#~ " audited for consistency, resulting in "
2465#~ "either the detection of compromised "
2466#~ "systems or the demonstration that "
2467#~ "participants were honest. Actual transaction"
2468#~ " costs are fractions of a cent. \n"
2469#~ msgstr ""
2470
2471#~ msgid ""
2472#~ "The scalable business model for Taler"
2473#~ " is the operation of the payment "
2474#~ "service provider, which converts money "
2475#~ "from traditional payment systems (MasterCard,"
2476#~ " SEPA, UPI, Visa, Bitcoin, ACH, "
2477#~ "SWIFT, etc.) to anonymous electronic "
2478#~ "coins in the same currency. The "
2479#~ "customer can then redeem the electronic"
2480#~ " coins at a merchant, who can "
2481#~ "exchange them for money represented "
2482#~ "using traditional payment systems at the"
2483#~ " exchange. The exchange charges fees "
2484#~ "to facilitate the transactions. "
2485#~ msgstr ""
2486
2487#~ msgid ""
2488#~ "The payment service operator runs the"
2489#~ " <em>Taler exchange</em>. The exchange "
2490#~ "charges <b>transaction fees</b> to customers"
2491#~ " or merchants. Its operational expenses "
2492#~ "are from wire transfers with the "
2493#~ "banking system and the operation of "
2494#~ "the computing infrastructure. "
2495#~ msgstr ""
2496
2497#~ msgid ""
2498#~ "Taler is a cost-effective electronic "
2499#~ "payment system which provides you with"
2500#~ " cryptographic proof that the payment "
2501#~ "worked correctly within milliseconds. Your "
2502#~ "Web customers pay with previously "
2503#~ "unknown levels of convenience without "
2504#~ "risk of fraud. "
2505#~ msgstr ""
2506
2507#~ msgid ""
2508#~ "Processing transactions with Taler is "
2509#~ "fast, allowing you to confirm the "
2510#~ "transaction with your customer virtually "
2511#~ "immediately. Your customers will appreciate"
2512#~ " that they do not have to type"
2513#~ " in credit card information and play"
2514#~ " the &quot;verified by&quot; game. By "
2515#~ "making payments significantly more convenient"
2516#~ " for your customers, you may be "
2517#~ "able to use Taler for small "
2518#~ "transactions that would not work with"
2519#~ " credit card payments due to the "
2520#~ "mental overhead for customers. "
2521#~ msgstr ""
2522
2523#~ msgid ""
2524#~ "You will have cryptographic proof of "
2525#~ "payment from the Taler payment service"
2526#~ " provider. With Taler you never "
2527#~ "handle sensitive customer account information"
2528#~ " and thus do not have to "
2529#~ "undergo any particular security audits "
2530#~ "(such as PCI DSS). Your systems "
2531#~ "will have customer contracts with "
2532#~ "qualified signatures for all transactions "
2533#~ "which you can use in court in "
2534#~ "case of disputes. "
2535#~ msgstr ""
2536
2537#~ msgid ""
2538#~ "Taler is free software, and you "
2539#~ "can use the liberally-licensed reference"
2540#~ " code as a starting point to "
2541#~ "integrate Taler into your services. To"
2542#~ " use Taler, you do not need to"
2543#~ " pay license fees, and the free "
2544#~ "software development model will ensure "
2545#~ "that you can select from many "
2546#~ "competing integrators for support. "
2547#~ msgstr ""
2548
2549#~ msgid ""
2550#~ "Taler is uses efficient cryptographic "
2551#~ "constructions with low bandwidth and "
2552#~ "storage requirements. Combined with Taler's"
2553#~ " strong security which makes fraud "
2554#~ "impossible, Taler payment service providers"
2555#~ " can operate with very low overhead"
2556#~ " and thus offer low transaction fees."
2557#~ " "
2558#~ msgstr ""
2559
2560#~ msgid ""
2561#~ "Taler can be used for different "
2562#~ "currencies (such as Euros, US Dollars"
2563#~ " or Bitcoins) and any amount, limited"
2564#~ " only by applicable regulatation and "
2565#~ "what denominations the payment service "
2566#~ "provider supports. "
2567#~ msgstr ""
2568
2569#~ msgid ""
2570#~ "Taler prevents tax evasion and money "
2571#~ "laundering. Taler's protocols are efficient"
2572#~ " and do not use wasteful proof-"
2573#~ "of-work calculations. Taler encourages "
2574#~ "transparency by providing an open "
2575#~ "standard and free software reference "
2576#~ "implementations. "
2577#~ msgstr ""
2578
2579#~ msgid ""
2580#~ "The backend <b>signs</b> and <b>stores</b> "
2581#~ "the complete terms of offers made "
2582#~ "by the merchant to customers. For "
2583#~ "this, the merchant's frontend needs to"
2584#~ " give the customer's order in a "
2585#~ "JSON format to the backend. "
2586#~ msgstr ""
2587
2588#~ msgid ""
2589#~ "The backend <b>validates</b> payments received"
2590#~ " from the wallet and <b>executes</b> "
2591#~ "them with the Taler payment service "
2592#~ "provider (the exchange). For this, the"
2593#~ " merchant's frontend must pass the "
2594#~ "payment request through to the Taler "
2595#~ "backend and check the HTTP status "
2596#~ "code that is returned. "
2597#~ msgstr ""
2598
2599#~ msgid ""
2600#~ "The backend can <b>list</b> completed "
2601#~ "transactions and <b>map</b> wire transfers "
2602#~ "to sets of business transactions, "
2603#~ "including the exact terms of each "
2604#~ "contract. "
2605#~ msgstr ""
2606
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-16 21:32:38 +0000