From 14af51dacedf00bbd460cdc1584cd9f81cb0d1f5 Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Mon, 6 Mar 2017 03:50:07 +0100 Subject: conversion/text --- about.html.j2 | 216 +++++++++++----------- common/base.j2 | 2 +- common/footer.j2.inc | 11 +- common/header.j2.inc | 1 - common/navigation.j2.inc | 107 +++++------ developers.html.j2 | 455 +++++++++++++++++++++++------------------------ governments.html.j2 | 299 +++++++++++++++---------------- index.html.j2 | 52 +++--- investors.html.j2 | 183 ++++++++++--------- justified-nav.css | 80 --------- merchants.html.j2 | 326 ++++++++++++++++----------------- styles.css | 10 ++ template.py | 7 +- 13 files changed, 807 insertions(+), 942 deletions(-) delete mode 100644 justified-nav.css diff --git a/about.html.j2 b/about.html.j2 index 3af6dd1b..1b596b1f 100644 --- a/about.html.j2 +++ b/about.html.j2 @@ -1,116 +1,100 @@ - - - - - {{ _("GNU Taler") }} - {{ _("About us") }} - - {% include "common/header.j2.inc" %} - - -
- {% include "common/navigation.j2.inc" %} - -
-

{{ _("About us") }}

-
- - -
-
-

Dr. Christian Grothoff

- Christian Grothoff -

{{ _("GNU maintainer. Network security & privacy researcher. Software architect.") }}

-
-
-

Leon Schumacher

- Leon Schumacher -

{{ _("Entrepreneur, Investor, Fortune 100 CIO, IT company director in different industries, ….") }}

-
-
-
-
-

Dr. Jeffrey Burdges

- Jeffrey Burdges -

{{ _("Applied cryptography. Contact to W3c & Tor.") }}

-
-
-

Dr. Cristina Onete

- Cristina Onete -

{{ _("Theoretical foundations.") }}

-
-
-

Dr. Richard M. Stallman

- Richard Stallman -

{{ _("Founder of the GNU project. Ethical guidance and licensing.") }}

-
-
-
-
-

Sree Harsha Totakura

- Sree Harsha Totakura -

{{ _("PhD Student, TU Munich. Currently teaching.") }}

-
-
-

Florian Dold

- Florian Dold -

{{ _("PhD Student, Inria..") }}

-
-
-

Marcello Stanisci

- Marcello Stanisci -

{{ _("Software engineer.") }}

-
-
-
-
-

Dr. Nana Karlstetter

- Nana Karlstetter -

{{ _("Sustainable business development.") }}

-
-
-

Benedikt Müller

-

{{ _("Software engineer. Works on libebics.") }}

-
-
-

Gabor Toth

-

{{ _("Software engineer.") }}

-
-
-
-
-

Martín Olivera

-

{{ _("Translator (Spanish)") }}

-
-
-

Greta Breveglieri

-

{{ _("Translator (Italian)") }}

-
-
-

Ylenia Baldanza

-

{{ _("Translator (Italian)") }}

-
-
-
-
-

Jan Suhr

-

{{ _("Hardware security module") }}

-
-
-

Hartmut Goebel

-

{{ _("Risk management") }}

-
-
-

Julian Kirsch

-

{{ _("PhD student, TU Munich. Currently teaching.") }}

-
-
-
-
-

Oliver Broome

-

{{ _("Software engineer. Works on Android wallet.") }}

-
-
- {% include "common/footer.j2.inc" %} -
- - +{% extends "common/base.j2" %} +{% block body_content %} +
+
+
+

Dr. Christian Grothoff

+ Christian Grothoff +

{{ _("GNU maintainer. Network security & privacy researcher. Software architect.") }}

+
+
+

Leon Schumacher

+ Leon Schumacher +

{{ _("Entrepreneur, Investor, Fortune 100 CIO, IT company director in different industries, ….") }}

+
+
+
+
+

Dr. Jeffrey Burdges

+ Jeffrey Burdges +

{{ _("Applied cryptography. Contact to W3c & Tor.") }}

+
+
+

Dr. Cristina Onete

+ Cristina Onete +

{{ _("Theoretical foundations.") }}

+
+
+

Dr. Richard M. Stallman

+ Richard Stallman +

{{ _("Founder of the GNU project. Ethical guidance and licensing.") }}

+
+
+
+
+

Sree Harsha Totakura

+ Sree Harsha Totakura +

{{ _("PhD Student, TU Munich. Currently teaching.") }}

+
+
+

Florian Dold

+ Florian Dold +

{{ _("PhD Student, Inria..") }}

+
+
+

Marcello Stanisci

+ Marcello Stanisci +

{{ _("Software engineer.") }}

+
+
+
+
+

Dr. Nana Karlstetter

+ Nana Karlstetter +

{{ _("Sustainable business development.") }}

+
+
+

Benedikt Müller

+

{{ _("Software engineer. Works on libebics.") }}

+
+
+

Gabor Toth

+

{{ _("Software engineer.") }}

+
+
+
+
+

Martín Olivera

+

{{ _("Translator (Spanish)") }}

+
+
+

Greta Breveglieri

+

{{ _("Translator (Italian)") }}

+
+
+

Ylenia Baldanza

+

{{ _("Translator (Italian)") }}

+
+
+
+
+

Jan Suhr

+

{{ _("Hardware security module") }}

+
+
+

Hartmut Goebel

+

{{ _("Risk management") }}

+
+
+

Julian Kirsch

+

{{ _("PhD student, TU Munich. Currently teaching.") }}

+
+
+
+
+

Oliver Broome

+

{{ _("Software engineer. Works on Android wallet.") }}

