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