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, 1405 insertions, 491 deletions
diff --git a/locale/en/LC_MESSAGES/messages.po b/locale/en/LC_MESSAGES/messages.po
index 8e3d522d..bb3307fe 100644
--- a/locale/en/LC_MESSAGES/messages.po
+++ b/locale/en/LC_MESSAGES/messages.po
@@ -1,18 +1,23 @@
1 1
2msgid "" 2msgid ""
3msgstr "" 3msgstr ""
4"Project-Id-Version: PROJECT VERSION\n" 4"Project-Id-Version: PROJECT VERSION Report-Msgid-Bugs-To: EMAIL@ADDRESS "
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"
5"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" 10"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
6"POT-Creation-Date: 2017-05-23 10:32+0200\n" 11"POT-Creation-Date: 2017-06-02 13:48+0200\n"
7"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" 12"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
8"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" 13"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
9"Language: en\n" 14"Language: en\n"
10"Language-Team: en <LL@li.org>\n" 15"Language-Team: en <LL@li.org>\n"
11"Plural-Forms: nplurals=2; plural=(n!=1)\n" 16"Plural-Forms: nplurals=2; plural=(n != 1)\n"
12"MIME-Version: 1.0\n" 17"MIME-Version: 1.0\n"
13"Content-Type: text/plain; charset=utf-8\n" 18"Content-Type: text/plain; charset=utf-8\n"
14"Content-Transfer-Encoding: 8bit\n" 19"Content-Transfer-Encoding: 8bit\n"
15"Generated-By: Babel 2.3.4\n" 20"Generated-By: Babel 2.4.0\n"
16 21
17#: about.html.j2:8 22#: about.html.j2:8
18msgid "" 23msgid ""
@@ -109,11 +114,9 @@ msgstr ""
109 114
110#: citizens.html.j2:9 115#: citizens.html.j2:9
111msgid "" 116msgid ""
112"Taler largely functions like digital cash. You\n" 117"Taler largely functions like digital cash. You withdraw money from your "
113"withdraw money from your bank account into your\n" 118"bank account into your electronic wallet, and can henceforth spend "
114"electronic wallet, and can henceforth spend digital\n" 119"digital cash. The electronic wallet can carry multiple currencies."
115"cash. The electronic wallet can carry multiple\n"
116"currencies.\n"
117msgstr "" 120msgstr ""
118 121
119#: citizens.html.j2:25 governments.html.j2:58 index.html.j2:56 122#: citizens.html.j2:25 governments.html.j2:58 index.html.j2:56
@@ -123,12 +126,10 @@ msgstr ""
123 126
124#: citizens.html.j2:27 127#: citizens.html.j2:27
125msgid "" 128msgid ""
126"Taler uses modern cryptography, ensuring that there\n" 129"Taler uses modern cryptography, ensuring that there is no counterfeit. "
127"is no counterfeit. Your digital wallet is safer\n" 130"Your digital wallet is safer than your physical wallet. At most, you can "
128"than your physical wallet. At most, you can lose\n" 131"lose its contents because your computer or mobile is irreparably damaged "
129"its contents because your computer or mobile is\n" 132"or compromised. Unlike a physical wallet, you can make backups to secure "
130"irreparably damaged or compromised. Unlike a\n"
131"physical wallet, you can make backups to secure\n"
132"against data loss." 133"against data loss."
133msgstr "" 134msgstr ""
134 135
@@ -138,12 +139,10 @@ msgstr ""
138 139
139#: citizens.html.j2:39 140#: citizens.html.j2:39
140msgid "" 141msgid ""
141"Your transactions are private, neither the payment\n" 142"Your transactions are private, neither the payment service provider nor "
142"service provider nor merchant needs to learn your\n" 143"merchant needs to learn your identity. There is no need to give out "
143"identity. There is no need to give out credit card\n" 144"credit card numbers or other sensitive information. The merchant will "
144"numbers or other sensitive information. The merchant\n" 145"only be able to do exactly the transaction you agreed to."
145"will only be able to do exactly the transaction you\n"
146"agreed to."
147msgstr "" 146msgstr ""
148 147
149#: citizens.html.j2:50 148#: citizens.html.j2:50
@@ -152,11 +151,10 @@ msgstr ""
152 151
153#: citizens.html.j2:52 152#: citizens.html.j2:52
154msgid "" 153msgid ""
155"You will be able to withdraw money to replenish the\n" 154"You will be able to withdraw money to replenish the digital coins in your"
156"digital coins in your wallet using your credit card\n" 155" wallet using your credit card or wire transfers. Afterwards you can pay "
157"or wire transfers. Afterwards you can pay with\n" 156"with one-click using the Taler wallet, which optionally keeps your "
158"one-click using the Taler wallet, which optionally\n" 157"transaction history on your computer."
159"keeps your transaction history on your computer."
160msgstr "" 158msgstr ""
161 159
162#: citizens.html.j2:61 index.html.j2:42 160#: citizens.html.j2:61 index.html.j2:42
@@ -165,12 +163,10 @@ msgstr ""
165 163
166#: citizens.html.j2:63 164#: citizens.html.j2:63
167msgid "" 165msgid ""
168"Coins in your digital wallet will be of the same\n" 166"Coins in your digital wallet will be of the same denomination as the cash"
169"denomination as the cash in your physical wallet.\n" 167" in your physical wallet. Taler is not a crypto-currency, so you do not "
170"Taler is not a crypto-currency, so you do not have\n" 168"have to worry about cryto-currency related value fluctuations. Banking "
171"to worry about cryto-currency related value\n" 169"with Taler is subject to the usual government protections for financial "
172"fluctuations. Banking with Taler is subject to the\n"
173"usual government protections for financial\n"
174"services." 170"services."
175msgstr "" 171msgstr ""
176 172
@@ -181,9 +177,8 @@ msgstr ""
181#: citizens.html.j2:81 177#: citizens.html.j2:81
182msgid "" 178msgid ""
183"We currently provide a <a href=\"wallet.html\">wallet browser " 179"We currently provide a <a href=\"wallet.html\">wallet browser "
184"extension</a> for Chromium, Chrome, Firefox, Opera\n" 180"extension</a> for Chromium, Chrome, Firefox, Opera and Edge. Wallets for "
185"and Edge. Wallets for mobile phones and other platforms will be " 181"mobile phones and other platforms will be available in the future."
186"available in the future.\n"
187msgstr "" 182msgstr ""
188 183
189#: citizens.html.j2:88 184#: citizens.html.j2:88
@@ -193,7 +188,7 @@ msgstr ""
193#: citizens.html.j2:90 188#: citizens.html.j2:90
194msgid "" 189msgid ""
195"You can see how Taler works in practice by visiting our <a " 190"You can see how Taler works in practice by visiting our <a "
196"href=\"https://demo.taler.net\">demo page</a>.\n" 191"href=\"https://demo.taler.net\">demo page</a>."
197msgstr "" 192msgstr ""
198 193
199#: citizens.html.j2:103 194#: citizens.html.j2:103
@@ -201,39 +196,32 @@ msgid "The Taler Wallet for customers"
201msgstr "" 196msgstr ""
202 197
203#: citizens.html.j2:105 198#: citizens.html.j2:105
204msgid "" 199msgid "Customers interact with the Taler system using the Taler wallet:"
205"Customers interact with the Taler system using\n"
206"the Taler wallet:"
207msgstr "" 200msgstr ""
208 201
209#: citizens.html.j2:110 202#: citizens.html.j2:110
210msgid "" 203msgid ""
211"To <b>withdraw</b> electronic coins, the customer\n" 204"To <b>withdraw</b> electronic coins, the customer transfers funds from "
212"transfers funds from his bank account to the Taler\n" 205"his bank account to the Taler payment service provider (the exchange). "
213"payment service provider (the exchange). The wire\n" 206"The wire transfer subject must match a code identifying the customer's "
214"transfer subject must match a code identifying the\n" 207"wallet. After the wire transfer is complete, the wallet will "
215"customer's wallet. After the wire transfer is\n" 208"automatically withdraw the coins from the exchange."
216"complete, the wallet will automatically withdraw the\n"
217"coins from the exchange."
218msgstr "" 209msgstr ""
219 210
220#: citizens.html.j2:118 211#: citizens.html.j2:118
221msgid "" 212msgid ""
222"To <b>spend</b> electronic coins, a merchant must\n" 213"To <b>spend</b> electronic coins, a merchant must cause the wallet to "
223"cause the wallet to display a proposal for some\n" 214"display a proposal for some purchase. The wallet will ask the customer "
224"purchase. The wallet will ask the customer for\n" 215"for one-click confirmation. Payment is then instant. Transaction "
225"one-click confirmation. Payment is then instant.\n" 216"histories and digitally signed contracts can be preserved by the wallet."
226"Transaction histories and digitally signed contracts\n"
227"can be preserved by the wallet."
228msgstr "" 217msgstr ""
229 218
230#: citizens.html.j2:125 219#: citizens.html.j2:125
231msgid "" 220msgid ""
232"The customer can use the wallet to <b>review</b> his\n" 221"The customer can use the wallet to <b>review</b> his balance. The wallet "
233"balance. The wallet can contain different\n" 222"can contain different currencies, and may be shared across devices. "
234"currencies, and may be shared across\n" 223"Customers can make backups of the wallet to secure its contents against "
235"devices. Customers can make backups of the wallet to\n" 224"hardware failures."
236"secure its contents against hardware failures."
237msgstr "" 225msgstr ""
238 226
239#: contact.html.j2:6 227#: contact.html.j2:6
@@ -246,12 +234,10 @@ msgstr ""
246 234
247#: contact.html.j2:15 235#: contact.html.j2:15
248msgid "" 236msgid ""
249"An archived, public mailing list for GNU Taler is\n" 237"An archived, public mailing list for GNU Taler is hosted at <a "
250"hosted at\n"
251"<a "
252"href=\"https://lists.gnu.org/mailman/listinfo/taler\">https://lists.gnu.org/mailman/listinfo/taler</a>." 238"href=\"https://lists.gnu.org/mailman/listinfo/taler\">https://lists.gnu.org/mailman/listinfo/taler</a>."
253" You can send messages to the list\n" 239" You can send messages to the list at <a "
254"at <a href=\"mailto:taler@gnu.org\">taler@gnu.org</a>.\n" 240"href=\"mailto:taler@gnu.org\">taler@gnu.org</a>."
255msgstr "" 241msgstr ""
256 242
257#: contact.html.j2:25 243#: contact.html.j2:25
@@ -260,9 +246,8 @@ msgstr ""
260 246
261#: contact.html.j2:27 247#: contact.html.j2:27
262msgid "" 248msgid ""
263"Team members are generally reachable at\n" 249"Team members are generally reachable at <tt>LASTNAME@taler.net</tt>. All "
264"<tt>LASTNAME@taler.net</tt>. All of us\n" 250"of us support receiving GnuPG encrypted e-mails."
265"support receiving GnuPG encrypted e-mails.\n"
266msgstr "" 251msgstr ""
267 252
268#: contact.html.j2:36 253#: contact.html.j2:36
@@ -271,11 +256,10 @@ msgstr ""
271 256
272#: contact.html.j2:38 257#: contact.html.j2:38
273msgid "" 258msgid ""
274"We track open feature requests and bugs in our\n" 259"We track open feature requests and bugs in our <a "
275"<a href=\"https://gnunet.org/bugs/\">Bug tracker</a>,\n" 260"href=\"https://gnunet.org/bugs/\">Bug tracker</a>, which is shared with "
276"which is shared with the GNUnet project.\n" 261"the GNUnet project. You can also report bugs or feature requests to the "
277"You can also report bugs or feature requests to the\n" 262"mailing list."
278"mailing list.\n"
279msgstr "" 263msgstr ""
280 264
281#: contact.html.j2:49 265#: contact.html.j2:49
@@ -284,8 +268,39 @@ msgstr ""
284 268
285#: contact.html.j2:51 269#: contact.html.j2:51
286msgid "" 270msgid ""
287"For non-technical commercial requests, please contact\n" 271"For non-technical commercial requests, please contact <tt>ceo AT "
288"<tt>ceo AT taler.net</tt>.\n" 272"taler.net</tt>."
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>"
289msgstr "" 304msgstr ""
290 305
291#: developers.html.j2:5 306#: developers.html.j2:5
@@ -298,17 +313,14 @@ msgstr ""
298 313
299#: developers.html.j2:15 314#: developers.html.j2:15
300msgid "" 315msgid ""
301"GNU Taler is free software implementing an open\n" 316"GNU Taler is free software implementing an open protocol. Anybody is "
302"protocol. Anybody is welcome to integrate our reference\n" 317"welcome to integrate our reference implementation into their "
303"implementation into their applications. Different\n" 318"applications. Different components of Taler are being made available "
304"components of Taler are being made available under\n" 319"under different licenses. The Affero GPLv3+ is used for the exchange, the"
305"different licenses. The Affero GPLv3+ is used for the\n" 320" LGPLv3+ is used for reference code demonstrating integration with "
306"exchange, the LGPLv3+ is used for reference code\n" 321"merchant platforms, and licenses like GPLv3+ are used for wallets and "
307"demonstrating integration with merchant platforms, and\n" 322"related customer-facing software. We are open for constructive "
308"licenses like GPLv3+ are used for\n" 323"suggestions for maximizing the adoption of this payment platform."
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"
312msgstr "" 324msgstr ""
313 325
314#: developers.html.j2:32 326#: developers.html.j2:32
@@ -317,18 +329,14 @@ msgstr ""
317 329
318#: developers.html.j2:35 330#: developers.html.j2:35
319msgid "" 331msgid ""
320"Taler is designed to work on the Internet. To\n" 332"Taler is designed to work on the Internet. To ensure that Taler payments "
321"ensure that Taler payments can work with\n" 333"can work with restrictive network setups, Taler uses a RESTful protocol "
322"restrictive network setups, Taler uses a RESTful\n" 334"over HTTP or HTTPS. Taler's security does not depend upon the use of "
323"protocol over HTTP or HTTPS. Taler's security does\n" 335"HTTPS, but obviously merchants may choose to offer HTTPS for consistency "
324"not depend upon the use of HTTPS, but obviously\n" 336"and because it generally is better for privacy compared to HTTP. Taler "
325"merchants may choose to offer HTTPS for consistency\n" 337"uses JSON to encode structure data, making it easy to integrate Taler "
326"and because it generally is better for privacy\n" 338"with existing Web applications. Taler's protocol is documented in detail "
327"compared to HTTP. Taler uses JSON to encode\n" 339"at <a href=\"https://api.taler.net/\">api.taler.net</a>."
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"
332msgstr "" 340msgstr ""
333 341
334#: developers.html.j2:58 342#: developers.html.j2:58
@@ -337,15 +345,13 @@ msgstr ""
337 345
338#: developers.html.j2:61 346#: developers.html.j2:61
339msgid "" 347msgid ""
340"Taler is currently primarily developed by a\n" 348"Taler is currently primarily developed by a research team at <a "
341"research team at <a href=\"http://www.inria.fr/\">Inria</a> and\n" 349"href=\"http://www.inria.fr/\">Inria</a> and <a "
342"<a href=\"https://gnunet.org/\">GNUnet</a>. However,\n" 350"href=\"https://gnunet.org/\">GNUnet</a>. However, contributions from "
343"contributions from anyone are welcome. Our Git\n" 351"anyone are welcome. Our Git repositories can be cloned using the Git and "
344"repositories can be cloned using the Git and HTTP\n" 352"HTTP access methods against <tt>git.taler.net</tt> with the name of the "
345"access methods against <tt>git.taler.net</tt> with\n" 353"respective repository. A list of repositories can be found in our <a "
346"the name of the respective repository. A list of\n" 354"href=\"https://git.taler.net/\">GitWeb</a>."
347"repositories can be found in\n"
348"our <a href=\"https://git.taler.net/\">GitWeb</a>.\n"
349msgstr "" 355msgstr ""
350 356
351#: developers.html.j2:75 357#: developers.html.j2:75
@@ -354,11 +360,10 @@ msgstr ""
354 360
355#: developers.html.j2:78 361#: developers.html.j2:78
356msgid "" 362msgid ""
357"In addition to this website, the <a\n" 363"In addition to this website, the <a "
358"href=\"https://git.taler.net/\">documented code</a> and\n" 364"href=\"https://git.taler.net/\">documented code</a> and the <a "
359"the <a href=\"https://api.taler.net/\">API\n" 365"href=\"https://api.taler.net/\">API documentation</a>. Technical papers "
360"documentation</a>. Technical papers can be found in\n" 366"can be found in our <a href=\"bibliography.html\">bibliography</a>."
361"our <a href=\"bibliography.html\">bibliography</a>.\n"
362msgstr "" 367msgstr ""
363 368
364#: developers.html.j2:88 369#: developers.html.j2:88
@@ -367,11 +372,9 @@ msgstr ""
367 372
368#: developers.html.j2:91 373#: developers.html.j2:91
369msgid "" 374msgid ""
370"We have a mailing list for developer discussions.\n" 375"We have a mailing list for developer discussions. You can subscribe to or"
371"You can subscribe to or read the list archive at\n" 376" read the list archive at <a "
372"<a "
373"href=\"http://lists.gnu.org/mailman/listinfo/taler\">http://lists.gnu.org/mailman/listinfo/taler</a>." 377"href=\"http://lists.gnu.org/mailman/listinfo/taler\">http://lists.gnu.org/mailman/listinfo/taler</a>."
374"\n"
375msgstr "" 378msgstr ""
376 379
377#: developers.html.j2:101 380#: developers.html.j2:101
@@ -380,10 +383,9 @@ msgstr ""
380 383
381#: developers.html.j2:104 384#: developers.html.j2:104
382msgid "" 385msgid ""
383"We have <a href=\"https://buildbot.net/\">Buildbot</a>\n" 386"We have <a href=\"https://buildbot.net/\">Buildbot</a> automation tests "
384"automation tests to detect regressions and check for\n" 387"to detect regressions and check for portability at <a "
385"portability at <a\n" 388"href=\"https://buildbot.taler.net/\">buildbot.taler.net</a>."
386"href=\"https://buildbot.taler.net/\">buildbot.taler.net</a>.\n"
387msgstr "" 389msgstr ""
388 390
389#: developers.html.j2:113 391#: developers.html.j2:113
@@ -392,11 +394,9 @@ msgstr ""
392 394
393#: developers.html.j2:116 395#: developers.html.j2:116
394msgid "" 396msgid ""
395"We use\n" 397"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\">LCOV</a> "
396"<a href=\"http://ltp.sourceforge.net/coverage/lcov.php\">LCOV</a>\n" 398"to analyze the code coverage of our tests, the results are available at "
397"to analyze the code coverage of our tests, the\n" 399"<a href=\"https://lcov.taler.net/\">lcov.taler.net</a>."
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,11 +405,9 @@ msgstr ""
405 405
406#: developers.html.j2:129 406#: developers.html.j2:129
407msgid "" 407msgid ""
408"We\n" 408"We use <a href=\"https://gnunet.org/gauger\">Gauger</a> for performance "
409"use <a href=\"https://gnunet.org/gauger\">Gauger</a>\n" 409"regression analysis of the exchange backend at <a "
410"for performance regression analysis of the exchange\n" 410"href=\"https://gauger.taler.net/\">gauger.taler.net</a>."
411"backend\n"
412"at <a href=\"https://gauger.taler.net/\">gauger.taler.net</a>.\n"
413msgstr "" 411msgstr ""
414 412
415#: developers.html.j2:145 413#: developers.html.j2:145
@@ -418,120 +416,88 @@ msgstr ""
418 416
419#: developers.html.j2:148 417#: developers.html.j2:148
420msgid "" 418msgid ""
421"The Taler system consists of protocols executed among\n" 419"The Taler system consists of protocols executed among a number of actors "
422"a number of actors as illustrated in the illustration on the right.\n" 420"as illustrated in the illustration on the right. Typical transactions "
423"Typical transactions involve the following steps:\n" 421"involve the following steps:"
424msgstr "" 422msgstr ""
425 423
426#: developers.html.j2:158 424#: developers.html.j2:158
427msgid "" 425msgid ""
428"A customer instructs his <b>bank</b> to\n" 426"A customer instructs his <b>bank</b> to transfer funds from his account "
429"transfer funds from his account to the Taler\n" 427"to the Taler exchange (top left). In the subject of the transaction, he "
430"exchange (top left). In the subject of the\n" 428"includes an authentication token from his electronic <b>wallet</b>. In "
431"transaction, he includes an authentication\n" 429"Taler terminology, the customer creates a reserve at the exchange."
432"token from his electronic <b>wallet</b>. In\n"
433"Taler terminology, the customer creates a\n"
434"reserve at the exchange.\n"
435msgstr "" 430msgstr ""
436 431
437#: developers.html.j2:170 432#: developers.html.j2:170
438msgid "" 433msgid ""
439"Once the exchange has received the wire\n" 434"Once the exchange has received the wire transfer, it allows the "
440"transfer, it allows the customer's electronic\n" 435"customer's electronic wallet to <b>withdraw</b> electronic coins. The "
441"wallet to <b>withdraw</b> electronic coins.\n" 436"electronic coins are digital representations of the original currency "
442"The electronic coins are digital\n" 437"from the transfer. It is important to note that the exchange does not "
443"representations of the original currency from\n" 438"learn the &quot;serial numbers&quot; of the coins created in this "
444"the transfer. It is important to note that the\n" 439"process, so it cannot tell later which customer purchased what at which "
445"exchange does not learn the &quot;serial\n" 440"merchant. The use of Taler does not change the currency or the total "
446"numbers&quot; of the coins created in this\n" 441"value of the funds (except for fees which the exchange may charge for the"
447"process, so it cannot tell later which customer\n" 442" service)."
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"
452msgstr "" 443msgstr ""
453 444
454#: developers.html.j2:188 445#: developers.html.j2:188
455msgid "" 446msgid ""
456"Once the customer has the digital coins in his\n" 447"Once the customer has the digital coins in his wallet, the wallet can be "
457"wallet, the wallet can be used to <b>spend</b>\n" 448"used to <b>spend</b> the coins with merchant portals that support the "
458"the coins with merchant portals that support\n" 449"Taler payment system and accept the respective exchange as a business "
459"the Taler payment system and accept the\n" 450"partner (bottom arrow). This creates a digital contract signed by the "
460"respective exchange as a business partner\n" 451"customer's coins and the merchant. If necessary, the customer can later "
461"(bottom arrow). This creates a digital contract\n" 452"use this digitally signed contract in a court of law to prove the exact "
462"signed by the customer's coins and the\n" 453"terms of the contract and that he paid the respective amount. The "
463"merchant. If necessary, the customer can later\n" 454"customer does not learn the banking details of the merchant, and Taler "
464"use this digitally signed contract in a court\n" 455"does not require the merchant to learn the identity of the customer. "
465"of law to prove the exact terms of the contract\n" 456"Naturally, the customer can spend any fraction of his digital coins (the "
466"and that he paid the respective amount. The\n" 457"system takes care of customers getting change)."
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"
473msgstr "" 458msgstr ""
474 459
475#: developers.html.j2:210 460#: developers.html.j2:210
476msgid "" 461msgid ""
477"Merchants receiving digital\n" 462"Merchants receiving digital coins <b>deposit</b> the respective claims "
478"coins <b>deposit</b> the respective claims\n" 463"that resulted from the contract signing with the customer at the exchange"
479"that resulted from the contract signing with\n" 464" to redeem the coins. The deposit step does not reveal the details of the"
480"the customer at the exchange to redeem the\n" 465" contract between the customer and the merchant or the identity of the "
481"coins. The deposit step does not reveal the\n" 466"customer to the exchange in any way. However, the exchange does learn the"
482"details of the contract between the customer\n" 467" identity of the merchant via the provided bank routing information. The "
483"and the merchant or the identity of the\n" 468"merchant can, for example when compelled by the state for taxation, "
484"customer to the exchange in any way. However,\n" 469"provide information linking the individual deposit to the respective "
485"the exchange does learn the identity of the\n" 470"contract signed by the customer. Thus, the exchange's database allows the"
486"merchant via the provided bank routing\n" 471" state to enforce that merchants pay applicable taxes (and do not engage "
487"information. The merchant can, for example\n" 472"in illegal contracts)."
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"
495msgstr "" 473msgstr ""
496 474
497#: developers.html.j2:233 475#: developers.html.j2:233
498msgid "" 476msgid ""
499"Finally, the exchange transfers funds\n" 477"Finally, the exchange transfers funds corresponding to the digital coins "
500"corresponding to the digital coins redeemed by\n" 478"redeemed by the merchants to the merchant's <b>bank</b> account. The "
501"the merchants to the merchant's <b>bank</b>\n" 479"exchange may combine multiple small transactions into one larger bank "
502"account. The exchange may combine multiple\n" 480"transfer. The merchant can query the exchange about the relationship "
503"small transactions into one larger bank\n" 481"between the bank transfers and the individual claims that were deposited."
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"
508msgstr "" 482msgstr ""
509 483
510#: developers.html.j2:247 484#: developers.html.j2:247
511msgid "" 485msgid ""
512"Most importantly, the exchange keeps\n" 486"Most importantly, the exchange keeps cryptographic proofs that allow it "
513"cryptographic proofs that allow it to\n" 487"to demonstrate that it is operating correctly to third parties. The "
514"demonstrate that it is operating correctly to\n" 488"system requires an external <b>auditor</b>, such as a government-"
515"third parties. The system requires an\n" 489"appointed financial regulatory body, to frequently verify the exchange's "
516"external <b>auditor</b>, such as a\n" 490"databases and check that its bank balance matches the total value of the "
517"government-appointed financial regulatory body,\n" 491"remaining coins in circulation."
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"
522msgstr "" 492msgstr ""
523 493
524#: developers.html.j2:262 494#: developers.html.j2:262
525msgid "" 495msgid ""
526"Without the auditor, the exchange operators\n" 496"Without the auditor, the exchange operators could embezzle funds they are"
527"could embezzle funds they are holding in\n" 497" holding in reserve. Customers and merchants cannot cheat each other or "
528"reserve. Customers and merchants cannot cheat\n" 498"the exchange. If any party's computers are compromised, the financial "
529"each other or the exchange. If any party's\n" 499"damage is limited to the respective party and proportional to the funds "
530"computers are compromised, the financial damage\n" 500"they have in circulation during the period of the compromise."
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"
535msgstr "" 501msgstr ""
536 502
537#: faq.html.j2:5 503#: faq.html.j2:5
@@ -540,17 +506,17 @@ msgstr ""
540 506
541#: faq.html.j2:6 507#: faq.html.j2:6
542msgid "" 508msgid ""
543"<p>Taler does not use any Blockchain technology or Bitcoin directly.\n" 509"<p>Taler does not use any Blockchain technology or Bitcoin directly. "
544"Taler is not based on proof-of-work or any other distributed consensus\n" 510"Taler is not based on proof-of-work or any other distributed consensus "
545"mechanism. Instead Taler is based on blind signatures.</p>\n" 511"mechanism. Instead Taler is based on blind signatures.</p>"
546msgstr "" 512msgstr ""
547 513
548#: faq.html.j2:11 514#: faq.html.j2:11
549msgid "" 515msgid ""
550"<p>It would be possible, however, to withdraw coins denominated in\n" 516"<p>It would be possible, however, to withdraw coins denominated in "
551"Bitcoin into a Taler wallet (with an appropriate exchange), which\n" 517"Bitcoin into a Taler wallet (with an appropriate exchange), which would "
552"would give some benefits over plain Bitcoin, such as instant\n" 518"give some benefits over plain Bitcoin, such as instant confirmation "
553"confirmation times.</p>\n" 519"times.</p>"
554msgstr "" 520msgstr ""
555 521
556#: faq.html.j2:18 522#: faq.html.j2:18
@@ -559,9 +525,9 @@ msgstr ""
559 525
560#: faq.html.j2:19 526#: faq.html.j2:19
561msgid "" 527msgid ""
562"<p>Your wallet stores digital coins and thus ultimately your computer\n" 528"<p>Your wallet stores digital coins and thus ultimately your computer "
563"holds your balance. The exchange keeps funds matching all unspent\n" 529"holds your balance. The exchange keeps funds matching all unspent coins "
564"coins in an escrow bank account.</p>\n" 530"in an escrow bank account.</p>"
565msgstr "" 531msgstr ""
566 532
567#: faq.html.j2:25 533#: faq.html.j2:25
@@ -570,16 +536,16 @@ msgstr ""
570 536
571#: faq.html.j2:26 537#: faq.html.j2:26
572msgid "" 538msgid ""
573"<p>Since the digital coins of value in your wallet are anonymized, the\n" 539"<p>Since the digital coins of value in your wallet are anonymized, the "
574"exchange can not assist you in recovering a lost or stolen wallet.\n" 540"exchange can not assist you in recovering a lost or stolen wallet. Just "
575"Just like with a physical wallet for cash, you are responsible for\n" 541"like with a physical wallet for cash, you are responsible for keeping it "
576"keeping it safe.</p>\n" 542"safe.</p>"
577msgstr "" 543msgstr ""
578 544
579#: faq.html.j2:32 545#: faq.html.j2:32
580msgid "" 546msgid ""
581"<p>The risk of losing a wallet can be mitigated by making backups or\n" 547"<p>The risk of losing a wallet can be mitigated by making backups or "
582"keeping the balance reasonably low.</p>\n" 548"keeping the balance reasonably low.</p>"
583msgstr "" 549msgstr ""
584 550
585#: faq.html.j2:37 551#: faq.html.j2:37
@@ -588,9 +554,9 @@ msgstr ""
588 554
589#: faq.html.j2:38 555#: faq.html.j2:38
590msgid "" 556msgid ""
591"<p>In case of a compromise of one of your devices, an attacker can\n" 557"<p>In case of a compromise of one of your devices, an attacker can spend "
592"spend coins from your wallet. Checking your balance might reveal\n" 558"coins from your wallet. Checking your balance might reveal to you that "
593"to you that your device has been compromised.</p>\n" 559"your device has been compromised.</p>"
594msgstr "" 560msgstr ""
595 561
596#: faq.html.j2:44 562#: faq.html.j2:44
@@ -599,15 +565,15 @@ msgstr ""
599 565
600#: faq.html.j2:45 566#: faq.html.j2:45
601msgid "" 567msgid ""
602"<p>If your friend provides goods or services for you in exchange for a\n" 568"<p>If your friend provides goods or services for you in exchange for a "
603"payment, they can easily set up a Taler merchant and receive the\n" 569"payment, they can easily set up a Taler merchant and receive the payment "
604"payment in their bank account.</p>\n" 570"in their bank account.</p>"
605msgstr "" 571msgstr ""
606 572
607#: faq.html.j2:50 573#: faq.html.j2:50
608msgid "" 574msgid ""
609"<p>Future versions of the Taler wallet may allow exchanging coins\n" 575"<p>Future versions of the Taler wallet may allow exchanging coins among "
610"among friends directly as well.</p>\n" 576"friends directly as well.</p>"
611msgstr "" 577msgstr ""
612 578
613#: faq.html.j2:56 579#: faq.html.j2:56
@@ -616,12 +582,12 @@ msgstr ""
616 582
617#: faq.html.j2:57 583#: faq.html.j2:57
618msgid "" 584msgid ""
619"<p>Taler wallets can store digital coins corresponding to multiple\n" 585"<p>Taler wallets can store digital coins corresponding to multiple "
620"different currencies such as the Euro, US Dollars or Bitcoins.</p>\n" 586"different currencies such as the Euro, US Dollars or Bitcoins.</p>"
621msgstr "" 587msgstr ""
622 588
623#: faq.html.j2:61 589#: faq.html.j2:61
624msgid "<p>Taler currently does not offer conversion between currencies.</p>\n" 590msgid "<p>Taler currently does not offer conversion between currencies.</p>"
625msgstr "" 591msgstr ""
626 592
627#: faq.html.j2:65 593#: faq.html.j2:65
@@ -630,12 +596,11 @@ msgstr ""
630 596
631#: faq.html.j2:66 597#: faq.html.j2:66
632msgid "" 598msgid ""
633"<p>Your wallet stores digital coins that are <a\n" 599"<p>Your wallet stores digital coins that are <a "
634"href=\"https://en.wikipedia.org/wiki/Blind_signature\">blindly\n" 600"href=\"https://en.wikipedia.org/wiki/Blind_signature\">blindly signed</a>"
635"signed</a> by an exchange. The use of a blind signature protects your\n" 601" by an exchange. The use of a blind signature protects your privacy as it"
636"privacy as it prevents the exchange from knowing which coin it signed\n" 602" prevents the exchange from knowing which coin it signed for which "
637"for which customer.</p>\n" 603"customer.</p>"
638"\n"
639msgstr "" 604msgstr ""
640 605
641#: glossary.html.j2:6 606#: glossary.html.j2:6
@@ -645,7 +610,7 @@ msgstr ""
645#: glossary.html.j2:8 610#: glossary.html.j2:8
646msgid "" 611msgid ""
647"trusted third party that verifies that the `exchange` is operating " 612"trusted third party that verifies that the `exchange` is operating "
648"correctly\n" 613"correctly"
649msgstr "" 614msgstr ""
650 615
651#: glossary.html.j2:12 616#: glossary.html.j2:12
@@ -655,7 +620,7 @@ msgstr ""
655#: glossary.html.j2:14 620#: glossary.html.j2:14
656msgid "" 621msgid ""
657"traditional financial service provider who offers wire `transfers` " 622"traditional financial service provider who offers wire `transfers` "
658"between accounts\n" 623"between accounts"
659msgstr "" 624msgstr ""
660 625
661#: glossary.html.j2:18 626#: glossary.html.j2:18
@@ -665,7 +630,7 @@ msgstr ""
665#: glossary.html.j2:20 630#: glossary.html.j2:20
666msgid "" 631msgid ""
667"coins are individual token representing a certain amount of value, also " 632"coins are individual token representing a certain amount of value, also "
668"known as the `denomination` of the coin\n" 633"known as the `denomination` of the coin"
669msgstr "" 634msgstr ""
670 635
671#: glossary.html.j2:24 636#: glossary.html.j2:24
@@ -673,7 +638,7 @@ msgid "contract"
673msgstr "" 638msgstr ""
674 639
675#: glossary.html.j2:26 640#: glossary.html.j2:26
676msgid "the proposal signed by the wallet.\n" 641msgid "the proposal signed by the wallet."
677msgstr "" 642msgstr ""
678 643
679#: glossary.html.j2:30 644#: glossary.html.j2:30
@@ -683,7 +648,7 @@ msgstr ""
683#: glossary.html.j2:32 648#: glossary.html.j2:32
684msgid "" 649msgid ""
685"unit of currency, specifies both the currency and the face value of a " 650"unit of currency, specifies both the currency and the face value of a "
686"`coin`\n" 651"`coin`"
687msgstr "" 652msgstr ""
688 653
689#: glossary.html.j2:36 654#: glossary.html.j2:36
@@ -693,7 +658,7 @@ msgstr ""
693#: glossary.html.j2:38 658#: glossary.html.j2:38
694msgid "" 659msgid ""
695"RSA key used by the exchange to certify that a given `coin` is valid and " 660"RSA key used by the exchange to certify that a given `coin` is valid and "
696"of a particular `denomination`\n" 661"of a particular `denomination`"
697msgstr "" 662msgstr ""
698 663
699#: glossary.html.j2:42 664#: glossary.html.j2:42
@@ -704,7 +669,7 @@ msgstr ""
704msgid "" 669msgid ""
705"operation by which a merchant passes coins to an exchange, expecting the " 670"operation by which a merchant passes coins to an exchange, expecting the "
706"exchange to credit his `bank` account in the future using a wire " 671"exchange to credit his `bank` account in the future using a wire "
707"`transfer`\n" 672"`transfer`"
708msgstr "" 673msgstr ""
709 674
710#: glossary.html.j2:48 675#: glossary.html.j2:48
@@ -716,7 +681,7 @@ msgid ""
716"a `coin` is dirty if its public key may be known to an entity other than " 681"a `coin` is dirty if its public key may be known to an entity other than "
717"the customer, thereby creating the danger of some entity being able to " 682"the customer, thereby creating the danger of some entity being able to "
718"link multiple transactions of coin's owner if the coin is not refreshed " 683"link multiple transactions of coin's owner if the coin is not refreshed "
719"first\n" 684"first"
720msgstr "" 685msgstr ""
721 686
722#: glossary.html.j2:54 687#: glossary.html.j2:54
@@ -725,8 +690,8 @@ msgstr ""
725 690
726#: glossary.html.j2:56 691#: glossary.html.j2:56
727msgid "" 692msgid ""
728"Taler's payment service provider. Issues eletronic `coins` during " 693"Taler's payment service provider. Issues eletronic `coins` during "
729"`withdrawal` and redeems them when they are `deposited` by merchants.\n" 694"`withdrawal` and redeems them when they are `deposited` by merchants."
730msgstr "" 695msgstr ""
731 696
732#: glossary.html.j2:60 697#: glossary.html.j2:60
@@ -734,7 +699,7 @@ msgid "extension"
734msgstr "" 699msgstr ""
735 700
736#: glossary.html.j2:62 701#: glossary.html.j2:62
737msgid "implementation of a `wallet` for browsers\n" 702msgid "implementation of a `wallet` for browsers"
738msgstr "" 703msgstr ""
739 704
740#: glossary.html.j2:66 705#: glossary.html.j2:66
@@ -742,7 +707,7 @@ msgid "fresh coin"
742msgstr "" 707msgstr ""
743 708
744#: glossary.html.j2:68 709#: glossary.html.j2:68
745msgid "a `coin` is fresh if its public key is only known to the customer\n" 710msgid "a `coin` is fresh if its public key is only known to the customer"
746msgstr "" 711msgstr ""
747 712
748#: glossary.html.j2:72 713#: glossary.html.j2:72
@@ -752,7 +717,7 @@ msgstr ""
752#: glossary.html.j2:74 717#: glossary.html.j2:74
753msgid "" 718msgid ""
754"offline key used by the exchange to certify denomination keys and message" 719"offline key used by the exchange to certify denomination keys and message"
755" signing keys\n" 720" signing keys"
756msgstr "" 721msgstr ""
757 722
758#: glossary.html.j2:78 723#: glossary.html.j2:78
@@ -760,7 +725,7 @@ msgid "message signing key"
760msgstr "" 725msgstr ""
761 726
762#: glossary.html.j2:80 727#: glossary.html.j2:80
763msgid "key used by the exchange to sign online messages, other than coins\n" 728msgid "key used by the exchange to sign online messages, other than coins"
764msgstr "" 729msgstr ""
765 730
766#: glossary.html.j2:84 731#: glossary.html.j2:84
@@ -770,15 +735,11 @@ msgstr ""
770#: glossary.html.j2:86 735#: glossary.html.j2:86
771msgid "" 736msgid ""
772"specification of the details of a transaction, specifies the payment " 737"specification of the details of a transaction, specifies the payment "
773"obligations\n" 738"obligations for the customer (i.e. the amount), the deliverables of the "
774"for the customer (i.e. the amount), the deliverables of the merchant and " 739"merchant and other related information, such as deadlines or locations; "
775"other\n" 740"However, it lacks some information that the backend is supposed to "
776"related information, such as deadlines or locations; However, it lacks " 741"provide. In other words, after the backend adds the missing information "
777"some\n" 742"to the offer and signs it, it becomes a proposal."
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"
782msgstr "" 743msgstr ""
783 744
784#: glossary.html.j2:95 745#: glossary.html.j2:95
@@ -786,7 +747,7 @@ msgid "owner"
786msgstr "" 747msgstr ""
787 748
788#: glossary.html.j2:97 749#: glossary.html.j2:97
789msgid "a `coin` is owned by the entity that knows the private key of the coin\n" 750msgid "a `coin` is owned by the entity that knows the private key of the coin"
790msgstr "" 751msgstr ""
791 752
792#: glossary.html.j2:101 753#: glossary.html.j2:101
@@ -796,7 +757,7 @@ msgstr ""
796#: glossary.html.j2:103 757#: glossary.html.j2:103
797msgid "" 758msgid ""
798"message that cryptographically demonstrates that a particular claim is " 759"message that cryptographically demonstrates that a particular claim is "
799"correct\n" 760"correct"
800msgstr "" 761msgstr ""
801 762
802#: glossary.html.j2:107 763#: glossary.html.j2:107
@@ -804,7 +765,7 @@ msgid "proposal"
804msgstr "" 765msgstr ""
805 766
806#: glossary.html.j2:109 767#: glossary.html.j2:109
807msgid "a sketch that has been completed and signed by the merchant backend.\n" 768msgid "a sketch that has been completed and signed by the merchant backend."
808msgstr "" 769msgstr ""
809 770
810#: glossary.html.j2:113 771#: glossary.html.j2:113
@@ -815,7 +776,7 @@ msgstr ""
815msgid "" 776msgid ""
816"funds set aside for future use; either the balance of a customer at the " 777"funds set aside for future use; either the balance of a customer at the "
817"exchange ready for `withdrawal`, or the funds kept in the exchange's bank" 778"exchange ready for `withdrawal`, or the funds kept in the exchange's bank"
818" account to cover obligations from coins in circulation\n" 779" account to cover obligations from coins in circulation"
819msgstr "" 780msgstr ""
820 781
821#: glossary.html.j2:119 782#: glossary.html.j2:119
@@ -825,7 +786,7 @@ msgstr ""
825#: glossary.html.j2:121 786#: glossary.html.j2:121
826msgid "" 787msgid ""
827"operation by which a `dirty` `coin` is converted into one or more `fresh`" 788"operation by which a `dirty` `coin` is converted into one or more `fresh`"
828" coins\n" 789" coins"
829msgstr "" 790msgstr ""
830 791
831#: glossary.html.j2:125 792#: glossary.html.j2:125
@@ -836,7 +797,7 @@ msgstr ""
836msgid "" 797msgid ""
837"operation by which a merchant steps back from the right to funds that he " 798"operation by which a merchant steps back from the right to funds that he "
838"obtained from a `deposit` operation, giving the right to the funds back " 799"obtained from a `deposit` operation, giving the right to the funds back "
839"to the customer\n" 800"to the customer"
840msgstr "" 801msgstr ""
841 802
842#: glossary.html.j2:131 803#: glossary.html.j2:131
@@ -847,7 +808,7 @@ msgstr ""
847msgid "" 808msgid ""
848"users can share ownership of a `coin` by sharing access to the coin's " 809"users can share ownership of a `coin` by sharing access to the coin's "
849"private key, thereby allowing all co-owners to spend the coin at any " 810"private key, thereby allowing all co-owners to spend the coin at any "
850"time.\n" 811"time."
851msgstr "" 812msgstr ""
852 813
853#: glossary.html.j2:137 814#: glossary.html.j2:137
@@ -855,7 +816,7 @@ msgid "signing key"
855msgstr "" 816msgstr ""
856 817
857#: glossary.html.j2:139 818#: glossary.html.j2:139
858msgid "see message signing key.\n" 819msgid "see message signing key."
859msgstr "" 820msgstr ""
860 821
861#: glossary.html.j2:143 822#: glossary.html.j2:143
@@ -865,7 +826,7 @@ msgstr ""
865#: glossary.html.j2:145 826#: glossary.html.j2:145
866msgid "" 827msgid ""
867"operation by which a customer gives a merchant the right to `deposit` " 828"operation by which a customer gives a merchant the right to `deposit` "
868"coins in return for merchandise\n" 829"coins in return for merchandise"
869msgstr "" 830msgstr ""
870 831
871#: glossary.html.j2:149 832#: glossary.html.j2:149
@@ -873,7 +834,7 @@ msgid "transfer"
873msgstr "" 834msgstr ""
874 835
875#: glossary.html.j2:151 836#: glossary.html.j2:151
876msgid "method of sending funds between `bank` accounts\n" 837msgid "method of sending funds between `bank` accounts"
877msgstr "" 838msgstr ""
878 839
879#: glossary.html.j2:155 840#: glossary.html.j2:155
@@ -883,7 +844,7 @@ msgstr ""
883#: glossary.html.j2:157 844#: glossary.html.j2:157
884msgid "" 845msgid ""
885"method by which ownership is exclusively transferred from one entity to " 846"method by which ownership is exclusively transferred from one entity to "
886"another\n" 847"another"
887msgstr "" 848msgstr ""
888 849
889#: glossary.html.j2:161 850#: glossary.html.j2:161
@@ -891,7 +852,7 @@ msgid "transaction id"
891msgstr "" 852msgstr ""
892 853
893#: glossary.html.j2:163 854#: glossary.html.j2:163
894msgid "unique number by which a merchant identifies a `transaction`\n" 855msgid "unique number by which a merchant identifies a `transaction`"
895msgstr "" 856msgstr ""
896 857
897#: glossary.html.j2:167 858#: glossary.html.j2:167
@@ -901,7 +862,7 @@ msgstr ""
901#: glossary.html.j2:169 862#: glossary.html.j2:169
902msgid "" 863msgid ""
903"software running on a customer's computer; withdraws, stores and spends " 864"software running on a customer's computer; withdraws, stores and spends "
904"coins\n" 865"coins"
905msgstr "" 866msgstr ""
906 867
907#: glossary.html.j2:173 868#: glossary.html.j2:173
@@ -909,7 +870,7 @@ msgid "wire transfer"
909msgstr "" 870msgstr ""
910 871
911#: glossary.html.j2:175 872#: glossary.html.j2:175
912msgid "see `transfer`\n" 873msgid "see `transfer`"
913msgstr "" 874msgstr ""
914 875
915#: glossary.html.j2:179 876#: glossary.html.j2:179
@@ -919,7 +880,7 @@ msgstr ""
919#: glossary.html.j2:181 880#: glossary.html.j2:181
920msgid "" 881msgid ""
921"subject of a wire `transfer`; usually a random string to uniquely " 882"subject of a wire `transfer`; usually a random string to uniquely "
922"identify the `transfer`\n" 883"identify the `transfer`"
923msgstr "" 884msgstr ""
924 885
925#: glossary.html.j2:185 886#: glossary.html.j2:185
@@ -929,7 +890,7 @@ msgstr ""
929#: glossary.html.j2:187 890#: glossary.html.j2:187
930msgid "" 891msgid ""
931"operation by which a `wallet` can convert funds from a reserve to fresh " 892"operation by which a `wallet` can convert funds from a reserve to fresh "
932"coins\n" 893"coins"
933msgstr "" 894msgstr ""
934 895
935#: governments.html.j2:6 896#: governments.html.j2:6
@@ -938,13 +899,12 @@ msgstr ""
938 899
939#: governments.html.j2:8 900#: governments.html.j2:8
940msgid "" 901msgid ""
941"Taler provides accountability to ensure business operate\n" 902"Taler provides accountability to ensure business operate legally, while "
942"legally, while also respecting civil liberties of\n" 903"also respecting civil liberties of citizens. Taler is a payment system "
943"citizens. Taler is a payment system based on\n" 904"based on open standards and free software. Taler needs governments as "
944"open standards and free software. Taler needs\n" 905"they set a financial framework and act as trusted regulators. Taler "
945"governments as they set a financial framework and act as\n" 906"contributes to digital sovereignty in the critical financial "
946"trusted regulators. Taler contributes to digital\n" 907"infrastructure."
947"sovereignty in the critical financial infrastructure.\n"
948msgstr "" 908msgstr ""
949 909
950#: governments.html.j2:25 index.html.j2:71 910#: governments.html.j2:25 index.html.j2:71
@@ -953,51 +913,44 @@ msgstr ""
953 913
954#: governments.html.j2:28 914#: governments.html.j2:28
955msgid "" 915msgid ""
956"Taler was built with the goal of fighting corruption and\n" 916"Taler was built with the goal of fighting corruption and supporting "
957"supporting taxation. With Taler, the receiver of any\n" 917"taxation. With Taler, the receiver of any form of payment is easily "
958"form of payment is easily identified by the government,\n" 918"identified by the government, and the merchant can be compelled to "
959"and the merchant can be compelled to provide the contract\n" 919"provide the contract that was accepted by the customer. Governments can "
960"that was accepted by the customer. Governments can use\n" 920"use this data to tax businesses and individuals based on their income, "
961"this data to tax businesses and individuals based on\n" 921"making tax evasion and black markets less viable."
962"their income, making tax evasion and black markets less\n"
963"viable.\n"
964msgstr "" 922msgstr ""
965 923
966#: governments.html.j2:41 924#: governments.html.j2:41
967msgid "" 925msgid ""
968"Thus, despite offering anonymity for citizens spending\n" 926"Thus, despite offering anonymity for citizens spending digital cash to "
969"digital cash to buy goods and services, Taler also\n" 927"buy goods and services, Taler also ensures that the state can observe "
970"ensures that the state can observe incoming funds. This\n" 928"incoming funds. This can be used to ensure businesses engage only in "
971"can be used to ensure businesses engage only in legal\n" 929"legal activities, and do not evade income tax, sales tax or value-added "
972"activities, and do not evade income tax, sales tax or\n" 930"tax. However, this observational capability does not extend to the "
973"value-added tax. However, this observational capability\n" 931"immediate personal domain. In particular, monitoring does not cover "
974"does not extend to the immediate personal domain. In\n" 932"shared access to funds with trusted friends and family, or synchronizing "
975"particular, monitoring does not cover shared access to\n" 933"wallets across multiple devices."
976"funds with trusted friends and family, or synchronizing\n"
977"wallets across multiple devices.\n"
978msgstr "" 934msgstr ""
979 935
980#: governments.html.j2:61 936#: governments.html.j2:61
981msgid "" 937msgid ""
982"Taler's payments are cryptographically secured. Thus,\n" 938"Taler's payments are cryptographically secured. Thus, customers, "
983"customers, merchants and the Taler payment service provider\n" 939"merchants and the Taler payment service provider (the exchange) can "
984"(the exchange) can mathematically\n" 940"mathematically demonstrate their lawful behavior in court in case of "
985"demonstrate their lawful behavior in court in case of\n" 941"disputes. Financial damages are strictly limited, improving economic "
986"disputes. Financial damages are strictly limited,\n" 942"security for individuals, merchants, the exchange and the state."
987"improving economic security for individuals, merchants,\n"
988"the exchange and the state.\n"
989msgstr "" 943msgstr ""
990 944
991#: governments.html.j2:73 945#: governments.html.j2:73
992msgid "" 946msgid ""
993"As a payment service provider, the Taler exchange is\n" 947"As a payment service provider, the Taler exchange is subject to financial"
994"subject to financial regulation. Financial regulation and\n" 948" regulation. Financial regulation and regular audits are critical to "
995"regular audits are critical to establish trust. In\n" 949"establish trust. In particular, the Taler design mandates the existence "
996"particular, the Taler design mandates the existence of an\n" 950"of an independent auditor who checks cryptographic proofs that accumulate"
997"independent auditor who checks cryptographic proofs that\n" 951" at the exchange to ensure that the escrow account is managed honestly. "
998"accumulate at the exchange to ensure that the escrow\n" 952"This ensures that the exchange does not threaten the economy due to "
999"account is managed honestly. This ensures that the\n" 953"fraud."
1000"exchange does not threaten the economy due to fraud.\n"
1001msgstr "" 954msgstr ""
1002 955
1003#: governments.html.j2:88 index.html.j2:97 956#: governments.html.j2:88 index.html.j2:97
@@ -1006,10 +959,9 @@ msgstr ""
1006 959
1007#: governments.html.j2:91 960#: governments.html.j2:91
1008msgid "" 961msgid ""
1009"Taler is free software implementing an open protocol\n" 962"Taler is free software implementing an open protocol standard. Thus, "
1010"standard. Thus, Taler will enable competition and avoid\n" 963"Taler will enable competition and avoid the monopolization of payment "
1011"the monopolization of payment systems that threatens\n" 964"systems that threatens global political and financial stability today."
1012"global political and financial stability today.\n"
1013msgstr "" 965msgstr ""
1014 966
1015#: governments.html.j2:101 967#: governments.html.j2:101
@@ -1018,11 +970,9 @@ msgstr ""
1018 970
1019#: governments.html.j2:104 971#: governments.html.j2:104
1020msgid "" 972msgid ""
1021"Taler has an efficient design. Unlike\n" 973"Taler has an efficient design. Unlike Blockchain-based payment systems, "
1022"Blockchain-based payment systems, such as Bitcoin,\n" 974"such as Bitcoin, Taler will not threaten the availability of national "
1023"Taler will not threaten the availability of\n" 975"electric grids or (significantly) contribute to environmental pollution."
1024"national electric grids or (significantly)\n"
1025"contribute to environmental pollution.\n"
1026msgstr "" 976msgstr ""
1027 977
1028#: governments.html.j2:120 978#: governments.html.j2:120
@@ -1075,41 +1025,36 @@ msgstr ""
1075 1025
1076#: governments.html.j2:140 1026#: governments.html.j2:140
1077msgid "" 1027msgid ""
1078"Taler assumes governments can observe traditional wire transfers\n" 1028"Taler assumes governments can observe traditional wire transfers entering"
1079"entering and leaving the Taler payment system. Starting with the\n" 1029" and leaving the Taler payment system. Starting with the wire transfers, "
1080"wire transfers, governments can obtain:\n" 1030"governments can obtain:"
1081msgstr "" 1031msgstr ""
1082 1032
1083#: governments.html.j2:148 1033#: governments.html.j2:148
1084msgid "" 1034msgid ""
1085"The total amount of digital currency withdrawn by a\n" 1035"The total amount of digital currency withdrawn by a customer. The "
1086"customer. The government can impose limits on how much\n" 1036"government can impose limits on how much digital cash a customer can "
1087"digital cash a customer can withdraw within a\n" 1037"withdraw within a given time frame."
1088"given time frame.\n"
1089msgstr "" 1038msgstr ""
1090 1039
1091#: governments.html.j2:157 1040#: governments.html.j2:157
1092msgid "" 1041msgid "The income received by any merchant via the Taler system."
1093"The income received by any merchant via the Taler\n"
1094"system.\n"
1095msgstr "" 1042msgstr ""
1096 1043
1097#: governments.html.j2:164 1044#: governments.html.j2:164
1098msgid "" 1045msgid ""
1099"The exact details of the underlying contract that was\n" 1046"The exact details of the underlying contract that was signed between "
1100"signed between customer and merchant. However, this\n" 1047"customer and merchant. However, this information would typically not "
1101"information would typically not include the identity\n" 1048"include the identity of the customer."
1102"of the customer.\n"
1103msgstr "" 1049msgstr ""
1104 1050
1105#: governments.html.j2:174 1051#: governments.html.j2:174
1106msgid "" 1052msgid ""
1107"The amounts of digital coins legitimately withdrawn\n" 1053"The amounts of digital coins legitimately withdrawn by customers from the"
1108"by customers from the exchange, the value of\n" 1054" exchange, the value of non-redeemed digital coins in customer's wallets,"
1109"non-redeemed digital coins in customer's wallets, the\n" 1055" the value and corresponding wire details of deposit operations performed"
1110"value and corresponding wire details of deposit\n" 1056" by merchants with the exchange, and the income of the exchange from "
1111"operations performed by merchants with the exchange,\n" 1057"transaction fees."
1112"and the income of the exchange from transaction fees.\n"
1113msgstr "" 1058msgstr ""
1114 1059
1115#: index.html.j2:10 1060#: index.html.j2:10
@@ -1118,12 +1063,12 @@ msgstr ""
1118 1063
1119#: index.html.j2:13 1064#: index.html.j2:13
1120msgid "" 1065msgid ""
1121"GNU Taler is an electronic payment system under development at\n" 1066"GNU Taler is an electronic payment system under development at <a "
1122"<a href=\"http://www.inria.fr/\">Inria</a>. We expect to make it\n" 1067"href=\"http://www.inria.fr/\">Inria</a>. We expect to make it operational"
1123"operational in 2017. You can learn about Taler on this website,\n" 1068" in 2017. You can learn about Taler on this website, try the <a "
1124"try the <a href=\"https://demo.taler.net\">demo</a> and look at\n" 1069"href=\"https://demo.taler.net\">demo</a> and look at our <a "
1125"our <a href=\"https://docs.taler.net\">developer</a> and <a\n" 1070"href=\"https://docs.taler.net\">developer</a> and <a "
1126"href=\"https://api.taler.net\">API</a> documentation.\n" 1071"href=\"https://api.taler.net\">API</a> documentation."
1127msgstr "" 1072msgstr ""
1128 1073
1129#: index.html.j2:29 1074#: index.html.j2:29
@@ -1132,53 +1077,48 @@ msgstr ""
1132 1077
1133#: index.html.j2:32 1078#: index.html.j2:32
1134msgid "" 1079msgid ""
1135"Taler is easy to integrate with existing Web\n" 1080"Taler is easy to integrate with existing Web applications. Payments are "
1136"applications. Payments are cryptographically\n" 1081"cryptographically secured and are confirmed within milliseconds with "
1137"secured and are confirmed within milliseconds with\n" 1082"extremely low transaction costs."
1138"extremely low transaction costs.\n"
1139msgstr "" 1083msgstr ""
1140 1084
1141#: index.html.j2:45 1085#: index.html.j2:45
1142msgid "" 1086msgid ""
1143"Taler does not introduce a new currency. Taler\n" 1087"Taler does not introduce a new currency. Taler uses a digital wallet "
1144"uses a digital wallet storing coins and payment service\n" 1088"storing coins and payment service providers with escrow accounts in "
1145"providers with escrow accounts in existing currencies.\n" 1089"existing currencies. Thus, Taler's cryptographic coins correspond to "
1146"Thus, Taler's cryptographic coins correspond to existing\n" 1090"existing currencies, such as US Dollars, Euros or even Bitcoins."
1147"currencies, such as US Dollars, Euros or even Bitcoins.\n"
1148msgstr "" 1091msgstr ""
1149 1092
1150#: index.html.j2:59 1093#: index.html.j2:59
1151msgid "" 1094msgid ""
1152"By design Taler does not suffer from many classes\n" 1095"By design Taler does not suffer from many classes of security problems "
1153"of security problems such as phishing or counterfeit.\n" 1096"such as phishing or counterfeit. Thanks to its security features, Taler "
1154"Thanks to its security features, Taler never rejects a legitimate\n" 1097"never rejects a legitimate customer due to a fraud-detection false "
1155"customer due to a fraud-detection false positive.\n" 1098"positive."
1156msgstr "" 1099msgstr ""
1157 1100
1158#: index.html.j2:74 1101#: index.html.j2:74
1159msgid "" 1102msgid ""
1160"When using Taler, merchant's revenue is transparent for tax\n" 1103"When using Taler, merchant's revenue is transparent for tax collection "
1161"collection authorities. Unlike cash and most digital currencies,\n" 1104"authorities. Unlike cash and most digital currencies, Taler helps prevent"
1162"Taler helps prevent black markets. Taler is not suitable for\n" 1105" black markets. Taler is not suitable for illegal activities."
1163"illegal activities.\n"
1164msgstr "" 1106msgstr ""
1165 1107
1166#: index.html.j2:86 1108#: index.html.j2:86
1167msgid "" 1109msgid ""
1168"When you pay with Taler, your identity does not\n" 1110"When you pay with Taler, your identity does not have to be revealed. Just"
1169"have to be revealed. Just like\n" 1111" like payments in cash, nobody else can track how you spent your "
1170"payments in cash, nobody else can track how you\n" 1112"electronic money. However, you obtain a legally valid proof of payment."
1171"spent your electronic money. However, you obtain a\n"
1172"legally valid proof of payment.\n"
1173msgstr "" 1113msgstr ""
1174 1114
1175#: index.html.j2:100 1115#: index.html.j2:100
1176msgid "" 1116msgid ""
1177"Taler provides protocols and reference implementations that in\n" 1117"Taler provides protocols and reference implementations that in principle "
1178"principle enables anybody to run their own payment infrastructure,\n" 1118"enables anybody to run their own payment infrastructure, be it "
1179"be it individuals, organizations or whole countries. Since the\n" 1119"individuals, organizations or whole countries. Since the reference "
1180"reference implementation is a <a href=\"http://www.gnu.org/\">GNU</a>\n" 1120"implementation is a <a href=\"http://www.gnu.org/\">GNU</a> package, it "
1181"package, it will always remain free software.\n" 1121"will always remain free software."
1182msgstr "" 1122msgstr ""
1183 1123
1184#: index.html.j2:117 1124#: index.html.j2:117
@@ -1187,12 +1127,12 @@ msgstr ""
1187 1127
1188#: index.html.j2:118 1128#: index.html.j2:118
1189msgid "" 1129msgid ""
1190"<p>To pay with Taler, customers install an electronic wallet\n" 1130"<p>To pay with Taler, customers install an electronic wallet on their "
1191"on their device. Before the first payment, the wallet's balance must\n" 1131"device. Before the first payment, the wallet's balance must be charged in"
1192"be charged in the desired currency by some other means of payment.</p>\n" 1132" the desired currency by some other means of payment.</p> <p>Once the "
1193"<p>Once the wallet is charged, payments on websites take only one click,\n" 1133"wallet is charged, payments on websites take only one click, are never "
1194"are never falsely rejected by fraud detection and do not pose any risk\n" 1134"falsely rejected by fraud detection and do not pose any risk of phishing "
1195"of phishing or identity theft.</p>\n" 1135"or identity theft.</p>"
1196msgstr "" 1136msgstr ""
1197 1137
1198#: index.html.j2:128 1138#: index.html.j2:128
@@ -1201,11 +1141,11 @@ msgstr ""
1201 1141
1202#: index.html.j2:129 1142#: index.html.j2:129
1203msgid "" 1143msgid ""
1204"<p>To receive Taler payments, a merchant needs a bank account\n" 1144"<p>To receive Taler payments, a merchant needs a bank account in the "
1205"in the desired currency. We provide supporting software\n" 1145"desired currency. We provide supporting software in various programming "
1206"in various programming languages to make the integration painless.\n" 1146"languages to make the integration painless. The merchant's backend for "
1207"The merchant's backend for Taler transaction processing can run\n" 1147"Taler transaction processing can run on the merchant's premises or be "
1208"on the merchant's premises or be hosted by a third party.</p>\n" 1148"hosted by a third party.</p>"
1209msgstr "" 1149msgstr ""
1210 1150
1211#: index.html.j2:145 1151#: index.html.j2:145
@@ -1222,10 +1162,8 @@ msgstr ""
1222 1162
1223#: investors.html.j2:9 1163#: investors.html.j2:9
1224msgid "" 1164msgid ""
1225"We have created a company, Taler Systems SA in\n" 1165"We have created a company, Taler Systems SA in Luxembourg.<br> Please "
1226"Luxembourg.<br>\n" 1166"contact <tt>invest@taler.net</tt> if you want to invest in Taler."
1227"Please contact <tt>invest@taler.net</tt>\n"
1228"if you want to invest in Taler.\n"
1229msgstr "" 1167msgstr ""
1230 1168
1231#: investors.html.j2:24 1169#: investors.html.j2:24
@@ -1235,20 +1173,17 @@ msgstr ""
1235#: investors.html.j2:27 1173#: investors.html.j2:27
1236msgid "" 1174msgid ""
1237"Our <a href=\"about.html\">team</a> combines world-class business " 1175"Our <a href=\"about.html\">team</a> combines world-class business "
1238"leaders,\n" 1176"leaders, cryptographers, software engineers, civil-rights activists and "
1239"cryptographers, software engineers, civil-rights\n" 1177"academics. We are unified by a vision of how payments should work and the"
1240"activists and academics. We are unified by a vision\n" 1178" goal of imposing this vision upon the world."
1241"of how payments should work and the goal of\n"
1242"imposing this vision upon the world.\n"
1243msgstr "" 1179msgstr ""
1244 1180
1245#: investors.html.j2:37 1181#: investors.html.j2:37
1246msgid "" 1182msgid ""
1247"We are currently supported by <a href=\"http://www.inria.fr/\">Inria</a>," 1183"We are currently supported by <a href=\"http://www.inria.fr/\">Inria</a>,"
1248" the French\n" 1184" the French national institute for research in informatics and "
1249"national institute for research in informatics and\n"
1250"automation, and the <a href=\"https://renewablefreedom.org/\">Renewable " 1185"automation, and the <a href=\"https://renewablefreedom.org/\">Renewable "
1251"Freedom Foundation</a>.\n" 1186"Freedom Foundation</a>."
1252msgstr "" 1187msgstr ""
1253 1188
1254#: investors.html.j2:45 1189#: investors.html.j2:45
@@ -1258,16 +1193,13 @@ msgstr ""
1258#: investors.html.j2:48 1193#: investors.html.j2:48
1259msgid "" 1194msgid ""
1260"All transactions in Taler are secured using <a " 1195"All transactions in Taler are secured using <a "
1261"href=\"bibliography.html\">modern\n" 1196"href=\"bibliography.html\">modern cryptography</a> and trust in all "
1262"cryptography</a> and trust in all parties is\n" 1197"parties is minimized. Financial damage is bounded (for customers, "
1263"minimized. Financial damage is bounded (for\n" 1198"merchants and the exchange) even in the case that systems are compromised"
1264"customers, merchants and the exchange) even in the\n" 1199" and private keys are stolen. Databases can be audited for consistency, "
1265"case that systems are compromised and private keys\n" 1200"resulting in either the detection of compromised systems or the "
1266"are stolen. Databases can be audited for\n" 1201"demonstration that participants were honest. Actual transaction costs are"
1267"consistency, resulting in either the detection of\n" 1202" fractions of a cent."
1268"compromised systems or the demonstration that\n"
1269"participants were honest. Actual transaction costs\n"
1270"are fractions of a cent.\n"
1271msgstr "" 1203msgstr ""
1272 1204
1273#: investors.html.j2:63 1205#: investors.html.j2:63
@@ -1276,15 +1208,13 @@ msgstr ""
1276 1208
1277#: investors.html.j2:66 1209#: investors.html.j2:66
1278msgid "" 1210msgid ""
1279"The scalable business model for Taler is the operation\n" 1211"The scalable business model for Taler is the operation of the payment "
1280"of the payment service provider, which converts money from\n" 1212"service provider, which converts money from traditional payment systems "
1281"traditional payment systems (MasterCard, SEPA, UPI,\n" 1213"(MasterCard, SEPA, UPI, Visa, Bitcoin, ACH, SWIFT, etc.) to anonymous "
1282"Visa, Bitcoin, ACH, SWIFT, etc.) to anonymous\n" 1214"electronic coins in the same currency. The customer can then redeem the "
1283"electronic coins in the same currency. The customer\n" 1215"electronic coins at a merchant, who can exchange them for money "
1284"can then redeem the electronic coins at a merchant,\n" 1216"represented using traditional payment systems at the exchange. The "
1285"who can exchange them for money represented using\n" 1217"exchange charges fees to facilitate the transactions."
1286"traditional payment systems at the exchange. The\n"
1287"exchange charges fees to facilitate the transactions.\n"
1288msgstr "" 1218msgstr ""
1289 1219
1290#: investors.html.j2:85 1220#: investors.html.j2:85
@@ -1297,10 +1227,10 @@ msgstr ""
1297 1227
1298#: investors.html.j2:110 1228#: investors.html.j2:110
1299msgid "" 1229msgid ""
1300"The payment service operator runs the <em>Taler exchange</em>.\n" 1230"The payment service operator runs the <em>Taler exchange</em>. The "
1301"The exchange charges <b>transaction fees</b> to customers or merchants.\n" 1231"exchange charges <b>transaction fees</b> to customers or merchants. Its "
1302"Its operational expenses are from wire transfers with the banking\n" 1232"operational expenses are from wire transfers with the banking system and "
1303"system and the operation of the computing infrastructure.\n" 1233"the operation of the computing infrastructure."
1304msgstr "" 1234msgstr ""
1305 1235
1306#: investors.html.j2:120 1236#: investors.html.j2:120
@@ -1335,11 +1265,10 @@ msgstr ""
1335 1265
1336#: merchants.html.j2:8 1266#: merchants.html.j2:8
1337msgid "" 1267msgid ""
1338"Taler is a cost-effective electronic payment system\n" 1268"Taler is a cost-effective electronic payment system which provides you "
1339"which provides you with cryptographic proof that\n" 1269"with cryptographic proof that the payment worked correctly within "
1340"the payment worked correctly within milliseconds.\n" 1270"milliseconds. Your Web customers pay with previously unknown levels of "
1341"Your Web customers pay with previously unknown\n" 1271"convenience without risk of fraud."
1342"levels of convenience without risk of fraud.\n"
1343msgstr "" 1272msgstr ""
1344 1273
1345#: merchants.html.j2:22 1274#: merchants.html.j2:22
@@ -1348,39 +1277,32 @@ msgstr ""
1348 1277
1349#: merchants.html.j2:25 1278#: merchants.html.j2:25
1350msgid "" 1279msgid ""
1351"Processing transactions with Taler is fast,\n" 1280"Processing transactions with Taler is fast, allowing you to confirm the "
1352"allowing you to confirm the transaction with your\n" 1281"transaction with your customer virtually immediately. Your customers will"
1353"customer virtually immediately. Your customers\n" 1282" appreciate that they do not have to type in credit card information and "
1354"will appreciate that they do not have to type in\n" 1283"play the &quot;verified by&quot; game. By making payments significantly "
1355"credit card information and play the &quot;verified\n" 1284"more convenient for your customers, you may be able to use Taler for "
1356"by&quot; game. By making payments significantly\n" 1285"small transactions that would not work with credit card payments due to "
1357"more convenient for your customers, you may be able\n" 1286"the mental overhead for customers."
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"
1361msgstr "" 1287msgstr ""
1362 1288
1363#: merchants.html.j2:44 1289#: merchants.html.j2:44
1364msgid "" 1290msgid ""
1365"You will have cryptographic proof of payment from the\n" 1291"You will have cryptographic proof of payment from the Taler payment "
1366"Taler payment service provider. With Taler you never\n" 1292"service provider. With Taler you never handle sensitive customer account "
1367"handle sensitive customer account information and thus\n" 1293"information and thus do not have to undergo any particular security "
1368"do not have to undergo any particular security audits\n" 1294"audits (such as PCI DSS). Your systems will have customer contracts with "
1369"(such as PCI DSS). Your systems will have customer\n" 1295"qualified signatures for all transactions which you can use in court in "
1370"contracts with qualified signatures for all\n" 1296"case of disputes."
1371"transactions which you can use in court in case of\n"
1372"disputes.\n"
1373msgstr "" 1297msgstr ""
1374 1298
1375#: merchants.html.j2:61 1299#: merchants.html.j2:61
1376msgid "" 1300msgid ""
1377"Taler is free software, and you can use the\n" 1301"Taler is free software, and you can use the liberally-licensed reference "
1378"liberally-licensed reference code as a starting\n" 1302"code as a starting point to integrate Taler into your services. To use "
1379"point to integrate Taler into your services. To use\n" 1303"Taler, you do not need to pay license fees, and the free software "
1380"Taler, you do not need to pay license fees, and the\n" 1304"development model will ensure that you can select from many competing "
1381"free software development model will ensure that\n" 1305"integrators for support."
1382"you can select from many competing integrators for\n"
1383"support.\n"
1384msgstr "" 1306msgstr ""
1385 1307
1386#: merchants.html.j2:76 1308#: merchants.html.j2:76
@@ -1389,11 +1311,10 @@ msgstr ""
1389 1311
1390#: merchants.html.j2:79 1312#: merchants.html.j2:79
1391msgid "" 1313msgid ""
1392"Taler is uses efficient cryptographic constructions with low\n" 1314"Taler is uses efficient cryptographic constructions with low bandwidth "
1393"bandwidth and storage requirements. Combined with Taler's strong\n" 1315"and storage requirements. Combined with Taler's strong security which "
1394"security which makes fraud impossible, Taler payment service\n" 1316"makes fraud impossible, Taler payment service providers can operate with "
1395"providers can operate with very low overhead and\n" 1317"very low overhead and thus offer low transaction fees."
1396"thus offer low transaction fees.\n"
1397msgstr "" 1318msgstr ""
1398 1319
1399#: merchants.html.j2:89 1320#: merchants.html.j2:89
@@ -1402,10 +1323,9 @@ msgstr ""
1402 1323
1403#: merchants.html.j2:92 1324#: merchants.html.j2:92
1404msgid "" 1325msgid ""
1405"Taler can be used for different currencies (such as\n" 1326"Taler can be used for different currencies (such as Euros, US Dollars or "
1406"Euros, US Dollars or Bitcoins) and any amount, limited\n" 1327"Bitcoins) and any amount, limited only by applicable regulatation and "
1407"only by applicable regulatation and what denominations\n" 1328"what denominations the payment service provider supports."
1408"the payment service provider supports.\n"
1409msgstr "" 1329msgstr ""
1410 1330
1411#: merchants.html.j2:101 1331#: merchants.html.j2:101
@@ -1414,11 +1334,10 @@ msgstr ""
1414 1334
1415#: merchants.html.j2:104 1335#: merchants.html.j2:104
1416msgid "" 1336msgid ""
1417"Taler prevents tax evasion and money laundering.\n" 1337"Taler prevents tax evasion and money laundering. Taler's protocols are "
1418"Taler's protocols are efficient and do not use wasteful\n" 1338"efficient and do not use wasteful proof-of-work calculations. Taler "
1419"proof-of-work calculations. Taler encourages\n" 1339"encourages transparency by providing an open standard and free software "
1420"transparency by providing an open standard and free\n" 1340"reference implementations."
1421"software reference implementations.\n"
1422msgstr "" 1341msgstr ""
1423 1342
1424#: merchants.html.j2:119 1343#: merchants.html.j2:119
@@ -1447,28 +1366,25 @@ msgstr ""
1447 1366
1448#: merchants.html.j2:147 1367#: merchants.html.j2:147
1449msgid "" 1368msgid ""
1450"The backend <b>signs</b> and <b>stores</b> the\n" 1369"The backend <b>signs</b> and <b>stores</b> the complete terms of offers "
1451"complete terms of offers made by the merchant to customers.\n" 1370"made by the merchant to customers. For this, the merchant's frontend "
1452"For this, the merchant's frontend needs to give the\n" 1371"needs to give the customer's order in a JSON format to the backend."
1453"customer's order in a JSON format to the backend.\n"
1454msgstr "" 1372msgstr ""
1455 1373
1456#: merchants.html.j2:156 1374#: merchants.html.j2:156
1457msgid "" 1375msgid ""
1458"The backend <b>validates</b> payments received from\n" 1376"The backend <b>validates</b> payments received from the wallet and "
1459"the wallet and <b>executes</b> them with the Taler\n" 1377"<b>executes</b> them with the Taler payment service provider (the "
1460"payment service provider (the exchange). For this,\n" 1378"exchange). For this, the merchant's frontend must pass the payment "
1461"the merchant's frontend must pass the payment\n" 1379"request through to the Taler backend and check the HTTP status code that "
1462"request through to the Taler backend and check the\n" 1380"is returned."
1463"HTTP status code that is returned.\n"
1464msgstr "" 1381msgstr ""
1465 1382
1466#: merchants.html.j2:167 1383#: merchants.html.j2:167
1467msgid "" 1384msgid ""
1468"The backend can <b>list</b> completed transactions\n" 1385"The backend can <b>list</b> completed transactions and <b>map</b> wire "
1469"and <b>map</b> wire transfers to sets of business\n" 1386"transfers to sets of business transactions, including the exact terms of "
1470"transactions, including the exact terms of each\n" 1387"each contract."
1471"contract.\n"
1472msgstr "" 1388msgstr ""
1473 1389
1474#: press.html.j2:4 1390#: press.html.j2:4
@@ -1690,3 +1606,1001 @@ msgstr ""
1690#~ msgid "Low Fees" 1606#~ msgid "Low Fees"
1691#~ msgstr "" 1607#~ msgstr ""
1692 1608
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-27 04:21:59 +0000