+
+
+
+{% endblock body_content %} diff --git a/common/base.j2 b/common/base.j2 index 58114b5d..d515ea1d 100644 --- a/common/base.j2 +++ b/common/base.j2 @@ -6,7 +6,7 @@ {% include "common/header.j2.inc" %} - + {% include "common/navigation.j2.inc" %} {% block body_content %}{% endblock %}
diff --git a/common/footer.j2.inc b/common/footer.j2.inc index cc96baad..f5395b34 100644 --- a/common/footer.j2.inc +++ b/common/footer.j2.inc @@ -1,7 +1,4 @@ - - + diff --git a/common/header.j2.inc b/common/header.j2.inc index 3087d23e..ab0f6ba4 100644 --- a/common/header.j2.inc +++ b/common/header.j2.inc @@ -32,7 +32,6 @@ - diff --git a/common/navigation.j2.inc b/common/navigation.j2.inc index d4c63c8f..ee2d74e4 100644 --- a/common/navigation.j2.inc +++ b/common/navigation.j2.inc @@ -1,63 +1,44 @@ - + diff --git a/developers.html.j2 b/developers.html.j2 index f6023274..3cad801c 100644 --- a/developers.html.j2 +++ b/developers.html.j2 @@ -1,232 +1,223 @@ - - - - - {{ _("GNU Taler") }} - {{ _("Developers") }} - - {% include "common/header.j2.inc" %} - - -
- {% include "common/navigation.j2.inc" %} - -
-

{{ _("Taler for developers") }}

-
- - -
-
-

{{ _("Free") }}

- -

{{ _("Taler is free software implementing an open - protocol. Anybody is welcome to inspect our code - and integrate our reference implementation into - their applications. Different components of Taler - are being made available under different - licenses. The Affero GPLv3+ is used for the - exchange, the LGPLv3+ is used for reference code - demonstrating integration with merchant platforms, - and licenses like Apache/Mozilla/GPLv3+ are used - for wallets and related customer-facing software. - We are open for constructive suggestions for - maximizing the adoption of this libre payment - platform. ") }}

- -
-
-

{{ _("RESTful") }}

- -

{{ _("Taler is designed to work on the Internet. To - ensure that Taler payments can work with - restrictive network setups, Taler uses a RESTful - protocol over HTTP or HTTPS. Taler's security does - not depend upon the use of HTTPS, but obviously - merchants may choose to offer HTTPS for consistency - and because it generally is better for privacy - compared to HTTP. Taler uses JSON to encode - structure data, making it easy to integrate Taler - with existing Web applications. Taler's protocol - is documented in - detail here. - ") }}

- -
-
-
-
-

{{ _("Code") }}

- -

{{ _("Taler is currently primarily developed by a - research team at Inria and GNUnet e.V. However, - contributions from anyone are welcome. Our Git - repositories can be cloned using the Git and HTTP - access methods against git.taler.net with - the name of the respective repository. A list of - public repositories can be found in - our GitWeb. - ") }}

- -
-
-

{{ _("Documentation") }}

- -

{{ _("In addition to this website, - the documented - code and - the API - documentation, we are in the process of - preparing a comprehensive design document which - will be published here soon. ") }}

-
-
-

{{ _("Discussion") }}

- -

{{ _("We have a mailinglist for developer discussions. - You can subscribe to it or read the list archive at - http://lists.gnu.org/mailman/listinfo/taler.") }}

-
-
- -
-
-

{{ _("Regression Testing") }}

- -

{{ _("We have - Buildbot - automation tests to detect regressions and check - for portability at - buildbot.taler.net. - ") }}

-
-
-

{{ _("Code Coverage Analysis") }}

- -

{{ _("We use - LCOV - to analyze the code coverage of our tests, the - results are available - at lcov.taler.net. - ") }}

-
-
-

{{ _("Performance Analysis") }}

- -

{{ _("We - use Gauger - for performance regression analysis of the exchange - backend - at gauger.taler.net. - ") }}

-
-
- -
-

{{ _("Taler system overview") }}

- -

{{ _("The Taler system consists of protocols executed among - a number of actors with the help - of Free Software - as illustrated in the illustration on the right. - Typical transactions involve the following steps: ") - }}

- - system overview -
    -
  1. {{ _("A customer instructs his bank to - transfer funds from his account to the Taler - exchange (top left). In the subject of the - transaction, he includes an authentication - token from his electronic wallet. In - Taler terminology, the customer creates a - reserve at the exchange. ") }}
  2. - -
  3. {{ _("Once the exchange has received the wire - transfer, it allows the customer's electronic - wallet to withdraw electronic coins. - The electronic coins are digital - representations of the original currency from - the transfer. It is important to note that the - exchange does not learn the "serial - numbers" of the coins created in this - process, so it cannot tell later which customer - purchased what at which merchant. The use of - Taler does not change the currency or the total - value of the funds (except for fees which the - exchange may charge for the service). ") - }}
  4. - -
  5. {{ _("Once the customer has the digital coins in his - wallet, the wallet can be used to spend - the coins with merchant portals that support - the Taler payment system and accept the - respective exchange as a business partner - (bottom arrow). This creates a digital contract - signed by the customer's coins and the - merchant. If necessary, the customer can later - use this digitally signed contract in a court - of law to prove the exact terms of the contract - and that he paid the respective amount. The - customer does not learn the banking details of - the merchant, and Taler does not require the - merchant to learn the identity of the - customer. Naturally, the customer can spend any - fraction of his digital coins (the system takes - care of customers getting change). ") }}
  6. - -
  7. {{ _("Merchants receiving digital - coins deposit the respective receipts - that resulted from the contract signing with - the customer at the exchange to redeem the - coins. The deposit step does not reveal the - details of the contract between the customer - and the merchant or the identity of the - customer to the exchange in any way. However, - the exchange does learn the identity of the - merchant via the provided bank routing - information. The merchant can, for example - when compelled by the state for taxation, - provide information linking the individual - deposit to the respective contract signed by - the customer. Thus, the exchange's database - allows the state to enforce that merchants pay - applicable taxes (and do not engage in illegal - contracts). ") }}
  8. - -
  9. {{ _("Finally, the exchange transfers funds - corresponding to the digital coins redeemed by - the merchants to the merchant's bank - account. The exchange may combine multiple - small transactions into one larger bank - transfer. The merchant can query the exchange - about the relationship between the bank - transfers and the individual claims that were - deposited. ") }}
  10. - -
  11. {{ _("Most importantly, the exchange keeps - cryptographic proofs that allow it to - demonstrate that it is operating correctly to - third parties. The system requires an - external auditor, such as a - government-appointed financial regulatory body, - to frequently verify the exchange's databases - and check that its bank balance matches the - total value of the remaining coins in - circulation. ") }}
  12. - -
  13. {{ _("Without the auditor, the exchange operators - could embezzle funds they are holding in - reserve. Customers and merchants cannot cheat - each other or the exchange. If any party's - computers are compromised, the financial damage - is limited to the respective party and - proportional to the funds they have in - circulation during the period of the - compromise. ") }}
  14. -
