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