-

-
- {% include "common/footer.j2.inc" %}:w -
- - +{% extends "common/base.j2" %} +{% block body_content %} +
+
+

{{ _("Taler for developers") }}

+
+
+ +
+
+
+

{{ _("Free") }}

+ +

{{ _("Taler is free software implementing an open + protocol. Anybody is welcome to inspect our code + and integrate our reference implementation into + their applications. Different components of Taler + are being made available under different + licenses. The Affero GPLv3+ is used for the + exchange, the LGPLv3+ is used for reference code + demonstrating integration with merchant platforms, + and licenses like Apache/Mozilla/GPLv3+ are used + for wallets and related customer-facing software. + We are open for constructive suggestions for + maximizing the adoption of this libre payment + platform. ") }}

+ +
+
+

{{ _("RESTful") }}

+ +

{{ _("Taler is designed to work on the Internet. To + ensure that Taler payments can work with + restrictive network setups, Taler uses a RESTful + protocol over HTTP or HTTPS. Taler's security does + not depend upon the use of HTTPS, but obviously + merchants may choose to offer HTTPS for consistency + and because it generally is better for privacy + compared to HTTP. Taler uses JSON to encode + structure data, making it easy to integrate Taler + with existing Web applications. Taler's protocol + is documented in + detail here. + ") }}

+ +
+
+
+
+

{{ _("Code") }}

+ +

{{ _("Taler is currently primarily developed by a + research team at Inria and GNUnet e.V. However, + contributions from anyone are welcome. Our Git + repositories can be cloned using the Git and HTTP + access methods against git.taler.net with + the name of the respective repository. A list of + public repositories can be found in + our GitWeb. + ") }}

+ +
+
+

{{ _("Documentation") }}

+ +

{{ _("In addition to this website, + the documented + code and + the API + documentation, we are in the process of + preparing a comprehensive design document which + will be published here soon. ") }}

+
+
+

{{ _("Discussion") }}

+ +

{{ _("We have a mailinglist for developer discussions. + You can subscribe to it or read the list archive at + http://lists.gnu.org/mailman/listinfo/taler.") }}

+
+
+ +
+
+

{{ _("Regression Testing") }}

+ +

{{ _("We have + Buildbot + automation tests to detect regressions and check + for portability at + buildbot.taler.net. + ") }}

+
+
+

{{ _("Code Coverage Analysis") }}

+ +

{{ _("We use + LCOV + to analyze the code coverage of our tests, the + results are available + at lcov.taler.net. + ") }}

+
+
+

{{ _("Performance Analysis") }}

+ +

{{ _("We + use Gauger + for performance regression analysis of the exchange + backend + at gauger.taler.net. + ") }}

+
+
+ +
+

{{ _("Taler system overview") }}

+ +

{{ _("The Taler system consists of protocols executed among + a number of actors with the help + of Free Software + as illustrated in the illustration on the right. + Typical transactions involve the following steps: ") + }}

+ + system overview +
    +
  1. {{ _("A customer instructs his bank to + transfer funds from his account to the Taler + exchange (top left). In the subject of the + transaction, he includes an authentication + token from his electronic wallet. In + Taler terminology, the customer creates a + reserve at the exchange. ") }}
  2. + +
  3. {{ _("Once the exchange has received the wire + transfer, it allows the customer's electronic + wallet to withdraw electronic coins. + The electronic coins are digital + representations of the original currency from + the transfer. It is important to note that the + exchange does not learn the "serial + numbers" of the coins created in this + process, so it cannot tell later which customer + purchased what at which merchant. The use of + Taler does not change the currency or the total + value of the funds (except for fees which the + exchange may charge for the service). ") + }}
  4. + +
  5. {{ _("Once the customer has the digital coins in his + wallet, the wallet can be used to spend + the coins with merchant portals that support + the Taler payment system and accept the + respective exchange as a business partner + (bottom arrow). This creates a digital contract + signed by the customer's coins and the + merchant. If necessary, the customer can later + use this digitally signed contract in a court + of law to prove the exact terms of the contract + and that he paid the respective amount. The + customer does not learn the banking details of + the merchant, and Taler does not require the + merchant to learn the identity of the + customer. Naturally, the customer can spend any + fraction of his digital coins (the system takes + care of customers getting change). ") }}
  6. + +
  7. {{ _("Merchants receiving digital + coins deposit the respective receipts + that resulted from the contract signing with + the customer at the exchange to redeem the + coins. The deposit step does not reveal the + details of the contract between the customer + and the merchant or the identity of the + customer to the exchange in any way. However, + the exchange does learn the identity of the + merchant via the provided bank routing + information. The merchant can, for example + when compelled by the state for taxation, + provide information linking the individual + deposit to the respective contract signed by + the customer. Thus, the exchange's database + allows the state to enforce that merchants pay + applicable taxes (and do not engage in illegal + contracts). ") }}
  8. + +
  9. {{ _("Finally, the exchange transfers funds + corresponding to the digital coins redeemed by + the merchants to the merchant's bank + account. The exchange may combine multiple + small transactions into one larger bank + transfer. The merchant can query the exchange + about the relationship between the bank + transfers and the individual claims that were + deposited. ") }}
  10. + +
  11. {{ _("Most importantly, the exchange keeps + cryptographic proofs that allow it to + demonstrate that it is operating correctly to + third parties. The system requires an + external auditor, such as a + government-appointed financial regulatory body, + to frequently verify the exchange's databases + and check that its bank balance matches the + total value of the remaining coins in + circulation. ") }}
  12. + +
  13. {{ _("Without the auditor, the exchange operators + could embezzle funds they are holding in + reserve. Customers and merchants cannot cheat + each other or the exchange. If any party's + computers are compromised, the financial damage + is limited to the respective party and + proportional to the funds they have in + circulation during the period of the + compromise. ") }}
  14. +
+

+
+ {% include "common/footer.j2.inc" %}:w +
+{% endblock body_content %} diff --git a/governments.html.j2 b/governments.html.j2 index 2512bb22..23494400 100644 --- a/governments.html.j2 +++ b/governments.html.j2 @@ -1,155 +1,144 @@ -3 - - - - {{ _("GNU Taler") }} - {{ _("Governments") }} - - {% include "common/header.j2.inc" %} - - -
- {% include "common/navigation.j2.inc" %} - -
-

{{ _("Advantages for Governments") }}

- -
- -

{{ _("Taler provides accountability to ensure business - accepting payments operate legally, while also - respecting civil liberties of citizens spending - digital cash. Taler is a commons, a payment system - based on open standards and free software. Taler - needs governments to set a financial framework and - to act as trusted regulators. Taler contributes to - digital sovereignty in the critial financial - infrastructure.") }}

- -
-
- - -
-
-

{{ _("Taxable") }}

- -

{{ _("Taler was - built with the goal of fighting corruption and supporting taxation. - With Taler, the receiver of any form of payment is - easily identified by the government, and the merchant - can be compelled to provide the contract that was accepted - by the customer. Governments can use this data to - tax businesses and individuals based on their - income, making tax evasion and black markets less - viable.") }}

- -

{{ _("Thus, despite offering anonymity for citizens - spending digital cash to buy goods and services, - Taler also ensures that the state can observe - incoming funds. This can be used to ensure - businesses engage only in legal activities, and do - not evade income tax, sales tax or value-added tax. - However, this observational capability does not - extend to the immediate personal domain. In - particular, sharing access to funds within a family - or synchronizing wallets across multiple devices is not - subject to monitoring.") }}

- -
-

{{ _("Secure") }}

- -

{{ _("Taler's payments are cryptographically - secured. Thus, customers, merchants and the - exchange can mathematically demonstrate their - lawful behavior in court in case of - disputes. Financial damages are strictly limited, - improving economic security for individuals, - merchants, the exchange and the state.") }} - -

{{ _("By design, the Taler payment service provider is - subject to financial regulation. Financial - regulation and regular audits are critical to - establish trust. In particular, the Taler design - mandates the existence of an independent auditor - who checks cryptographic proofs that accumulate at - the payment service provider to ensure that the - escrow account is managed honestly. This ensures - that the payment service provider does not threaten - the economy due to fraud.") }}

-

{{ - _("Libre") }}

- -

{{ _("Taler is free software implementing an open - protocol standard. Thus, Taler will enable - competition and avoid the monopolization of payment - systems that threatens global political and - financial stability today.") }}

- - -
-
-

{{ _("Efficient") }}

- -

{{ _("Taler has an efficient design. Unlike - timeline-based payment systems, such as Bitcoin, - Taler will not threaten the availability of - national electric grids or (significantly) - contribute to environmental pollution.") }}

- -
-
-
-

{{ _("Taler as seen by governments") }}

- -

{{ _("Governments can observe traditional wire transfers - entering and leaving the Taler system, and require - merchants and exchange operators to provide certain - information during financial audits. Exchange - operators are expected to be permanently checked by - auditors, while merchants may be required to reveal - information during regular tax audits. Information - available to the government includes: ") }}

- -

- government perspective -

    - -
  • {{ _("From the banking system: The total amount of - digital currency obtained by a customer. The - government could impose limits on how many - digital coins a customer may withdraw within a - given timeframe.") }}
  • - -
  • {{ _("From the banking system: The total amount of - income received by any merchant via the Taler - system.") }}
  • - -
  • {{ _("From auditing the exchange: The amounts of - digital coins legitimately withdrawn by - customers from the exchange, the value of - non-redeemed digital coins in customer's - wallets, the value and corresponding wire - details of deposit operations performed by - merchants with the exchange, and the income of - the exchange from transaction fees.") }}
  • - -
  • {{ _("From auditing merchants: For each deposit - operation, the exact details of the underlying - contract that was signed between customer and - merchant. However, this information would - typically not include the identity of the - customer. Note that while the customer can - decide to prove that it was his transaction - (i.e. in court when suing the merchant if the - merchant failed to deliver on the contract), - merchant, exchange and government cannot find - out the customer's identity from the information - that Taler collects.") }}
  • - -
-

-
- {% include "common/footer.j2.inc" %} -
- - +{% extends "common/base.j2" %} +{% block body_content %} + +
+
+

{{ _("Advantages for Governments") }}

+

{{ _("Taler provides accountability to ensure business + accepting payments operate legally, while also + respecting civil liberties of citizens spending + digital cash. Taler is a commons, a payment system + based on open standards and free software. Taler + needs governments to set a financial framework and + to act as trusted regulators. Taler contributes to + digital sovereignty in the critial financial + infrastructure.") }}

+
+
+ +
+ + +
+
+

{{ _("Taxable") }}

+ +

{{ _("Taler was + built with the goal of fighting corruption and supporting taxation. + With Taler, the receiver of any form of payment is + easily identified by the government, and the merchant + can be compelled to provide the contract that was accepted + by the customer. Governments can use this data to + tax businesses and individuals based on their + income, making tax evasion and black markets less + viable.") }}

+ +

{{ _("Thus, despite offering anonymity for citizens + spending digital cash to buy goods and services, + Taler also ensures that the state can observe + incoming funds. This can be used to ensure + businesses engage only in legal activities, and do + not evade income tax, sales tax or value-added tax. + However, this observational capability does not + extend to the immediate personal domain. In + particular, sharing access to funds within a family + or synchronizing wallets across multiple devices is not + subject to monitoring.") }}

+ +
+

{{ _("Secure") }}

+ +

{{ _("Taler's payments are cryptographically + secured. Thus, customers, merchants and the + exchange can mathematically demonstrate their + lawful behavior in court in case of + disputes. Financial damages are strictly limited, + improving economic security for individuals, + merchants, the exchange and the state.") }} + +

{{ _("By design, the Taler payment service provider is + subject to financial regulation. Financial + regulation and regular audits are critical to + establish trust. In particular, the Taler design + mandates the existence of an independent auditor + who checks cryptographic proofs that accumulate at + the payment service provider to ensure that the + escrow account is managed honestly. This ensures + that the payment service provider does not threaten + the economy due to fraud.") }}

+

{{ + _("Libre") }}

+ +

{{ _("Taler is free software implementing an open + protocol standard. Thus, Taler will enable + competition and avoid the monopolization of payment + systems that threatens global political and + financial stability today.") }}

+ + +
+
+

{{ _("Efficient") }}

+ +

{{ _("Taler has an efficient design. Unlike + timeline-based payment systems, such as Bitcoin, + Taler will not threaten the availability of + national electric grids or (significantly) + contribute to environmental pollution.") }}

+ +
+
+
+

{{ _("Taler as seen by governments") }}

+ +

{{ _("Governments can observe traditional wire transfers + entering and leaving the Taler system, and require + merchants and exchange operators to provide certain + information during financial audits. Exchange + operators are expected to be permanently checked by + auditors, while merchants may be required to reveal + information during regular tax audits. Information + available to the government includes: ") }}

+ +

+ government perspective +

    + +
  • {{ _("From the banking system: The total amount of + digital currency obtained by a customer. The + government could impose limits on how many + digital coins a customer may withdraw within a + given timeframe.") }}
  • + +
  • {{ _("From the banking system: The total amount of + income received by any merchant via the Taler + system.") }}
  • + +
  • {{ _("From auditing the exchange: The amounts of + digital coins legitimately withdrawn by + customers from the exchange, the value of + non-redeemed digital coins in customer's + wallets, the value and corresponding wire + details of deposit operations performed by + merchants with the exchange, and the income of + the exchange from transaction fees.") }}
  • + +
  • {{ _("From auditing merchants: For each deposit + operation, the exact details of the underlying + contract that was signed between customer and + merchant. However, this information would + typically not include the identity of the + customer. Note that while the customer can + decide to prove that it was his transaction + (i.e. in court when suing the merchant if the + merchant failed to deliver on the contract), + merchant, exchange and government cannot find + out the customer's identity from the information + that Taler collects.") }}
  • + +
+

+
+
+ +{% endblock body_content %} diff --git a/index.html.j2 b/index.html.j2 index 3d7445a1..362eedad 100644 --- a/index.html.j2 +++ b/index.html.j2 @@ -1,34 +1,32 @@ {% extends "common/base.j2" %} {% block body_content %} -
- -
- Taler logo -
-
-

{{ _("Independent One-Click Payments!") }}

+ +
+ Taler logo -

- {% trans %} - Taler is an electronic payment system under - development - at Inria. We expect to make it operational in 2017. - Meanwhile you can learn about Taler on this website, try the demo - and look at our developer and API documentation. - {% endtrans %} -

- +
+

{{ _("Independent One-Click Payments!") }}

+

+ {% trans %} + Taler is an electronic payment system under + development + at Inria. We expect to make it operational in 2017. + Meanwhile you can learn about Taler on this website, try the demo + and look at our developer and API documentation. + {% endtrans %} +

+
-

Advantages of Taler

+

Design goals of Taler

- {{ _("Taxable") }} +

{{ _("Taxable") }}

{% trans %} @@ -40,7 +38,7 @@

- {{ _("Privacy-friendly") }} +

{{ _("Privacy-friendly") }}

{% trans %} When you pay with Taler, your identity does not @@ -53,7 +51,7 @@

- {{ _("Libre") }} +

{{ _("Libre") }}

{% trans %} @@ -69,7 +67,7 @@

- {{ _("Practical") }} +

{{ _("Practical") }}

{% trans %} @@ -82,7 +80,7 @@

- {{ _("Stable") }} +

{{ _("Stable") }}

{% trans %} @@ -97,7 +95,7 @@

- {{ _("Security-focused") }} +

{{ _("Security-focused") }}

{% trans %} @@ -112,6 +110,7 @@

+
@@ -122,7 +121,10 @@

Receiving payments with Taler

- TODO + To receive Taler payments, a merchant only needs a bank account (or + any other kind of payment address) in the desired currency. We provide an + SDK in various languages that makes the integration into a merchant's store + painless.

Learn more

diff --git a/investors.html.j2 b/investors.html.j2 index 895682f6..9794acfd 100644 --- a/investors.html.j2 +++ b/investors.html.j2 @@ -1,102 +1,101 @@ - - - - - {{ _("GNU Taler") }} - {{ _("Investors") }} - - {% include "common/header.j2.inc" %} - - -
- {% include "common/navigation.j2.inc" %} - -
-

{{ _("Invest in Taler!") }}

-
-

{{ _("We have created a company, Taler Systems SA in - Luxemburg.
- Please contact invest@taler.net - if you want to invest in Taler.") }}

-
-
-
-
-

{{ _("The Team") }}

+{% extends "common/base.j2" %} +{% block body_content %} -

{{ _("Our team combines world-class business leaders, - cryptographers, software engineers, civil-rights - activits and academics. We are unified by a vision - of how payments should work and the goal of - imposing this vision upon the world.") }}

+
+
+

{{ _("Invest in Taler!") }}

+
+

+ {% trans %} + We have created a company, Taler Systems SA in + Luxemburg.
+ Please contact invest@taler.net + if you want to invest in Taler. + {% endtrans %} +

+
+
+
-

{{ _("We are currently supported by Inria, the French - national institute for research in informatics and - automation, and the Renewable Freedom Foundation.") }}

-
-
-

{{ _("The Technology") }}

-

{{ _("All transactions in Taler are secured using modern - cryptography and trust in all parties is - minimized. Financial damage is bounded (for - customers, merchants and the exchange) even in the - case that systems are compromised and private keys - are stolen. Databases can be audited for - consistency, resulting in either the detection of - compromised systems or the demonstration that - participants were honest. Actual transaction costs - are fractions of a cent.") }}

-
-
-

{{ _("The Business") }}

-

{{ _("The scalable business model for Taler is the operation - of the payment service provider, which converts money from - traditional payment systems (Mastercard, SEPA, - Visa, Bitcoin, ACH, SWIFT, etc.) to anonymous - electronic coins in the same currency. The customer - can then redeem the electronic coins at a merchant, - who can exchange them for money represented using - traditional payment systems at the exchange. The - exchange charges fees (to the customer, - merchant or both) to facilitate the transactions.") - }}

-
-
-
-

{{ _("Taler as seen by the payment service operator") }}

+
+
+
+

{{ _("The Team") }}

-

{{ _("The payment service operator runs a Taler - exchange, which is a Web service portal that - keeps databases with transaction details and - cryptographic proofs. Its operational expenses are - thus related to its interactions with the banking - system and the operation of the computing - infrastructure, while its income is based on - transaction fees it may charge for the various - interactions. Key interactions of the exchange - include: ") }}

+

{{ _("Our team combines world-class business leaders, + cryptographers, software engineers, civil-rights + activits and academics. We are unified by a vision + of how payments should work and the goal of + imposing this vision upon the world.") }}

-

- operator perspective -

    -
  • {{ _("Create a reserve based on an incoming - wire transfer from a customer.") }}
  • +

    {{ _("We are currently supported by Inria, the French + national institute for research in informatics and + automation, and the Renewable Freedom Foundation.") }}

    +
+
+

{{ _("The Technology") }}

-
  • {{ _("Allow customers to withdraw (and refresh) - digital coins from their reserve.") }}
  • +

    {{ _("All transactions in Taler are secured using modern + cryptography and trust in all parties is + minimized. Financial damage is bounded (for + customers, merchants and the exchange) even in the + case that systems are compromised and private keys + are stolen. Databases can be audited for + consistency, resulting in either the detection of + compromised systems or the demonstration that + participants were honest. Actual transaction costs + are fractions of a cent.") }}

    +
    +
    +

    {{ _("The Business") }}

    -
  • {{ _("Accept and validate deposits from merchants.") }}
  • +

    {{ _("The scalable business model for Taler is the operation + of the payment service provider, which converts money from + traditional payment systems (Mastercard, SEPA, + Visa, Bitcoin, ACH, SWIFT, etc.) to anonymous + electronic coins in the same currency. The customer + can then redeem the electronic coins at a merchant, + who can exchange them for money represented using + traditional payment systems at the exchange. The + exchange charges fees (to the customer, + merchant or both) to facilitate the transactions.") + }}

    +
    +
    +
    +

    {{ _("Taler as seen by the payment service operator") }}

    -
  • {{ _("Execute wire transfers to merchants in - response to validated deposits.") }}
  • +

    {{ _("The payment service operator runs a Taler + exchange, which is a Web service portal that + keeps databases with transaction details and + cryptographic proofs. Its operational expenses are + thus related to its interactions with the banking + system and the operation of the computing + infrastructure, while its income is based on + transaction fees it may charge for the various + interactions. Key interactions of the exchange + include: ") }}

    -
  • {{ _("Preserve and provide cryptographic proofs of - correct operation for audits by financial regulators.") }}
  • - -

    -
    - {% include "common/footer.j2.inc" %} -
    - - +

    + operator perspective +

      +
    • {{ _("Create a reserve based on an incoming + wire transfer from a customer.") }}
    • + +
    • {{ _("Allow customers to withdraw (and refresh) + digital coins from their reserve.") }}
    • + +
    • {{ _("Accept and validate deposits from merchants.") }}
    • + +
    • {{ _("Execute wire transfers to merchants in + response to validated deposits.") }}
    • + +
    • {{ _("Preserve and provide cryptographic proofs of + correct operation for audits by financial regulators.") }}
    • +
    +

    + +
    +{% endblock body_content %} diff --git a/justified-nav.css b/justified-nav.css deleted file mode 100644 index b8b8b74c..00000000 --- a/justified-nav.css +++ /dev/null @@ -1,80 +0,0 @@ -body { - padding-top: 20px; -} - -.footer { - padding-top: 40px; - padding-bottom: 40px; - margin-top: 40px; -} - -/* Main marketing message and sign up button */ -.jumbotron { - text-align: center; - background-color: transparent; -} -.jumbotron .btn { - padding: 12px 22px; - font-size: 19px; -} - -/* Customize the nav-justified links to be fill the entire space of the .navbar */ - -.nav-justified { - background: #fff; -} -.nav-justified > li > a { - border-radius: 20px; - padding-top: 5px; - padding-bottom: 5px; - margin-bottom: 5px; - margin-left: 10px; - margin-top: 5px; - font-weight: normal; - color: #000; - text-align: center; - font-size: large; -} - -.nav-justified > .active > a, -.nav-justified > .active > a:hover, -.nav-justified > .active > a:focus { - background-color: #ddd; -} - -.nav-justified > li > a:hover { - transition: background-color 0.3s; -} - -.nav-justified > .m_demo > a { - font-weight: bold; -} - - -/* Responsive: Portrait tablets and up */ -@media screen and (min-width: 768px) { - /* Remove the padding we set earlier */ - .masthead, - .marketing, - .footer { - padding-right: 0; - padding-left: 0; - } -} - -.navbar-taler { - background-color: #fff; - border-bottom: 2px solid #eee; -} - -.navbar-taler .navbar-toggle { - border-color: #ddd; -} -.navbar-taler .navbar-toggle:hover, -.navbar-taler .navbar-toggle:focus { - background-color: #ddd; -} -.navbar-taler .navbar-toggle .icon-bar { - background-color: #888; -} - diff --git a/merchants.html.j2 b/merchants.html.j2 index ce2a47f2..304a5078 100644 --- a/merchants.html.j2 +++ b/merchants.html.j2 @@ -1,169 +1,157 @@ - - - - - {{ _("GNU Taler") }} - {{ _("Merchants") }} - - {% include "common/header.j2.inc" %} - - -
    - {% include "common/navigation.j2.inc" %} - -
    -

    {{ _("Advantages for Merchants") }}

    -
    - -

    {{ _("Taler is a cost-effective electronic payment system - which provides you with cryptographic proof that - the payment worked correctly within milliseconds. - Your Web customers pay with previously unknown - levels of convenience without risk of fraud.") - }}

    - -
    -
    -
    -
    -

    {{ _("Fast") }}

    - -

    {{ _("Processing transactions with Taler is fast, - allowing you to confirm the transaction with your - customer virtually immediately. Your customers - will appreciate that they do not have to type in - credit card information and play the "verified - by" game. By making payments significantly - more convenient for your customers, you may be able - to use Taler for small transactions that would not - work with credit card payments due to the mental - overhead for customers.") }}

    - -
    -
    -

    {{ _("Secure") }}

    - -

    {{ _("You will have cryptographic proof of payment from - the Taler payment service provider. Taler does not - require you to undergo any particular security - audits (such as PCI DSS), processes or procedures, - as you never handle sensitive customer account - information. Your systems will have customer - contracts wih qualified signatures for all - transactions which you can use in court in case of - disputes.") }}

    - -
    -
    -

    {{ _("Free Software") }}

    - -

    {{ _("Taler is free software, and you can use the - liberally-licensed reference code as a starting - point to integrate Taler into your services. To use - Taler, you do not need to pay license fees, and the - free software development model will ensure that - you can select from many competent integrators for - support.") }}

    - -
    -
    -
    -
    -

    {{ _("Low Fees") }}

    - -

    {{ _("Taler is designed to minimize the work the exchange - needs to perform. Combined with Taler's strong - security which prevents fraud, payment service - providers can operate with very low overhead and - thus low transaction fees.") }}

    - -
    -
    -

    {{ _("Flexible") }}

    - -

    {{ _("Taler can be used for different currencies (such as - Euros, US Dollars or Bitcoins) and different - payment models limited only by what the payment - service provider supports in its interactions.") - }}

    - -
    -
    -

    {{ _("Ethical") }}

    - -

    {{ _("Taler prevents tax evasion and money laundering. - Taler's protocols are efficient and do not waste - energy. Taler encourages transparency by providing - an open standard and free software reference - implementations.") }}

    - -
    -
    -
    -

    {{ _("Taler as seen by merchants") }}

    - -

    {{ _("Merchants supporting the Taler system need to - integrate some relatively simple logic into their - transaction processing system. Typical steps - performed by the merchant system are: ") }}

    - -

    - merchant perspective -

      - -
    1. {{ _("The new logic detects when a customer's system - supports Taler and then needs to send a - cryptographically signed version of the proposed - contract in a simple JSON format to the - customer. The message also includes salted, - hashed wire details for the merchant, as well as - restrictions as to which exchange operators the - merchant is willing to deal with.") }}
    2. - -
    3. {{ _("The customer sends a signed response which - states that certain digital coins now belong to - the merchant to both signal acceptance of the - deal as well as to pay the respective amount - (bottom).") }}
    4. - -
    5. {{ _("The merchant then forwards the signed messages - received from the customer to the exchange, - together with its wire details and the salt - (without hashing). The exchange verifies the - details and sends a signed confirmation (or an - error message) to the merchant. The merchant - checks that the exchange's signature is valid, - sends a confirmation to the customer and - executes the contract-specific business - logic.") }}
    6. - -
    7. {{ _("The exchange performs wire transfers - corresponding to the claims deposited by the - merchant. Note that the exchange may charge - fees for the deposit operation, hence merchants - may impose limits restricting the set of - exchange operators they are willing to deal - with, for example by imposing a bound on - deposit fees.") }}
    8. -
    -

    -
    -
    -

    {{ _("Manuals for merchants") }}

    -

    -

      -
    • {{ _("The GNU Taler merchant backend operator manual") }} - (html, - pdf)
    • -
    • {{ _("The GNU Taler Web shop integration tutorial (PHP)") }} - (html, - pdf)
    • -
    • {{ _("The GNU Taler Web shop integration tutorial (Python)") }} - (html, - pdf)
    • -
    -

    -
    - {% include "common/footer.j2.inc" %} -
    - - +{% extends "common/base.j2" %} +{% block body_content %} +
    +
    +

    {{ _("Advantages for Merchants") }}

    +

    {{ _("Taler is a cost-effective electronic payment system + which provides you with cryptographic proof that + the payment worked correctly within milliseconds. + Your Web customers pay with previously unknown + levels of convenience without risk of fraud.") + }}

    +
    +
    + +
    +
    +
    +

    {{ _("Fast") }}

    + +

    {{ _("Processing transactions with Taler is fast, + allowing you to confirm the transaction with your + customer virtually immediately. Your customers + will appreciate that they do not have to type in + credit card information and play the "verified + by" game. By making payments significantly + more convenient for your customers, you may be able + to use Taler for small transactions that would not + work with credit card payments due to the mental + overhead for customers.") }}

    + +
    +
    +

    {{ _("Secure") }}

    + +

    {{ _("You will have cryptographic proof of payment from + the Taler payment service provider. Taler does not + require you to undergo any particular security + audits (such as PCI DSS), processes or procedures, + as you never handle sensitive customer account + information. Your systems will have customer + contracts wih qualified signatures for all + transactions which you can use in court in case of + disputes.") }}

    + +
    +
    +

    {{ _("Free Software") }}

    + +

    {{ _("Taler is free software, and you can use the + liberally-licensed reference code as a starting + point to integrate Taler into your services. To use + Taler, you do not need to pay license fees, and the + free software development model will ensure that + you can select from many competent integrators for + support.") }}

    + +
    +
    +
    +
    +

    {{ _("Low Fees") }}

    + +

    {{ _("Taler is designed to minimize the work the exchange + needs to perform. Combined with Taler's strong + security which prevents fraud, payment service + providers can operate with very low overhead and + thus low transaction fees.") }}

    + +
    +
    +

    {{ _("Flexible") }}

    + +

    {{ _("Taler can be used for different currencies (such as + Euros, US Dollars or Bitcoins) and different + payment models limited only by what the payment + service provider supports in its interactions.") + }}

    + +
    +
    +

    {{ _("Ethical") }}

    + +

    {{ _("Taler prevents tax evasion and money laundering. + Taler's protocols are efficient and do not waste + energy. Taler encourages transparency by providing + an open standard and free software reference + implementations.") }}

    + +
    +
    +
    +

    {{ _("Taler as seen by merchants") }}

    + +

    {{ _("Merchants supporting the Taler system need to + integrate some relatively simple logic into their + transaction processing system. Typical steps + performed by the merchant system are: ") }}

    + +

    + merchant perspective +

      + +
    1. {{ _("The new logic detects when a customer's system + supports Taler and then needs to send a + cryptographically signed version of the proposed + contract in a simple JSON format to the + customer. The message also includes salted, + hashed wire details for the merchant, as well as + restrictions as to which exchange operators the + merchant is willing to deal with.") }}
    2. + +
    3. {{ _("The customer sends a signed response which + states that certain digital coins now belong to + the merchant to both signal acceptance of the + deal as well as to pay the respective amount + (bottom).") }}
    4. + +
    5. {{ _("The merchant then forwards the signed messages + received from the customer to the exchange, + together with its wire details and the salt + (without hashing). The exchange verifies the + details and sends a signed confirmation (or an + error message) to the merchant. The merchant + checks that the exchange's signature is valid, + sends a confirmation to the customer and + executes the contract-specific business + logic.") }}
    6. + +
    7. {{ _("The exchange performs wire transfers + corresponding to the claims deposited by the + merchant. Note that the exchange may charge + fees for the deposit operation, hence merchants + may impose limits restricting the set of + exchange operators they are willing to deal + with, for example by imposing a bound on + deposit fees.") }}
    8. +
    +

    +
    +
    +

    {{ _("Manuals for merchants") }}

    +

    +

      +
    • {{ _("The GNU Taler merchant backend operator manual") }} + (html, + pdf)
    • +
    • {{ _("The GNU Taler Web shop integration tutorial (PHP)") }} + (html, + pdf)
    • +
    • {{ _("The GNU Taler Web shop integration tutorial (Python)") }} + (html, + pdf)
    • +
    +

    +
    +
    +{% endblock body_content %} diff --git a/styles.css b/styles.css index b1d6e624..c384a0e8 100644 --- a/styles.css +++ b/styles.css @@ -1,3 +1,8 @@ +body .jumbotron { + background-color: white; +} + + .lang-slector { float: right; padding-top: 2mm; @@ -28,3 +33,8 @@ html { margin-left:5px; margin-top: 8px; } + +#mybody { + /* override ugly bootstrap defaults */ + color: black; +} diff --git a/template.py b/template.py index ed8f47eb..78a801ff 100755 --- a/template.py +++ b/template.py @@ -50,7 +50,12 @@ for in_file in glob.glob("*.j2"): env.install_gettext_translations(tr, newstyle=True) - content = tmpl.render(lang=locale, url=url, self_localized=self_localized, url_localized=url_localized) + content = tmpl.render( + lang=locale, + url=url, + self_localized=self_localized, + url_localized=url_localized, + filename=name + "." + ext) out_name = "./" + locale + "/" + in_file.rstrip(".j2") os.makedirs("./" + locale, exist_ok=True) with codecs.open(out_name, "w", "utf-8") as f: -- cgit v1.2.3