[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-merchant] branch master updated: move documentation
|
From: |
gnunet |
|
Subject: |
[GNUnet-SVN] [taler-merchant] branch master updated: move documentation to docs repo |
|
Date: |
Thu, 29 Aug 2019 13:36:10 +0200 |
This is an automated email from the git hooks/post-receive script.
dold pushed a commit to branch master
in repository merchant.
The following commit(s) were added to refs/heads/master by this push:
new cb8472b move documentation to docs repo
cb8472b is described below
commit cb8472b5b0750c2e6ff22b8e111c220fa189ba4d
Author: Florian Dold <address@hidden>
AuthorDate: Thu Aug 29 13:36:07 2019 +0200
move documentation to docs repo
---
doc/Makefile.am | 61 --
doc/agpl.texi | 698 ----------------------
doc/arch-api.dot | 27 -
doc/arch.dot | 23 -
doc/arch.txt | 1 -
doc/configuration-format.texi | 73 ---
doc/fdl-1.3.texi | 506 ----------------
doc/highlight.pack.js | 2 -
doc/lgpl.texi | 549 -----------------
doc/manual.texi | 1296 -----------------------------------------
doc/merchant-api-curl.texi | 13 -
doc/merchant-api-php.texi | 13 -
doc/merchant-api-python.texi | 13 -
doc/merchant-api.content.texi | 1068 ---------------------------------
doc/syntax.texi | 44 --
doc/taler-config.texi | 47 --
16 files changed, 4434 deletions(-)
diff --git a/doc/Makefile.am b/doc/Makefile.am
index f135953..1fbae69 100644
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@@ -1,69 +1,8 @@
-all: manual.pdf manual.html
-
-manual.pdf: arch.pdf manual.texi
-manual.html: arch.png manual.texi
-
-%.png: %.dot
- dot -Tpng $< > $@
-%.pdf: %.dot
- dot -Tpdf $< > $@
-
-clean-local:
- -rm -f arch.png arch.pdf arch-api.png arch-api.pdf
-
-merchant-api-curl.pdf: merchant-api.content.texi arch-api.pdf
-merchant-api-python.pdf: merchant-api.content.texi arch-api.pdf
-merchant-api-curl.html: merchant-api.content.texi arch-api.png
-merchant-api-python.html: merchant-api.content.texi arch-api.png
-
-# NOTE: While GNU makeinfo 6.5 supports --css-ref=URL,
-# makeinfo 4.8 (in NetBSD 8.0, macOS, and maybe other
-# base) does only support --css-include=FILE.
-# The only difference is a shorter html output and
-# in 6.5 the ability to use refs instead of include.
-# We prefer not to break builds in this case, so
-# we use the include version which is backwards compatible
-# and upwards compatible, while the ref variant is neither.
-
-AM_MAKEINFOHTMLFLAGS = --no-split --css-include=docstyle.css
--css-include=brown-paper.css
-
man_MANS = \
taler-merchant-benchmark.1 \
taler-merchant-httpd.1
-info_TEXINFOS = \
- manual.texi \
- merchant-api-python.texi \
- merchant-api-curl.texi \
- merchant-api-php.texi
-
-manual_TEXINFOS = \
- version-manual.texi \
- merchant-api.content.texi
-
-merchant_api_python_TEXINFOS = \
- version-merchant-api-python.texi \
- merchant-api.content.texi
-
-merchant_api_curl_TEXINFOS = \
- version-merchant-api-curl.texi \
- merchant-api.content.texi
-
-merchant_api_php_TEXINFOS = \
- version-merchant-api-php.texi \
- merchant-api.content.texi
-
-extra_TEXINFOS = \
- fdl-1.3.texi \
- agpl.texi \
- syntax.texi \
- merchant-api.content.texi
-
EXTRA_DIST = \
- arch.dot \
- $(extra_TEXINFOS) \
- docstyle.css \
- brown-paper.css \
$(man_MANS)
DISTCLEANFILES = \
diff --git a/doc/agpl.texi b/doc/agpl.texi
deleted file mode 100644
index e6ee662..0000000
--- a/doc/agpl.texi
+++ /dev/null
@@ -1,698 +0,0 @@
-@c The GNU Affero General Public License.
-@center Version 3, 19 November 2007
-
-@c This file is intended to be included within another document,
-@c hence no sectioning command or @node.
-
-@display
-Copyright @copyright{} 2007 Free Software Foundation, Inc.
@url{http://fsf.org/}
-
-Everyone is permitted to copy and distribute verbatim copies of this
-license document, but changing it is not allowed.
-@end display
-
-@heading Preamble
-
-The GNU Affero General Public License is a free, copyleft license
-for software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
-
-The licenses for most software and other practical works are
-designed to take away your freedom to share and change the works. By
-contrast, our General Public Licenses are intended to guarantee your
-freedom to share and change all versions of a program--to make sure it
-remains free software for all its users.
-
-When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-Developers that use our General Public Licenses protect your rights
-with two steps: (1) assert copyright on the software, and (2) offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
-
-A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate. Many developers of free software are heartened and
-encouraged by the resulting cooperation. However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
-
-The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community. It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server. Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
-
-An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals. This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
-
-The precise terms and conditions for copying, distribution and
-modification follow.
-
-@heading TERMS AND CONDITIONS
-
-@enumerate 0
-@item Definitions.
-
-``This License'' refers to version 3 of the GNU Affero General Public License.
-
-``Copyright'' also means copyright-like laws that apply to other kinds
-of works, such as semiconductor masks.
-
-``The Program'' refers to any copyrightable work licensed under this
-License. Each licensee is addressed as ``you''. ``Licensees'' and
-``recipients'' may be individuals or organizations.
-
-To ``modify'' a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of
-an exact copy. The resulting work is called a ``modified version'' of
-the earlier work or a work ``based on'' the earlier work.
-
-A ``covered work'' means either the unmodified Program or a work based
-on the Program.
-
-To ``propagate'' a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy. Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-To ``convey'' a work means any kind of propagation that enables other
-parties to make or receive copies. Mere interaction with a user
-through a computer network, with no transfer of a copy, is not
-conveying.
-
-An interactive user interface displays ``Appropriate Legal Notices'' to
-the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License. If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-@item Source Code.
-
-The ``source code'' for a work means the preferred form of the work for
-making modifications to it. ``Object code'' means any non-source form
-of a work.
-
-A ``Standard Interface'' means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-The ``System Libraries'' of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form. A
-``Major Component'', in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-The ``Corresponding Source'' for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities. However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work. For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-The Corresponding Source need not include anything that users can
-regenerate automatically from other parts of the Corresponding Source.
-
-The Corresponding Source for a work in source code form is that same
-work.
-
-@item Basic Permissions.
-
-All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met. This License explicitly affirms your unlimited
-permission to run the unmodified Program. The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work. This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-You may make, run and propagate covered works that you do not convey,
-without conditions so long as your license otherwise remains in force.
-You may convey covered works to others for the sole purpose of having
-them make modifications exclusively for you, or provide you with
-facilities for running those works, provided that you comply with the
-terms of this License in conveying all material for which you do not
-control copyright. Those thus making or running the covered works for
-you must do so exclusively on your behalf, under your direction and
-control, on terms that prohibit them from making any copies of your
-copyrighted material outside their relationship with you.
-
-Conveying under any other circumstances is permitted solely under the
-conditions stated below. Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-@item Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such
-circumvention is effected by exercising rights under this License with
-respect to the covered work, and you disclaim any intention to limit
-operation or modification of the work as a means of enforcing, against
-the work's users, your or third parties' legal rights to forbid
-circumvention of technological measures.
-
-@item Conveying Verbatim Copies.
-
-You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-@item Conveying Modified Source Versions.
-
-You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these
-conditions:
-
-@enumerate a
-@item
-The work must carry prominent notices stating that you modified it,
-and giving a relevant date.
-
-@item
-The work must carry prominent notices stating that it is released
-under this License and any conditions added under section 7. This
-requirement modifies the requirement in section 4 to ``keep intact all
-notices''.
-
-@item
-You must license the entire work, as a whole, under this License to
-anyone who comes into possession of a copy. This License will
-therefore apply, along with any applicable section 7 additional terms,
-to the whole of the work, and all its parts, regardless of how they
-are packaged. This License gives no permission to license the work in
-any other way, but it does not invalidate such permission if you have
-separately received it.
-
-@item
-If the work has interactive user interfaces, each must display
-Appropriate Legal Notices; however, if the Program has interactive
-interfaces that do not display Appropriate Legal Notices, your work
-need not make them do so.
-@end enumerate
-
-A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-``aggregate'' if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit. Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-@item Conveying Non-Source Forms.
-
-You may convey a covered work in object code form under the terms of
-sections 4 and 5, provided that you also convey the machine-readable
-Corresponding Source under the terms of this License, in one of these
-ways:
-
-@enumerate a
-@item
-Convey the object code in, or embodied in, a physical product
-(including a physical distribution medium), accompanied by the
-Corresponding Source fixed on a durable physical medium customarily
-used for software interchange.
-
-@item
-Convey the object code in, or embodied in, a physical product
-(including a physical distribution medium), accompanied by a written
-offer, valid for at least three years and valid for as long as you
-offer spare parts or customer support for that product model, to give
-anyone who possesses the object code either (1) a copy of the
-Corresponding Source for all the software in the product that is
-covered by this License, on a durable physical medium customarily used
-for software interchange, for a price no more than your reasonable
-cost of physically performing this conveying of source, or (2) access
-to copy the Corresponding Source from a network server at no charge.
-
-@item
-Convey individual copies of the object code with a copy of the written
-offer to provide the Corresponding Source. This alternative is
-allowed only occasionally and noncommercially, and only if you
-received the object code with such an offer, in accord with subsection
-6b.
-
-@item
-Convey the object code by offering access from a designated place
-(gratis or for a charge), and offer equivalent access to the
-Corresponding Source in the same way through the same place at no
-further charge. You need not require recipients to copy the
-Corresponding Source along with the object code. If the place to copy
-the object code is a network server, the Corresponding Source may be
-on a different server (operated by you or a third party) that supports
-equivalent copying facilities, provided you maintain clear directions
-next to the object code saying where to find the Corresponding Source.
-Regardless of what server hosts the Corresponding Source, you remain
-obligated to ensure that it is available for as long as needed to
-satisfy these requirements.
-
-@item
-Convey the object code using peer-to-peer transmission, provided you
-inform other peers where the object code and Corresponding Source of
-the work are being offered to the general public at no charge under
-subsection 6d.
-
-@end enumerate
-
-A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-A ``User Product'' is either (1) a ``consumer product'', which means any
-tangible personal property which is normally used for personal,
-family, or household purposes, or (2) anything designed or sold for
-incorporation into a dwelling. In determining whether a product is a
-consumer product, doubtful cases shall be resolved in favor of
-coverage. For a particular product received by a particular user,
-``normally used'' refers to a typical or common use of that class of
-product, regardless of the status of the particular user or of the way
-in which the particular user actually uses, or expects or is expected
-to use, the product. A product is a consumer product regardless of
-whether the product has substantial commercial, industrial or
-non-consumer uses, unless such uses represent the only significant
-mode of use of the product.
-
-``Installation Information'' for a User Product means any methods,
-procedures, authorization keys, or other information required to
-install and execute modified versions of a covered work in that User
-Product from a modified version of its Corresponding Source. The
-information must suffice to ensure that the continued functioning of
-the modified object code is in no case prevented or interfered with
-solely because modification has been made.
-
-If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information. But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or
-updates for a work that has been modified or installed by the
-recipient, or for the User Product in which it has been modified or
-installed. Access to a network may be denied when the modification
-itself materially and adversely affects the operation of the network
-or violates the rules and protocols for communication across the
-network.
-
-Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-@item Additional Terms.
-
-``Additional permissions'' are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law. If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it. (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.) You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders
-of that material) supplement the terms of this License with terms:
-
-@enumerate a
-@item
-Disclaiming warranty or limiting liability differently from the terms
-of sections 15 and 16 of this License; or
-
-@item
-Requiring preservation of specified reasonable legal notices or author
-attributions in that material or in the Appropriate Legal Notices
-displayed by works containing it; or
-
-@item
-Prohibiting misrepresentation of the origin of that material, or
-requiring that modified versions of such material be marked in
-reasonable ways as different from the original version; or
-
-@item
-Limiting the use for publicity purposes of names of licensors or
-authors of the material; or
-
-@item
-Declining to grant rights under trademark law for use of some trade
-names, trademarks, or service marks; or
-
-@item
-Requiring indemnification of licensors and authors of that material by
-anyone who conveys the material (or modified versions of it) with
-contractual assumptions of liability to the recipient, for any
-liability that these contractual assumptions directly impose on those
-licensors and authors.
-@end enumerate
-
-All other non-permissive additional terms are considered ``further
-restrictions'' within the meaning of section 10. If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term. If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions; the
-above requirements apply either way.
-
-@item Termination.
-
-You may not propagate or modify a covered work except as expressly
-provided under this License. Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-However, if you cease all violation of this License, then your license
-from a particular copyright holder is reinstated (a) provisionally,
-unless and until the copyright holder explicitly and finally
-terminates your license, and (b) permanently, if the copyright holder
-fails to notify you of the violation by some reasonable means prior to
-60 days after the cessation.
-
-Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License. If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-@item Acceptance Not Required for Having Copies.
-
-You are not required to accept this License in order to receive or run
-a copy of the Program. Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance. However,
-nothing other than this License grants you permission to propagate or
-modify any covered work. These actions infringe copyright if you do
-not accept this License. Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-@item Automatic Licensing of Downstream Recipients.
-
-Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License. You are not responsible
-for enforcing compliance by third parties with this License.
-
-An ``entity transaction'' is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations. If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License. For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-@item Patents.
-
-A ``contributor'' is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based. The
-work thus licensed is called the contributor's ``contributor version''.
-
-A contributor's ``essential patent claims'' are all patent claims owned
-or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version. For
-purposes of this definition, ``control'' includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-In the following three paragraphs, a ``patent license'' is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement). To ``grant'' such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients. ``Knowingly relying'' means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-A patent license is ``discriminatory'' if it does not include within the
-scope of its coverage, prohibits the exercise of, or is conditioned on
-the non-exercise of one or more of the rights that are specifically
-granted under this License. You may not convey a covered work if you
-are a party to an arrangement with a third party that is in the
-business of distributing software, under which you make payment to the
-third party based on the extent of your activity of conveying the
-work, and under which the third party grants, to any of the parties
-who would receive the covered work from you, a discriminatory patent
-license (a) in connection with copies of the covered work conveyed by
-you (or copies made from those copies), or (b) primarily for and in
-connection with specific products or compilations that contain the
-covered work, unless you entered into that arrangement, or that patent
-license was granted, prior to 28 March 2007.
-
-Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-@item No Surrender of Others' Freedom.
-
-If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot convey
-a covered work so as to satisfy simultaneously your obligations under
-this License and any other pertinent obligations, then as a
-consequence you may not convey it at all. For example, if you agree
-to terms that obligate you to collect a royalty for further conveying
-from those to whom you convey the Program, the only way you could
-satisfy both those terms and this License would be to refrain entirely
-from conveying the Program.
-
-@item Remote Network Interaction; Use with the GNU General Public License.
-
-Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users interacting
-with it remotely through a computer network (if your version supports such
-interaction) an opportunity to receive the Corresponding Source of your
-version by providing access to the Corresponding Source from a network
-server at no charge, through some standard or customary means of
-facilitating copying of software. This Corresponding Source shall include
-the Corresponding Source for any work covered by version 3 of the GNU
-General Public License that is incorporated pursuant to the following
-paragraph.
-
-Notwithstanding any other provision of this License, you have permission to
-link or combine any covered work with a work licensed under version 3 of
-the GNU General Public License into a single combined work, and to convey
-the resulting work. The terms of this License will continue to apply to
-the part which is the covered work, but the work with which it is combined
-will remain governed by version 3 of the GNU General Public License.
-
-@item Revised Versions of this License.
-
-The Free Software Foundation may publish revised and/or new versions
-of the GNU Affero General Public License from time to time. Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies that a certain numbered version of the GNU Affero General Public
-License ``or any later version'' applies to it, you have the option of
-following the terms and conditions either of that numbered version or
-of any later version published by the Free Software Foundation. If
-the Program does not specify a version number of the GNU Affero General
-Public License, you may choose any version ever published by the Free
-Software Foundation.
-
-If the Program specifies that a proxy can decide which future versions
-of the GNU Affero General Public License can be used, that proxy's public
-statement of acceptance of a version permanently authorizes you to
-choose that version for the Program.
-
-Later license versions may give you additional or different
-permissions. However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-@item Disclaimer of Warranty.
-
-THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM ``AS IS'' WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
-LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
-PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
-DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
-CORRECTION.
-
-@item Limitation of Liability.
-
-IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR
-CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT
-NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
-LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM
-TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
-PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-@item Interpretation of Sections 15 and 16.
-
-If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-@end enumerate
-
-@heading END OF TERMS AND CONDITIONS
-
-@heading How to Apply These Terms to Your New Programs
-
-If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these
-terms.
-
-To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the ``copyright'' line and a pointer to where the full notice is found.
-
-@smallexample
-@var{one line to give the program's name and a brief idea of what it does.}
-Copyright (C) @var{year} @var{name of author}
-
-This program is free software: you can redistribute it and/or modify
-it under the terms of the GNU Affero General Public License as published by
-the Free Software Foundation, either version 3 of the License, or (at
-your option) any later version.
-
-This program is distributed in the hope that it will be useful, but
-WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-Affero General Public License for more details.
-
-You should have received a copy of the GNU Affero General Public License
-along with this program. If not, see @url{http://www.gnu.org/licenses/}.
-@end smallexample
-
-Also add information on how to contact you by electronic and paper mail.
-
-If your software can interact with users remotely through a computer
-network, you should also make sure that it provides a way for users to
-get its source. For example, if your program is a web application, its
-interface could display a ``Source'' link that leads users to an archive
-of the code. There are many ways you could offer source, and different
-solutions will be better for different programs; see section 13 for the
-specific requirements.
-
-You should also get your employer (if you work as a programmer) or school,
-if any, to sign a ``copyright disclaimer'' for the program, if necessary.
-For more information on this, and how to apply and follow the GNU AGPL, see
-@url{http://www.gnu.org/licenses/}.
diff --git a/doc/arch-api.dot b/doc/arch-api.dot
deleted file mode 100644
index 1c30c06..0000000
--- a/doc/arch-api.dot
+++ /dev/null
@@ -1,27 +0,0 @@
-digraph G {
-
- user[label="Customer browser"];
- admin[label="Shop admin"];
- Backend[color="blue"];
- BackendPublic[color="blue", label="Backend\n(public interface)"];
- subgraph cluster_0 {
- Frontend;
- Backoffice;
- Backend;
- BackendPublic;
- DBMS;
- label="Shop server";
- }
- subgraph cluster_1 {
- Exchange;
- label="Exchange";
- }
- user->Frontend;
- admin->Backoffice;
- Frontend->Backend;
- Backoffice->Backend;
- BackendPublic->Backend;
- user->BackendPublic;
- Backend->DBMS;
- Backend->Exchange;
-}
diff --git a/doc/arch.dot b/doc/arch.dot
deleted file mode 100644
index acc9ed8..0000000
--- a/doc/arch.dot
+++ /dev/null
@@ -1,23 +0,0 @@
-digraph G {
-
- user[label="Customer browser"];
- admin[label="Shop admin"];
- Backend [color="blue"];
- subgraph cluster_0 {
- Frontend;
- Backoffice;
- Backend;
- DBMS;
- label="Shop server";
- }
- subgraph cluster_1 {
- Exchange;
- label="Exchange";
- }
- user->Frontend;
- admin->Backoffice;
- Frontend->Backend;
- Backoffice->Backend;
- Backend->DBMS;
- Backend->Exchange;
-}
diff --git a/doc/arch.txt b/doc/arch.txt
deleted file mode 100644
index 8b26415..0000000
--- a/doc/arch.txt
+++ /dev/null
@@ -1 +0,0 @@
-Missing diagram image
diff --git a/doc/configuration-format.texi b/doc/configuration-format.texi
deleted file mode 100644
index 6453ba6..0000000
--- a/doc/configuration-format.texi
+++ /dev/null
@@ -1,73 +0,0 @@
-@c This file is used both in the exchange and merchant
-@c manuals. Edits should be propagated to both Gits!
-
-@node Configuration format
-@section Configuration format
-@cindex configuration
-
-In Taler realm, any component obeys to the same pattern to get configuration
-values. According to this pattern, once the component has been installed, the
-installation deploys default values in
@cite{$@{prefix@}/share/taler/config.d/}, in
-@cite{.conf} files. In order to override these defaults, the user can write a
custom
-@cite{.conf} file and either pass it to the component at execution time, or
name it
-@cite{taler.conf} and place it under @cite{$HOME/.config/}.
-
-
-A config file is a text file containing @cite{sections}, and each section
contains
-its @cite{values}. The right format follows:
-
-@example
-[section1]
-value1 = string
-value2 = 23
-
-[section2]
-value21 = string
-value22 = /path22
-@end example
-
-Throughout any configuration file, it is possible to use @code{$}-prefixed
variables,
-like @code{$VAR}, especially when they represent filesystem paths.
-It is also possible to provide defaults values for those variables that are
unset,
-by using the following syntax: @code{$@{VAR:-default@}}.
-However, there are two ways a user can set @code{$}-prefixable variables:
-
-by defining them under a @code{[paths]} section, see example below,
-
-@example
-[paths]
-TALER_DEPLOYMENT_SHARED = $@{HOME@}/shared-data
-..
-[section-x]
-path-x = $@{TALER_DEPLOYMENT_SHARED@}/x
-@end example
-
-or by setting them in the environment:
-
-@example
-$ export VAR=/x
-@end example
-
-The configuration loader will give precedence to variables set under
@code{[path]},
-though.
-
-The utility @code{taler-config}, which gets installed along with the exchange,
serves
-to get and set configuration values without directly editing the @cite{.conf}.
-The option @code{-f} is particularly useful to resolve pathnames, when they use
-several levels of @code{$}-expanded variables. See @code{taler-config --help}.
-
-Note that, in this stage of development, the file
@code{$HOME/.config/taler.conf}
-can contain sections for @emph{all} the component. For example, both an
exchange and
-a bank can read values from it.
-
-The repository @code{git://taler.net/deployment} contains examples of
configuration
-file used in our demos. See under @code{deployment/config}.
-
-@cartouche
-@quotation Note
-Expectably, some components will not work just by using default values, as
their
-work is often interdependent. For example, a merchant needs to know an exchange
-URL, or a database name.
-@end quotation
-@end cartouche
-
diff --git a/doc/fdl-1.3.texi b/doc/fdl-1.3.texi
deleted file mode 100644
index 8805f1a..0000000
--- a/doc/fdl-1.3.texi
+++ /dev/null
@@ -1,506 +0,0 @@
-@c The GNU Free Documentation License.
-@center Version 1.3, 3 November 2008
-
-@c This file is intended to be included within another document,
-@c hence no sectioning command or @node.
-
-@display
-Copyright @copyright{} 2000, 2001, 2002, 2007, 2008 Free Software Foundation,
Inc.
-@uref{http://fsf.org/}
-
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-@end display
-
-@enumerate 0
-@item
-PREAMBLE
-
-The purpose of this License is to make a manual, textbook, or other
-functional and useful document @dfn{free} in the sense of freedom: to
-assure everyone the effective freedom to copy and redistribute it,
-with or without modifying it, either commercially or noncommercially.
-Secondarily, this License preserves for the author and publisher a way
-to get credit for their work, while not being considered responsible
-for modifications made by others.
-
-This License is a kind of ``copyleft'', which means that derivative
-works of the document must themselves be free in the same sense. It
-complements the GNU General Public License, which is a copyleft
-license designed for free software.
-
-We have designed this License in order to use it for manuals for free
-software, because free software needs free documentation: a free
-program should come with manuals providing the same freedoms that the
-software does. But this License is not limited to software manuals;
-it can be used for any textual work, regardless of subject matter or
-whether it is published as a printed book. We recommend this License
-principally for works whose purpose is instruction or reference.
-
-@item
-APPLICABILITY AND DEFINITIONS
-
-This License applies to any manual or other work, in any medium, that
-contains a notice placed by the copyright holder saying it can be
-distributed under the terms of this License. Such a notice grants a
-world-wide, royalty-free license, unlimited in duration, to use that
-work under the conditions stated herein. The ``Document'', below,
-refers to any such manual or work. Any member of the public is a
-licensee, and is addressed as ``you''. You accept the license if you
-copy, modify or distribute the work in a way requiring permission
-under copyright law.
-
-A ``Modified Version'' of the Document means any work containing the
-Document or a portion of it, either copied verbatim, or with
-modifications and/or translated into another language.
-
-A ``Secondary Section'' is a named appendix or a front-matter section
-of the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall
-subject (or to related matters) and contains nothing that could fall
-directly within that overall subject. (Thus, if the Document is in
-part a textbook of mathematics, a Secondary Section may not explain
-any mathematics.) The relationship could be a matter of historical
-connection with the subject or with related matters, or of legal,
-commercial, philosophical, ethical or political position regarding
-them.
-
-The ``Invariant Sections'' are certain Secondary Sections whose titles
-are designated, as being those of Invariant Sections, in the notice
-that says that the Document is released under this License. If a
-section does not fit the above definition of Secondary then it is not
-allowed to be designated as Invariant. The Document may contain zero
-Invariant Sections. If the Document does not identify any Invariant
-Sections then there are none.
-
-The ``Cover Texts'' are certain short passages of text that are listed,
-as Front-Cover Texts or Back-Cover Texts, in the notice that says that
-the Document is released under this License. A Front-Cover Text may
-be at most 5 words, and a Back-Cover Text may be at most 25 words.
-
-A ``Transparent'' copy of the Document means a machine-readable copy,
-represented in a format whose specification is available to the
-general public, that is suitable for revising the document
-straightforwardly with generic text editors or (for images composed of
-pixels) generic paint programs or (for drawings) some widely available
-drawing editor, and that is suitable for input to text formatters or
-for automatic translation to a variety of formats suitable for input
-to text formatters. A copy made in an otherwise Transparent file
-format whose markup, or absence of markup, has been arranged to thwart
-or discourage subsequent modification by readers is not Transparent.
-An image format is not Transparent if used for any substantial amount
-of text. A copy that is not ``Transparent'' is called ``Opaque''.
-
-Examples of suitable formats for Transparent copies include plain
-@sc{ascii} without markup, Texinfo input format, La@TeX{} input
-format, @acronym{SGML} or @acronym{XML} using a publicly available
-@acronym{DTD}, and standard-conforming simple @acronym{HTML},
-PostScript or @acronym{PDF} designed for human modification. Examples
-of transparent image formats include @acronym{PNG}, @acronym{XCF} and
-@acronym{JPG}. Opaque formats include proprietary formats that can be
-read and edited only by proprietary word processors, @acronym{SGML} or
-@acronym{XML} for which the @acronym{DTD} and/or processing tools are
-not generally available, and the machine-generated @acronym{HTML},
-PostScript or @acronym{PDF} produced by some word processors for
-output purposes only.
-
-The ``Title Page'' means, for a printed book, the title page itself,
-plus such following pages as are needed to hold, legibly, the material
-this License requires to appear in the title page. For works in
-formats which do not have any title page as such, ``Title Page'' means
-the text near the most prominent appearance of the work's title,
-preceding the beginning of the body of the text.
-
-The ``publisher'' means any person or entity that distributes copies
-of the Document to the public.
-
-A section ``Entitled XYZ'' means a named subunit of the Document whose
-title either is precisely XYZ or contains XYZ in parentheses following
-text that translates XYZ in another language. (Here XYZ stands for a
-specific section name mentioned below, such as ``Acknowledgements'',
-``Dedications'', ``Endorsements'', or ``History''.) To ``Preserve the Title''
-of such a section when you modify the Document means that it remains a
-section ``Entitled XYZ'' according to this definition.
-
-The Document may include Warranty Disclaimers next to the notice which
-states that this License applies to the Document. These Warranty
-Disclaimers are considered to be included by reference in this
-License, but only as regards disclaiming warranties: any other
-implication that these Warranty Disclaimers may have is void and has
-no effect on the meaning of this License.
-
-@item
-VERBATIM COPYING
-
-You may copy and distribute the Document in any medium, either
-commercially or noncommercially, provided that this License, the
-copyright notices, and the license notice saying this License applies
-to the Document are reproduced in all copies, and that you add no other
-conditions whatsoever to those of this License. You may not use
-technical measures to obstruct or control the reading or further
-copying of the copies you make or distribute. However, you may accept
-compensation in exchange for copies. If you distribute a large enough
-number of copies you must also follow the conditions in section 3.
-
-You may also lend copies, under the same conditions stated above, and
-you may publicly display copies.
-
-@item
-COPYING IN QUANTITY
-
-If you publish printed copies (or copies in media that commonly have
-printed covers) of the Document, numbering more than 100, and the
-Document's license notice requires Cover Texts, you must enclose the
-copies in covers that carry, clearly and legibly, all these Cover
-Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
-the back cover. Both covers must also clearly and legibly identify
-you as the publisher of these copies. The front cover must present
-the full title with all words of the title equally prominent and
-visible. You may add other material on the covers in addition.
-Copying with changes limited to the covers, as long as they preserve
-the title of the Document and satisfy these conditions, can be treated
-as verbatim copying in other respects.
-
-If the required texts for either cover are too voluminous to fit
-legibly, you should put the first ones listed (as many as fit
-reasonably) on the actual cover, and continue the rest onto adjacent
-pages.
-
-If you publish or distribute Opaque copies of the Document numbering
-more than 100, you must either include a machine-readable Transparent
-copy along with each Opaque copy, or state in or with each Opaque copy
-a computer-network location from which the general network-using
-public has access to download using public-standard network protocols
-a complete Transparent copy of the Document, free of added material.
-If you use the latter option, you must take reasonably prudent steps,
-when you begin distribution of Opaque copies in quantity, to ensure
-that this Transparent copy will remain thus accessible at the stated
-location until at least one year after the last time you distribute an
-Opaque copy (directly or through your agents or retailers) of that
-edition to the public.
-
-It is requested, but not required, that you contact the authors of the
-Document well before redistributing any large number of copies, to give
-them a chance to provide you with an updated version of the Document.
-
-@item
-MODIFICATIONS
-
-You may copy and distribute a Modified Version of the Document under
-the conditions of sections 2 and 3 above, provided that you release
-the Modified Version under precisely this License, with the Modified
-Version filling the role of the Document, thus licensing distribution
-and modification of the Modified Version to whoever possesses a copy
-of it. In addition, you must do these things in the Modified Version:
-
-@enumerate A
-@item
-Use in the Title Page (and on the covers, if any) a title distinct
-from that of the Document, and from those of previous versions
-(which should, if there were any, be listed in the History section
-of the Document). You may use the same title as a previous version
-if the original publisher of that version gives permission.
-
-@item
-List on the Title Page, as authors, one or more persons or entities
-responsible for authorship of the modifications in the Modified
-Version, together with at least five of the principal authors of the
-Document (all of its principal authors, if it has fewer than five),
-unless they release you from this requirement.
-
-@item
-State on the Title page the name of the publisher of the
-Modified Version, as the publisher.
-
-@item
-Preserve all the copyright notices of the Document.
-
-@item
-Add an appropriate copyright notice for your modifications
-adjacent to the other copyright notices.
-
-@item
-Include, immediately after the copyright notices, a license notice
-giving the public permission to use the Modified Version under the
-terms of this License, in the form shown in the Addendum below.
-
-@item
-Preserve in that license notice the full lists of Invariant Sections
-and required Cover Texts given in the Document's license notice.
-
-@item
-Include an unaltered copy of this License.
-
-@item
-Preserve the section Entitled ``History'', Preserve its Title, and add
-to it an item stating at least the title, year, new authors, and
-publisher of the Modified Version as given on the Title Page. If
-there is no section Entitled ``History'' in the Document, create one
-stating the title, year, authors, and publisher of the Document as
-given on its Title Page, then add an item describing the Modified
-Version as stated in the previous sentence.
-
-@item
-Preserve the network location, if any, given in the Document for
-public access to a Transparent copy of the Document, and likewise
-the network locations given in the Document for previous versions
-it was based on. These may be placed in the ``History'' section.
-You may omit a network location for a work that was published at
-least four years before the Document itself, or if the original
-publisher of the version it refers to gives permission.
-
-@item
-For any section Entitled ``Acknowledgements'' or ``Dedications'', Preserve
-the Title of the section, and preserve in the section all the
-substance and tone of each of the contributor acknowledgements and/or
-dedications given therein.
-
-@item
-Preserve all the Invariant Sections of the Document,
-unaltered in their text and in their titles. Section numbers
-or the equivalent are not considered part of the section titles.
-
-@item
-Delete any section Entitled ``Endorsements''. Such a section
-may not be included in the Modified Version.
-
-@item
-Do not retitle any existing section to be Entitled ``Endorsements'' or
-to conflict in title with any Invariant Section.
-
-@item
-Preserve any Warranty Disclaimers.
-@end enumerate
-
-If the Modified Version includes new front-matter sections or
-appendices that qualify as Secondary Sections and contain no material
-copied from the Document, you may at your option designate some or all
-of these sections as invariant. To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice.
-These titles must be distinct from any other section titles.
-
-You may add a section Entitled ``Endorsements'', provided it contains
-nothing but endorsements of your Modified Version by various
-parties---for example, statements of peer review or that the text has
-been approved by an organization as the authoritative definition of a
-standard.
-
-You may add a passage of up to five words as a Front-Cover Text, and a
-passage of up to 25 words as a Back-Cover Text, to the end of the list
-of Cover Texts in the Modified Version. Only one passage of
-Front-Cover Text and one of Back-Cover Text may be added by (or
-through arrangements made by) any one entity. If the Document already
-includes a cover text for the same cover, previously added by you or
-by arrangement made by the same entity you are acting on behalf of,
-you may not add another; but you may replace the old one, on explicit
-permission from the previous publisher that added the old one.
-
-The author(s) and publisher(s) of the Document do not by this License
-give permission to use their names for publicity for or to assert or
-imply endorsement of any Modified Version.
-
-@item
-COMBINING DOCUMENTS
-
-You may combine the Document with other documents released under this
-License, under the terms defined in section 4 above for modified
-versions, provided that you include in the combination all of the
-Invariant Sections of all of the original documents, unmodified, and
-list them all as Invariant Sections of your combined work in its
-license notice, and that you preserve all their Warranty Disclaimers.
-
-The combined work need only contain one copy of this License, and
-multiple identical Invariant Sections may be replaced with a single
-copy. If there are multiple Invariant Sections with the same name but
-different contents, make the title of each such section unique by
-adding at the end of it, in parentheses, the name of the original
-author or publisher of that section if known, or else a unique number.
-Make the same adjustment to the section titles in the list of
-Invariant Sections in the license notice of the combined work.
-
-In the combination, you must combine any sections Entitled ``History''
-in the various original documents, forming one section Entitled
-``History''; likewise combine any sections Entitled ``Acknowledgements'',
-and any sections Entitled ``Dedications''. You must delete all
-sections Entitled ``Endorsements.''
-
-@item
-COLLECTIONS OF DOCUMENTS
-
-You may make a collection consisting of the Document and other documents
-released under this License, and replace the individual copies of this
-License in the various documents with a single copy that is included in
-the collection, provided that you follow the rules of this License for
-verbatim copying of each of the documents in all other respects.
-
-You may extract a single document from such a collection, and distribute
-it individually under this License, provided you insert a copy of this
-License into the extracted document, and follow this License in all
-other respects regarding verbatim copying of that document.
-
-@item
-AGGREGATION WITH INDEPENDENT WORKS
-
-A compilation of the Document or its derivatives with other separate
-and independent documents or works, in or on a volume of a storage or
-distribution medium, is called an ``aggregate'' if the copyright
-resulting from the compilation is not used to limit the legal rights
-of the compilation's users beyond what the individual works permit.
-When the Document is included in an aggregate, this License does not
-apply to the other works in the aggregate which are not themselves
-derivative works of the Document.
-
-If the Cover Text requirement of section 3 is applicable to these
-copies of the Document, then if the Document is less than one half of
-the entire aggregate, the Document's Cover Texts may be placed on
-covers that bracket the Document within the aggregate, or the
-electronic equivalent of covers if the Document is in electronic form.
-Otherwise they must appear on printed covers that bracket the whole
-aggregate.
-
-@item
-TRANSLATION
-
-Translation is considered a kind of modification, so you may
-distribute translations of the Document under the terms of section 4.
-Replacing Invariant Sections with translations requires special
-permission from their copyright holders, but you may include
-translations of some or all Invariant Sections in addition to the
-original versions of these Invariant Sections. You may include a
-translation of this License, and all the license notices in the
-Document, and any Warranty Disclaimers, provided that you also include
-the original English version of this License and the original versions
-of those notices and disclaimers. In case of a disagreement between
-the translation and the original version of this License or a notice
-or disclaimer, the original version will prevail.
-
-If a section in the Document is Entitled ``Acknowledgements'',
-``Dedications'', or ``History'', the requirement (section 4) to Preserve
-its Title (section 1) will typically require changing the actual
-title.
-
-@item
-TERMINATION
-
-You may not copy, modify, sublicense, or distribute the Document
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense, or distribute it is void, and
-will automatically terminate your rights under this License.
-
-However, if you cease all violation of this License, then your license
-from a particular copyright holder is reinstated (a) provisionally,
-unless and until the copyright holder explicitly and finally
-terminates your license, and (b) permanently, if the copyright holder
-fails to notify you of the violation by some reasonable means prior to
-60 days after the cessation.
-
-Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License. If your rights have been terminated and not permanently
-reinstated, receipt of a copy of some or all of the same material does
-not give you any rights to use it.
-
-@item
-FUTURE REVISIONS OF THIS LICENSE
-
-The Free Software Foundation may publish new, revised versions
-of the GNU Free Documentation License from time to time. Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns. See
-@uref{http://www.gnu.org/copyleft/}.
-
-Each version of the License is given a distinguishing version number.
-If the Document specifies that a particular numbered version of this
-License ``or any later version'' applies to it, you have the option of
-following the terms and conditions either of that specified version or
-of any later version that has been published (not as a draft) by the
-Free Software Foundation. If the Document does not specify a version
-number of this License, you may choose any version ever published (not
-as a draft) by the Free Software Foundation. If the Document
-specifies that a proxy can decide which future versions of this
-License can be used, that proxy's public statement of acceptance of a
-version permanently authorizes you to choose that version for the
-Document.
-
-@item
-RELICENSING
-
-``Massive Multiauthor Collaboration Site'' (or ``MMC Site'') means any
-World Wide Web server that publishes copyrightable works and also
-provides prominent facilities for anybody to edit those works. A
-public wiki that anybody can edit is an example of such a server. A
-``Massive Multiauthor Collaboration'' (or ``MMC'') contained in the
-site means any set of copyrightable works thus published on the MMC
-site.
-
-``CC-BY-SA'' means the Creative Commons Attribution-Share Alike 3.0
-license published by Creative Commons Corporation, a not-for-profit
-corporation with a principal place of business in San Francisco,
-California, as well as future copyleft versions of that license
-published by that same organization.
-
-``Incorporate'' means to publish or republish a Document, in whole or
-in part, as part of another Document.
-
-An MMC is ``eligible for relicensing'' if it is licensed under this
-License, and if all works that were first published under this License
-somewhere other than this MMC, and subsequently incorporated in whole
-or in part into the MMC, (1) had no cover texts or invariant sections,
-and (2) were thus incorporated prior to November 1, 2008.
-
-The operator of an MMC Site may republish an MMC contained in the site
-under CC-BY-SA on the same site at any time before August 1, 2009,
-provided the MMC is eligible for relicensing.
-
-@end enumerate
-
-@page
-@heading ADDENDUM: How to use this License for your documents
-
-To use this License in a document you have written, include a copy of
-the License in the document and put the following copyright and
-license notices just after the title page:
-
-@smallexample
-@group
- Copyright (C) @var{year} @var{your name}.
- Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.3
- or any later version published by the Free Software Foundation;
- with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
- Texts. A copy of the license is included in the section entitled ``GNU
- Free Documentation License''.
-@end group
-@end smallexample
-
-If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the ``with@dots{}Texts.'' line with this:
-
-@smallexample
-@group
- with the Invariant Sections being @var{list their titles}, with
- the Front-Cover Texts being @var{list}, and with the Back-Cover Texts
- being @var{list}.
-@end group
-@end smallexample
-
-If you have Invariant Sections without Cover Texts, or some other
-combination of the three, merge those two alternatives to suit the
-situation.
-
-If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License,
-to permit their use in free software.
-
-@c Local Variables:
-@c ispell-local-pdict: "ispell-dict"
-@c End:
-
diff --git a/doc/highlight.pack.js b/doc/highlight.pack.js
deleted file mode 100644
index b2f9ff2..0000000
--- a/doc/highlight.pack.js
+++ /dev/null
@@ -1,2 +0,0 @@
-/*! highlight.js v9.12.0 | BSD3 License | git.io/hljslicense */
-!function(e){var n="object"==typeof window&&window||"object"==typeof
self&&self;"undefined"!=typeof
exports?e(exports):n&&(n.hljs=e({}),"function"==typeof
define&&define.amd&&define([],function(){return n.hljs}))}(function(e){function
n(e){return
e.replace(/&/g,"&").replace(/</g,"<").replace(/>/g,">")}function
t(e){return e.nodeName.toLowerCase()}function r(e,n){var t=e&&e.exec(n);return
t&&0===t.index}function a(e){return k.test(e)}function i(e){var
n,t,r,i,o=e.className+" ";i [...]
\ No newline at end of file
diff --git a/doc/lgpl.texi b/doc/lgpl.texi
deleted file mode 100644
index ab03d6c..0000000
--- a/doc/lgpl.texi
+++ /dev/null
@@ -1,549 +0,0 @@
-@c The GNU Lesser General Public License.
-@center Version 2.1, February 1999
-
-@c This file is intended to be included within another document,
-@c hence no sectioning command or @node.
-
-@display
-Copyright @copyright{} 1991, 1999 Free Software Foundation, Inc.
-51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
-
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-
-[This is the first released version of the Lesser GPL. It also counts
-as the successor of the GNU Library Public License, version 2, hence the
-version number 2.1.]
-@end display
-
-@subheading Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-Licenses are intended to guarantee your freedom to share and change
-free software---to make sure the software is free for all its users.
-
- This license, the Lesser General Public License, applies to some
-specially designated software---typically libraries---of the Free
-Software Foundation and other authors who decide to use it. You can use
-it too, but we suggest you first think carefully about whether this
-license or the ordinary General Public License is the better strategy to
-use in any particular case, based on the explanations below.
-
- When we speak of free software, we are referring to freedom of use,
-not price. Our General Public Licenses are designed to make sure that
-you have the freedom to distribute copies of free software (and charge
-for this service if you wish); that you receive source code or can get
-it if you want it; that you can change the software and use pieces of it
-in new free programs; and that you are informed that you can do these
-things.
-
- To protect your rights, we need to make restrictions that forbid
-distributors to deny you these rights or to ask you to surrender these
-rights. These restrictions translate to certain responsibilities for
-you if you distribute copies of the library or if you modify it.
-
- For example, if you distribute copies of the library, whether gratis
-or for a fee, you must give the recipients all the rights that we gave
-you. You must make sure that they, too, receive or can get the source
-code. If you link other code with the library, you must provide
-complete object files to the recipients, so that they can relink them
-with the library after making changes to the library and recompiling
-it. And you must show them these terms so they know their rights.
-
- We protect your rights with a two-step method: (1) we copyright the
-library, and (2) we offer you this license, which gives you legal
-permission to copy, distribute and/or modify the library.
-
- To protect each distributor, we want to make it very clear that
-there is no warranty for the free library. Also, if the library is
-modified by someone else and passed on, the recipients should know
-that what they have is not the original version, so that the original
-author's reputation will not be affected by problems that might be
-introduced by others.
-
- Finally, software patents pose a constant threat to the existence of
-any free program. We wish to make sure that a company cannot
-effectively restrict the users of a free program by obtaining a
-restrictive license from a patent holder. Therefore, we insist that
-any patent license obtained for a version of the library must be
-consistent with the full freedom of use specified in this license.
-
- Most GNU software, including some libraries, is covered by the
-ordinary GNU General Public License. This license, the GNU Lesser
-General Public License, applies to certain designated libraries, and
-is quite different from the ordinary General Public License. We use
-this license for certain libraries in order to permit linking those
-libraries into non-free programs.
-
- When a program is linked with a library, whether statically or using
-a shared library, the combination of the two is legally speaking a
-combined work, a derivative of the original library. The ordinary
-General Public License therefore permits such linking only if the
-entire combination fits its criteria of freedom. The Lesser General
-Public License permits more lax criteria for linking other code with
-the library.
-
- We call this license the @dfn{Lesser} General Public License because it
-does @emph{Less} to protect the user's freedom than the ordinary General
-Public License. It also provides other free software developers Less
-of an advantage over competing non-free programs. These disadvantages
-are the reason we use the ordinary General Public License for many
-libraries. However, the Lesser license provides advantages in certain
-special circumstances.
-
- For example, on rare occasions, there may be a special need to
-encourage the widest possible use of a certain library, so that it becomes
-a de-facto standard. To achieve this, non-free programs must be
-allowed to use the library. A more frequent case is that a free
-library does the same job as widely used non-free libraries. In this
-case, there is little to gain by limiting the free library to free
-software only, so we use the Lesser General Public License.
-
- In other cases, permission to use a particular library in non-free
-programs enables a greater number of people to use a large body of
-free software. For example, permission to use the GNU C Library in
-non-free programs enables many more people to use the whole GNU
-operating system, as well as its variant, the GNU/Linux operating
-system.
-
- Although the Lesser General Public License is Less protective of the
-users' freedom, it does ensure that the user of a program that is
-linked with the Library has the freedom and the wherewithal to run
-that program using a modified version of the Library.
-
- The precise terms and conditions for copying, distribution and
-modification follow. Pay close attention to the difference between a
-``work based on the library'' and a ``work that uses the library''. The
-former contains code derived from the library, whereas the latter must
-be combined with the library in order to run.
-
-@subheading TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-@enumerate 0
-@item
-This License Agreement applies to any software library or other program
-which contains a notice placed by the copyright holder or other
-authorized party saying it may be distributed under the terms of this
-Lesser General Public License (also called ``this License''). Each
-licensee is addressed as ``you''.
-
- A ``library'' means a collection of software functions and/or data
-prepared so as to be conveniently linked with application programs
-(which use some of those functions and data) to form executables.
-
- The ``Library'', below, refers to any such software library or work
-which has been distributed under these terms. A ``work based on the
-Library'' means either the Library or any derivative work under
-copyright law: that is to say, a work containing the Library or a
-portion of it, either verbatim or with modifications and/or translated
-straightforwardly into another language. (Hereinafter, translation is
-included without limitation in the term ``modification''.)
-
- ``Source code'' for a work means the preferred form of the work for
-making modifications to it. For a library, complete source code means
-all the source code for all modules it contains, plus any associated
-interface definition files, plus the scripts used to control compilation
-and installation of the library.
-
- Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running a program using the Library is not restricted, and output from
-such a program is covered only if its contents constitute a work based
-on the Library (independent of the use of the Library in a tool for
-writing it). Whether that is true depends on what the Library does
-and what the program that uses the Library does.
-
-@item
-You may copy and distribute verbatim copies of the Library's
-complete source code as you receive it, in any medium, provided that
-you conspicuously and appropriately publish on each copy an
-appropriate copyright notice and disclaimer of warranty; keep intact
-all the notices that refer to this License and to the absence of any
-warranty; and distribute a copy of this License along with the
-Library.
-
- You may charge a fee for the physical act of transferring a copy,
-and you may at your option offer warranty protection in exchange for a
-fee.
-
-@item
-You may modify your copy or copies of the Library or any portion
-of it, thus forming a work based on the Library, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-@enumerate a
-@item
-The modified work must itself be a software library.
-
-@item
-You must cause the files modified to carry prominent notices
-stating that you changed the files and the date of any change.
-
-@item
-You must cause the whole of the work to be licensed at no
-charge to all third parties under the terms of this License.
-
-@item
-If a facility in the modified Library refers to a function or a
-table of data to be supplied by an application program that uses
-the facility, other than as an argument passed when the facility
-is invoked, then you must make a good faith effort to ensure that,
-in the event an application does not supply such function or
-table, the facility still operates, and performs whatever part of
-its purpose remains meaningful.
-
-(For example, a function in a library to compute square roots has
-a purpose that is entirely well-defined independent of the
-application. Therefore, Subsection 2d requires that any
-application-supplied function or table used by this function must
-be optional: if the application does not supply it, the square
-root function must still compute square roots.)
-@end enumerate
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Library,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Library, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote
-it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Library.
-
-In addition, mere aggregation of another work not based on the Library
-with the Library (or with a work based on the Library) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
-@item
-You may opt to apply the terms of the ordinary GNU General Public
-License instead of this License to a given copy of the Library. To do
-this, you must alter all the notices that refer to this License, so
-that they refer to the ordinary GNU General Public License, version 2,
-instead of to this License. (If a newer version than version 2 of the
-ordinary GNU General Public License has appeared, then you can specify
-that version instead if you wish.) Do not make any other change in
-these notices.
-
- Once this change is made in a given copy, it is irreversible for
-that copy, so the ordinary GNU General Public License applies to all
-subsequent copies and derivative works made from that copy.
-
- This option is useful when you wish to copy part of the code of
-the Library into a program that is not a library.
-
-@item
-You may copy and distribute the Library (or a portion or
-derivative of it, under Section 2) in object code or executable form
-under the terms of Sections 1 and 2 above provided that you accompany
-it with the complete corresponding machine-readable source code, which
-must be distributed under the terms of Sections 1 and 2 above on a
-medium customarily used for software interchange.
-
- If distribution of object code is made by offering access to copy
-from a designated place, then offering equivalent access to copy the
-source code from the same place satisfies the requirement to
-distribute the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-@item
-A program that contains no derivative of any portion of the
-Library, but is designed to work with the Library by being compiled or
-linked with it, is called a ``work that uses the Library''. Such a
-work, in isolation, is not a derivative work of the Library, and
-therefore falls outside the scope of this License.
-
- However, linking a ``work that uses the Library'' with the Library
-creates an executable that is a derivative of the Library (because it
-contains portions of the Library), rather than a ``work that uses the
-library''. The executable is therefore covered by this License.
-Section 6 states terms for distribution of such executables.
-
- When a ``work that uses the Library'' uses material from a header file
-that is part of the Library, the object code for the work may be a
-derivative work of the Library even though the source code is not.
-Whether this is true is especially significant if the work can be
-linked without the Library, or if the work is itself a library. The
-threshold for this to be true is not precisely defined by law.
-
- If such an object file uses only numerical parameters, data
-structure layouts and accessors, and small macros and small inline
-functions (ten lines or less in length), then the use of the object
-file is unrestricted, regardless of whether it is legally a derivative
-work. (Executables containing this object code plus portions of the
-Library will still fall under Section 6.)
-
- Otherwise, if the work is a derivative of the Library, you may
-distribute the object code for the work under the terms of Section 6.
-Any executables containing that work also fall under Section 6,
-whether or not they are linked directly with the Library itself.
-
-@item
-As an exception to the Sections above, you may also combine or
-link a ``work that uses the Library'' with the Library to produce a
-work containing portions of the Library, and distribute that work
-under terms of your choice, provided that the terms permit
-modification of the work for the customer's own use and reverse
-engineering for debugging such modifications.
-
- You must give prominent notice with each copy of the work that the
-Library is used in it and that the Library and its use are covered by
-this License. You must supply a copy of this License. If the work
-during execution displays copyright notices, you must include the
-copyright notice for the Library among them, as well as a reference
-directing the user to the copy of this License. Also, you must do one
-of these things:
-
-@enumerate a
-@item
-Accompany the work with the complete corresponding
-machine-readable source code for the Library including whatever
-changes were used in the work (which must be distributed under
-Sections 1 and 2 above); and, if the work is an executable linked
-with the Library, with the complete machine-readable ``work that
-uses the Library'', as object code and/or source code, so that the
-user can modify the Library and then relink to produce a modified
-executable containing the modified Library. (It is understood
-that the user who changes the contents of definitions files in the
-Library will not necessarily be able to recompile the application
-to use the modified definitions.)
-
-@item
-Use a suitable shared library mechanism for linking with the Library. A
-suitable mechanism is one that (1) uses at run time a copy of the
-library already present on the user's computer system, rather than
-copying library functions into the executable, and (2) will operate
-properly with a modified version of the library, if the user installs
-one, as long as the modified version is interface-compatible with the
-version that the work was made with.
-
-@item
-Accompany the work with a written offer, valid for at
-least three years, to give the same user the materials
-specified in Subsection 6a, above, for a charge no more
-than the cost of performing this distribution.
-
-@item
-If distribution of the work is made by offering access to copy
-from a designated place, offer equivalent access to copy the above
-specified materials from the same place.
-
-@item
-Verify that the user has already received a copy of these
-materials or that you have already sent this user a copy.
-@end enumerate
-
- For an executable, the required form of the ``work that uses the
-Library'' must include any data and utility programs needed for
-reproducing the executable from it. However, as a special exception,
-the materials to be distributed need not include anything that is
-normally distributed (in either source or binary form) with the major
-components (compiler, kernel, and so on) of the operating system on
-which the executable runs, unless that component itself accompanies the
-executable.
-
- It may happen that this requirement contradicts the license
-restrictions of other proprietary libraries that do not normally
-accompany the operating system. Such a contradiction means you cannot
-use both them and the Library together in an executable that you
-distribute.
-
-@item
-You may place library facilities that are a work based on the
-Library side-by-side in a single library together with other library
-facilities not covered by this License, and distribute such a combined
-library, provided that the separate distribution of the work based on
-the Library and of the other library facilities is otherwise
-permitted, and provided that you do these two things:
-
-@enumerate a
-@item
-Accompany the combined library with a copy of the same work
-based on the Library, uncombined with any other library
-facilities. This must be distributed under the terms of the
-Sections above.
-
-@item
-Give prominent notice with the combined library of the fact
-that part of it is a work based on the Library, and explaining
-where to find the accompanying uncombined form of the same work.
-@end enumerate
-
-@item
-You may not copy, modify, sublicense, link with, or distribute
-the Library except as expressly provided under this License. Any
-attempt otherwise to copy, modify, sublicense, link with, or
-distribute the Library is void, and will automatically terminate your
-rights under this License. However, parties who have received copies,
-or rights, from you under this License will not have their licenses
-terminated so long as such parties remain in full compliance.
-
-@item
-You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Library or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Library (or any work based on the
-Library), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Library or works based on it.
-
-@item
-Each time you redistribute the Library (or any work based on the
-Library), the recipient automatically receives a license from the
-original licensor to copy, distribute, link with or modify the Library
-subject to these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties with
-this License.
-
-@item
-If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Library at all. For example, if a patent
-license would not permit royalty-free redistribution of the Library by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Library.
-
-If any portion of this section is held invalid or unenforceable under any
-particular circumstance, the balance of the section is intended to apply,
-and the section as a whole is intended to apply in other circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-@item
-If the distribution and/or use of the Library is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Library under this License may add
-an explicit geographical distribution limitation excluding those countries,
-so that distribution is permitted only in or among countries not thus
-excluded. In such case, this License incorporates the limitation as if
-written in the body of this License.
-
-@item
-The Free Software Foundation may publish revised and/or new
-versions of the Lesser General Public License from time to time.
-Such new versions will be similar in spirit to the present version,
-but may differ in detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Library
-specifies a version number of this License which applies to it and
-``any later version'', you have the option of following the terms and
-conditions either of that version or of any later version published by
-the Free Software Foundation. If the Library does not specify a
-license version number, you may choose any version ever published by
-the Free Software Foundation.
-
-@item
-If you wish to incorporate parts of the Library into other free
-programs whose distribution conditions are incompatible with these,
-write to the author to ask for permission. For software which is
-copyrighted by the Free Software Foundation, write to the Free
-Software Foundation; we sometimes make exceptions for this. Our
-decision will be guided by the two goals of preserving the free status
-of all derivatives of our free software and of promoting the sharing
-and reuse of software generally.
-
-@center @b{NO WARRANTY}
-
-@item
-BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
-WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
-EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
-OTHER PARTIES PROVIDE THE LIBRARY ``AS IS'' WITHOUT WARRANTY OF ANY
-KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
-LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
-THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-@item
-IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
-WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
-AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
-FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
-CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
-LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
-RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
-FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
-SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
-DAMAGES.
-@end enumerate
-
-@subheading END OF TERMS AND CONDITIONS
-
-@page
-@subheading How to Apply These Terms to Your New Libraries
-
- If you develop a new library, and you want it to be of the greatest
-possible use to the public, we recommend making it free software that
-everyone can redistribute and change. You can do so by permitting
-redistribution under these terms (or, alternatively, under the terms of the
-ordinary General Public License).
-
- To apply these terms, attach the following notices to the library. It is
-safest to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least the
-``copyright'' line and a pointer to where the full notice is found.
-
-@smallexample
-@var{one line to give the library's name and an idea of what it does.}
-Copyright (C) @var{year} @var{name of author}
-
-This library is free software; you can redistribute it and/or modify it
-under the terms of the GNU Lesser General Public License as published by
-the Free Software Foundation; either version 2.1 of the License, or (at
-your option) any later version.
-
-This library is distributed in the hope that it will be useful, but
-WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-Lesser General Public License for more details.
-
-You should have received a copy of the GNU Lesser General Public
-License along with this library; if not, write to the Free Software
-Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
-USA.
-@end smallexample
-
-Also add information on how to contact you by electronic and paper mail.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a ``copyright disclaimer'' for the library, if
-necessary. Here is a sample; alter the names:
-
-@smallexample
-Yoyodyne, Inc., hereby disclaims all copyright interest in the library
-`Frob' (a library for tweaking knobs) written by James Random Hacker.
-
-@var{signature of Ty Coon}, 1 April 1990
-Ty Coon, President of Vice
-@end smallexample
-
-That's all there is to it!
diff --git a/doc/manual.texi b/doc/manual.texi
deleted file mode 100644
index b37ad61..0000000
--- a/doc/manual.texi
+++ /dev/null
@@ -1,1296 +0,0 @@
-\input texinfo @c -*-texinfo-*-
-@c %**start of header
-@c Too generic, should be renamed to avoid system conflicts.
-@c probably: manual.info -> taler-merchant.info
-@setfilename manual.info
-@include version-manual.texi
-@settitle The GNU Taler merchant backend operator tutorial @value{VERSION}
-
-@include syntax.texi
-
-@c Define a new index for options.
-@defcodeindex op
-@c Combine everything into one index (arbitrarily chosen to be the
-@c concept index).
-@syncodeindex op cp
-@c %**end of header
-
-@copying
-This manual is for the GNU Taler merchant backend (version @value{VERSION},
@value{UPDATED}),
-
-Copyright @copyright{} 2016, 2017, 2019 Taler Systems SA
-
-@quotation
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.3 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
-Texts. A copy of the license is included in the section entitled
-``GNU Free Documentation License''.
-@end quotation
-@end copying
-@c If your manual is published on paper by the FSF, it should include
-@c The standard FSF Front-Cover and Back-Cover Texts, as given in
-@c maintain.texi.
-@c
-@c Titlepage
-@c
-@titlepage
-@title The GNU Taler merchant backend operator tutorial
-@subtitle Version @value{VERSION}
-@subtitle @value{UPDATED}
-@author Marcello Stanisci (@email{marcello.stanisci@@inria.fr})
-@author Christian Grothoff (@email{christian.grothoff@@inria.fr})
-@page
-@vskip 0pt plus 1filll
-@insertcopying
-@end titlepage
-
-@summarycontents
-@contents
-
-@ifnottex
-@node Top
-@top The GNU Taler manual for Web shops
-@insertcopying
-@end ifnottex
-
-@menu
-* Introduction:: Whom this manual is addressed to
-* Installation:: Installing the Merchant backend
-* Configuration:: How to set up the Merchant backend
-* Testing:: How to test the installed Merchant backend
-* Advanced topics:: Detailed solutions to specific issues
-
-
-Appendices
-
-* GNU-LGPL:: The GNU Lesser General Public License says how you
- can use the code of libtalermerchant.so in your
own projects.
-* GNU Affero GPL:: The Affero GNU General Public License says how you
- can copy and share the Taler merchant backend.
-* GNU-FDL:: The GNU Free Documentation License says how you
- can copy and share the documentation of GNU Taler.
-
-Indices
-
-* Concept Index:: Index of concepts and programs.
-
-@detailmenu
- --- The Detailed Node Listing ---
-
-Introduction
-
-* About GNU Taler::
-* About this manual::
-* Architecture overview::
-
-Installation
-
-* Installing Taler using Docker::
-* Generic instructions::
-* Installing Taler on Debian GNU/Linux::
-
-Configuration
-
-* Backend options::
-* Sample backend configuration::
-* Launching the backend::
-
-Testing
-
-Advanced topics
-
-* Configuration format::
-* Using taler-config::
-* Merchant key management::
-* SEPA configuration::
-* Tipping visitors::
-* Generate payments::
-
-@end detailmenu
-@end menu
-
-
-@node Introduction
-@chapter Introduction
-
-@menu
-* About GNU Taler::
-* About this manual::
-* Architecture overview::
-@end menu
-
-@node About GNU Taler
-@section About GNU Taler
-
-GNU Taler is an open protocol for an electronic payment system with a
-free software reference implementation. GNU Taler offers secure, fast
-and easy payment processing using well understood cryptographic
-techniques. GNU Taler allows customers to remain anonymous, while
-ensuring that merchants can be held accountable by governments.
-Hence, GNU Taler is compatible with anti-money-laundering (AML) and
-know-your-customer (KYC) regulation, as well as data protection
-regulation (such as GDPR).
-
-GNU Taler is not yet production-ready, after following this manual
-you will have a backend that can process payments in ``KUDOS'', but
-not regular currencies. This is not so much because of limitations
-in the backend, but because we are not aware of a Taler exchange
-operator offering regular currencies today.
-
-@node About this manual
-@section About this manual
-
-This tutorial targets system administrators who want to
-install a GNU Taler merchant @emph{backend}.
-
-We expect some moderate familiarity with the compilation and installation
-of free software packages. An understanding of cryptography
-is not required.
-
-This first chapter of the tutorial will give a brief overview of
-the overall Taler architecture, describing the environment in which
-the Taler backend operates.
-The second chapter then explains how to install the software,
-including key dependencies. The third chapter will explain how to
-configure the backend, including in particular the configuration of the
-bank account details of the merchant.
-
-@c The fouth chapter will explain how to test that the setup worked correctly.
-
-The last chapter gives some additional information about advanced topics
-which will be useful for system administrators but are not necessary for
-operating a basic backend.
-
-@node Architecture overview
-@section Architecture overview
-
-@cindex crypto-currency
-@cindex KUDOS
-Taler is a pure payment system, not a new crypto-currency. As such, it
-operates in a traditional banking context. In particular, this means
-that in order to receive funds via Taler, the merchant must have a
-regular bank account, and payments can be executed in ordinary
-currencies such as USD or EUR. For testing purposes, Taler uses a
-special currency ``KUDOS'' and includes its own special bank.
-
-The Taler software stack for a merchant consists of four main components:
-
-@itemize
-@cindex frontend
-@item A frontend which interacts with the customer's browser. The
- frontend enables the customer to build a shopping cart and place
- an order. Upon payment, it triggers the respective business logic
- to satisfy the order. This component is not included with Taler,
- but rather assumed to exist at the merchant. This manual
- describes how to integrate Taler with Web shop frontends.
-@cindex back office
-@item A back office application that enables the shop operators to
- view customer orders, match them to financial transfers, and possibly
- approve refunds if an order cannot be satisfied. This component is
- again not included with Taler, but rather assumed to exist at the
- merchant. This manual will describe how to integrate such a component
- to handle payments managed by Taler.
-@cindex backend
-@item A Taler-specific payment backend which makes it easy for the
- frontend to process financial transactions with Taler. The
- next two chapters will describe how to install and configure
- this backend.
-@cindex DBMS
-@cindex Postgres
-@item A DBMS which stores the transaction history for the Taler backend.
- For now, the GNU Taler reference implemenation only supports Postgres,
- but the code could be easily extended to support another DBMS.
-@end itemize
-
-The following image illustrates the various interactions of these
-key components:
-
-@center @image{arch, 3in}
-
-@cindex RESTful
-Basically, the backend provides the cryptographic protocol support,
-stores Taler-specific financial information in a DBMS and communicates
-with the GNU Taler exchange over the Internet. The frontend accesses
-the backend via a RESTful API. As a result, the frontend never has to
-directly communicate with the exchange, and also does not deal with
-sensitive data. In particular, the merchant's signing keys and bank
-account information is encapsulated within the Taler backend.
-
-
-@node Installation
-@chapter Installation
-
-@menu
-* Installing Taler using Docker::
-* Generic instructions::
-* Installing Taler on Debian GNU/Linux::
-@c * Installing Taler with GNU Guix:: Installing Taler with GNU Guix
-@c * Installing Taler on Arch Linux:: Installing Taler on Arch Linux
-@c * Installing Taler on Windows:: Installing Taler on Windows
-@c * Installing Taler on OS X:: Installing Taler on OS X
-@end menu
-
-This chapter describes how to install the GNU Taler merchant backend.
-
-@node Installing Taler using Docker
-@section Installing Taler using Docker
-
-This section provides instructions for the merchant backend
-installation using `Docker`.
-
-For security reasons, we run Docker against a VirtualBox instance,
-so the @code{docker} command should connect to a @code{docker-machine}
-instance that uses the VirtualBox driver.
-
-Therefore, the needed tools are: ``docker``, ``docker-machine``, and
-``docker-compose``. Please refer to Docker's official
-@footnote{https://docs.docker.com/}documentation in order
-to get those components installed, as that is not in this manual's scope.
-
-Before starting to build the merchant's image, make sure a
-``docker-machine`` instance is up and running.
-
-Because all of the Docker source file are kept in our ``deployment``
-repository, we start by checking out the
-@code{git://taler.net/deployment} codebase:
-
-@smallexample
-$ git clone git://taler.net/deployment
-@end smallexample
-
-Now we actually build the merchant's image. From the same
-directory as above:
-
-@smallexample
-$ cd deployment/docker/merchant/
-$ docker-compose build
-@end smallexample
-
-If everything worked as expected, the merchant is ready to be
-launched. From the same directory as the previous step:
-
-@smallexample
-# Recall: the docker-machine should be up and running.
-$ docker-compose up
-@end smallexample
-
-You should see some live logging from all the involved containers.
-At this stage of development, you should also ignore some (harmless)
-error message from postresql about already existing roles and databases.
-
-To test if everything worked as expected, it suffices to issue a
-simple request to the merchant, as:
-
-@smallexample
-$ curl http://$(docker-machine ip)/
-# A greeting message should be returned by the merchant.
-@end smallexample
-
-
-@node Generic instructions
-@section Generic instructions
-
-This section provides generic instructions for the merchant backend
-installation independent of any particular operating system.
-Operating system specific instructions are provided in the following
-sections. You should follow the operating system specific
-instructions if those are available, and only consult the generic
-instructions if no system-specific instructions are provided for your
-specific operating system.
-
-@menu
-* Installation of dependencies::
-* Installing libgnunetutil::
-* Installing the GNU Taler exchange::
-* Installing the GNU Taler merchant backend::
-@end menu
-
-@node Installation of dependencies
-@subsection Installation of dependencies
-
-The following packages need to be installed before we can compile the
-backend:
-
-@itemize
-@item autoconf >= 2.69
-@item automake >= 1.14
-@item libtool >= 2.4
-@item autopoint >= 0.19
-@item libltdl >= 2.4
-@item libunistring >= 0.9.3
-@item libcurl >= 7.26 (or libgnurl >= 7.26)
-@item GNU libmicrohttpd >= 0.9.39
-@item GNU libgcrypt >= 1.6
-@item libjansson >= 2.7
-@item Postgres >= 9.4, including libpq
-@item libgnunetutil (from Git)
-@item GNU Taler exchange (from Git)
-@end itemize
-
-Except for the last two, these are available in most GNU/Linux
-distributions and should just be installed using the respective
-package manager.
-
-The following sections will provide detailed instructions for
-installing the libgnunetutil and GNU Taler exchange dependencies.
-
-@node Installing libgnunetutil
-@subsection Installing libgnunetutil
-
-@cindex GNUnet
-Before you install libgnunetutil, you must download and install the
-dependencies mentioned in the previous section, otherwise the build
-may succeed but fail to export some of the tooling required by Taler.
-
-To download and install libgnunetutil, proceed as follows:
-
-@example
-$ git clone https://gnunet.org/git/gnunet/
-$ cd gnunet/
-$ ./bootstrap
-$ ./configure [--prefix=GNUNETPFX]
-$ # Each dependency can be fetched from non standard locations via
-$ # the '--with-<LIBNAME>' option. See './configure --help'.
-$ make
-# make install
-@end example
-
-If you did not specify a prefix, GNUnet will install to
-@code{/usr/local}, which requires you to run the last step as
-@code{root}.
-
-@node Installing the GNU Taler exchange
-@subsection Installing the GNU Taler exchange
-
-@cindex exchange
-After installing GNUnet, you can download and install
-the exchange as follows:
-
-@example
-$ git clone git://taler.net/exchange
-$ cd exchange
-$ ./bootstrap
-$ ./configure [--prefix=EXCHANGEPFX] \
- [--with-gnunet=GNUNETPFX]
-$ # Each dependency can be fetched from non standard locations via
-$ # the '--with-<LIBNAME>' option. See './configure --help'.
-$ make
-# make install
-@end example
-
-If you did not specify a prefix, the exchange will install to
-@code{/usr/local}, which requires you to run the last step as
-@code{root}. Note that you have to specify
-@code{--with-gnunet=/usr/local} if you installed GNUnet to
-@code{/usr/local} in the previous step.
-
-@node Installing the GNU Taler merchant backend
-@subsection Installing the GNU Taler merchant backend
-
-@cindex backend
-The following steps assume all dependencies are installed.
-
-Use the following commands to download and install the
-merchant backend:
-
-@example
-$ git clone git://taler.net/merchant
-$ cd merchant
-$ ./bootstrap
-$ ./configure [--prefix=PFX] \
- [--with-gnunet=GNUNETPFX] \
- [--with-exchange=EXCHANGEPFX]
-$ # Each dependency can be fetched from non standard locations via
-$ # the '--with-<LIBNAME>' option. See './configure --help'.
-$ make
-$ make install
-@end example
-
-Note that you have to specify @code{--with-exchange=/usr/local} and/or
-@code{--with-exchange=/usr/local} if you installed the exchange and/or
-GNUnet to @code{/usr/local} in the previous steps.
-
-@c @node Installing Taler with GNU Guix
-@c @section Installing Taler with GNU Guix
-
-@c This section has not yet been written.
-
-
-
-
-@node Installing Taler on Debian GNU/Linux
-@section Installing Taler on Debian GNU/Linux
-
-@cindex Wheezy
-@cindex Debian
-Debian wheezy is too old and lacks most of the packages required.
-
-On Debian jessie, only GNU libmicrohttpd needs to be compiled from
-source. To install dependencies on Debian jesse, run the following
-commands:
-
-@example
-# apt-get install \
- autoconf \
- automake \
- autopoint \
- libtool \
- libltdl-dev \
- libunistring-dev \
- libcurl4-gnutls-dev \
- libgcrypt20-dev \
- libjansson-dev \
- libpq-dev \
- postgresql-9.4
-# wget https://ftp.gnu.org/gnu/libmicrohttpd/libmicrohttpd-latest.tar.gz
-# wget https://ftp.gnu.org/gnu/libmicrohttpd/libmicrohttpd-latest.tar.gz.sig
-# gpg -v libmicrohttpd-latest.tar.gz # Should show signed by 939E6BE1E29FC3CC
-# tar xf libmicrohttpd-latest.tar.gz
-# cd libmicrohttpd-0*
-# ./configure
-# make install
-@end example
-
-For more recent versions of Debian, you should instead run:
-
-@example
-# apt-get install \
- autoconf \
- automake \
- autopoint \
- libtool \
- libltdl-dev \
- libunistring-dev \
- libcurl4-gnutls-dev \
- libgcrypt20-dev \
- libjansson-dev \
- libpq-dev \
- postgresql-9.5 \
- libmicrohttpd-dev
-@end example
-
-For the rest of the installation, follow the
-generic installation instructions starting with the installation of
-libgnunetutil. Note that if you used the Debian wheezy instructions
-above, you need to pass
-@code{--with-microhttpd=/usr/local/} to all @code{configure} invocations.
-
-
-
-@c @node Installing Taler on Arch Linux
-@c @section Installing Taler on Arch Linux
-
-@c This section has not yet been written.
-
-
-@c @node Installing Taler on Windows
-@c @section Installing Taler on Windows
-
-@c This section has not yet been written.
-
-
-@c @node Installing Taler on OS X
-@c @section Installing Taler on OS X
-
-@c This section has not yet been written.
-
-
-@node Configuration
-@chapter How to configure the merchant's backend
-
-@cindex taler-config
-@cindex taler.conf
-The installation already provides reasonable defaults for most of the
-configuration options. However, some must be provided, in particular
-the database account and bank account that the backend should use. By
-default, the file @code{$HOME/.config/taler.conf} is where the Web
-shop administrator specifies configuration values that augment or
-override the defaults. The format of the configuration file is
-the well-known INI file format. You can edit the file by hand, or
-use the @code{taler-config} commands given as examples.
-For more information on @code{taler-config}, @pxref{Using taler-config}.
-
-@menu
-* Backend options::
-* Sample backend configuration::
-* Launching the backend::
-@end menu
-
-@node Backend options
-@section Backend options
-
-The following table describes the options that commonly need to
-be modified.
-Here, the notation @code{[$section]/$option} denotes the option
-@code{$option} under the section @code{[$section]} in the
-configuration file.
-
-
-@table @asis
-
-@item Service address
-The following option sets the transport layer address used by the merchant
backend:
-
-@cindex UNIX domain socket
-@cindex TCP
-@example
-[MERCHANT]/SERVE = TCP | UNIX
-@end example
-
-If given,
-@itemize
-@item @code{TCP}, then we need to set the TCP port in @code{[MERCHANT]/PORT}
-@item @code{UNIX}, then we need to set the unix domain socket path and mode in
-@code{[MERCHANT]/UNIXPATH} and @code{[MERCHANT]/UNIXPATH_MODE}. The latter
takes
-the usual permission mask given as a number, e.g. 660 for user/group
read-write access.
-@end itemize
-
-The frontend can then connect to the backend over HTTP using the specified
address.
-If frontend and backend run within the same operating system, the use of
-a UNIX domain socket is recommended to avoid accidentally exposing the backend
-to the network.
-
-@c FIXME: we should offer an option to bind the TCP socket to a particular IP
address (#4752)
-
-@cindex port
-To run the Taler backend on TCP port 8888, use:
-@example
-$ taler-config -s MERCHANT -o SERVE -V TCP
-$ taler-config -s MERCHANT -o PORT -V 8888
-@end example
-
-
-@item Currency
-Which currency the Web shop deals in, i.e. ``EUR'' or ``USD'', is specified
using the option
-
-@cindex currency
-@cindex KUDOS
-@example
-[TALER]/CURRENCY
-@end example
-
-For testing purposes, the currency MUST match ``KUDOS'' so that tests will work
-with the Taler demonstration exchange at
@url{https://exchange.demo.taler.net/}:
-
-@example
-$ taler-config -s TALER -o CURRENCY -V KUDOS
-@end example
-
-
-@item Database
-@cindex DBMS
-In principle is possible for the backend to support different DBMSs.
-The option
-
-@example
-[MERCHANT]/DB
-@end example
-
-specifies which DBMS is to be used. However, currently only the value
"postgres" is supported. This is also
-the default.
-
-In addition to selecting the DBMS software, the backend requires DBMS-specific
options to access the database.
-
-For postgres, you need to provide:
-
-@example
-[merchantdb-postgres]/config
-@end example
-@cindex Postgres
-
-This option specifies a postgres access path using the format
-@code{postgres:///$DBNAME}, where @code{$DBNAME} is the name of the Postgres
-database you want to use. Suppose @code{$USER} is the name of the
-user who will run the backend process. Then, you need to first run
-
-@example
-$ sudu -u postgres createuser -d $USER
-@end example
-
-as the Postgres database administrator (usually @code{postgres}) to
-grant @code{$USER} the ability to create new databases. Next, you
-should as @code{$USER} run:
-
-@example
-$ createdb $DBNAME
-@end example
-
-to create the backend's database. Here, @code{$DBNAME} must match the
database name
-given in the configuration file.
-
-To configure the Taler backend to use this database, run:
-@example
-$ taler-config -s MERCHANTDB-postgres -o CONFIG \
- -V postgres:///$DBNAME
-@end example
-
-
-@item Exchange
-@cindex exchange
-To add an exchange to the list of trusted payment service providers,
-you create a section with a name that starts with ``exchange-''.
-In that section, the following options need to be configured:
-
-@itemize
-
-@item
-The ``url'' option specifies the exchange's base URL. For example,
-to use the Taler demonstrator use:
-
-@example
-$ taler-config -s EXCHANGE-demo -o URL \
- -V https://exchange.demo.taler.net/
-@end example
-
-@item
-@cindex master key
-The ``master_key'' option specifies the exchange's master public key in base32
encoding.
-For the Taler demonstrator, use:
-
-@example
-$ taler-config -s EXCHANGE-demo -o master_key \
- -V CQQZ9DY3MZ1ARMN5K1VKDETS04Y2QCKMMCFHZSWJWWVN82BTTH00
-@end example
-
-Note that multiple exchanges can be added to the system by using different
-tokens in place of @code{demo} in the example above. Note that all
-of the exchanges must use the same currency. If you need to support
-multiple currencies, you need to configure a backend per currency.
-
-@end itemize
-
-@c FIXME: In the future, we need to describe specifying auditors here.
-@c @item Auditors
-
-
-@item Instances
-@cindex instance
-The backend allows the user to run multiple instances of shops with
-distinct business entities against a single backend. Each instance
-uses its own bank accounts and key for signing contracts. It is
-mandatory to configure a "default" instance.
-
-@itemize
-
-@item
-The ``KEYFILE'' option specifies the file containing the instance's
-private signing key. For example, use:
-
-@example
-$ taler-config -s INSTANCE-default -o KEYFILE \
- -V '$@{TALER_CONFIG_HOME@}/merchant/instace/default.key'
-@end example
-
-@item
-The ``NAME'' option specifies a human-readable name for the instance.
-For example, use:
-
-@example
-$ taler-config -s INSTANCE-default -o NAME \
- -V 'Kudos Inc.'
-@end example
-
-
-@item
-The optional ``TIP_EXCHANGE'' and ``TIP_EXCHANGE_PRIV_FILENAME''
-options are discussed in @cite{Tipping visitors}
-@end itemize
-
-
-
-@item Accounts
-@cindex wire format
-In order to receive payments, the merchant backend needs to communicate bank
-account details to the exchange. For this, the configuration must
-include one or more sections named ``ACCOUNT-name'' where @code{name} can be
-replaced by some human-readable word identifying the account. For
-each section, the following options should be provided:
-
-
-@itemize
-@item
-The ``URL'' option specifies a @code{payto://}-URL for the account of
-the merchant. For example, use:
-
-@example
-$ taler-config -s ACCOUNT-bank -o NAME \
- -V 'payto://x-taler-bank/bank.demo.taler.net/4'
-@end example
-
-@item
-The ``WIRE_RESPONSE'' option specifies where Taler should store the
-(salted) JSON encoding of the wire account. The file given will be
-created if it does not exist. For example, use:
-
-@example
-$ taler-config -s ACCOUNT-bank -o WIRE_RESPONSE \
- -V '@{$TALER_CONFIG_HOME@}/merchant/bank.json'
-@end example
-
-
-@item
-The ``PLUGIN'' option specifies which wire plugin should be used for
-this account. The plugin must support the wire method used by the
-URL. For example, use:
-
-@example
-$ taler-config -s ACCOUNT-bank -o PLUGIN \
- -V taler_bank
-@end example
-
-@item
-For each @code{instance} that should use this account, you should set
-@code{HONOR_instance} and @code{ACTIVE_instance} to YES. The first
-option will cause the instance to accept payments to the account (for
-existing contracts), while the second will cause the backend to
-include the account as a possible option for new contracts.
-
-For example, use:
-
-@example
-$ taler-config -s ACCOUNT-bank -o HONOR_default \
- -V YES
-$ taler-config -s ACCOUNT-bank -o ACTIVE_default \
- -V YES
-@end example
-
-to use ``account-bank'' for the ``default'' instance.
-
-@end itemize
-
-Depending on which PLUGIN you configured, you may additionally specfiy
-authentication options to enable the plugin to use the account.
-
-For example, with @code{taler_bank} plugin, use:
-
-@example
-$ taler-config -s ACCOUNT-bank -o TALER_BANK_AUTH_METHOD \
- -V basic
-$ taler-config -s ACCOUNT-bank -o USERNAME \
- -V user42
-$ taler-config -s ACCOUNT-bank -o PASSWORD \
- -V pass42
-@end example
-
-
-
-@c Document EBICS here once supported.
-
-Note that additional instances can be specified using different tokens
-in the section name instead of @code{default}.
-
-@end table
-
-@node Sample backend configuration
-@section Sample backend configuration
-
-@cindex configuration
-The following is an example for a complete backend configuration:
-
-@smallexample
-[TALER]
-CURRENCY = KUDOS
-
-[MERCHANT]
-SERVE = TCP
-PORT = 8888
-DATABASE = postgres
-
-[MERCHANTDB-postgres]
-CONFIG = postgres:///donations
-
-[INSTANCE-default]
-KEYFILE = $DATADIR/key.priv
-NAME = "Kudos Inc."
-
-[ACCOUNT-bank]
-URL = payto://x-taler-bank/bank.demo.taler.net/4
-WIRE_RESPONSE = $DATADIR/bank.json
-PLUGIN = taler_bank
-HONOR_default = YES
-ACTIVE_default = YES
-TALER_BANK_AUTH_METHOD = basic
-USERNAME = my_user
-PASSWORD = 1234pass
-
-[EXCHANGE-trusted]
-URL = https://exchange.demo.taler.net/
-MASTER_KEY = CQQZ9DY3MZ1ARMN5K1VKDETS04Y2QCKMMCFHZSWJWWVN82BTTH00
-CURRENCY = KUDOS
-
-@end smallexample
-
-
-Given the above configuration, the backend will use a database named
-@code{donations} within Postgres.
-
-The backend will deposit the coins it receives to the exchange at
-@url{https://exchange.demo.taler.net/}, which has the master key @*
-"CQQZ9DY3MZ1ARMN5K1VKDETS04Y2QCKMMCFHZSWJWWVN82BTTH00".
-
-Please note that @code{doc/config.sh} will walk you through all
-configuration steps, showing how to invoke @code{taler-config}
-for each of them.
-
-@node Launching the backend
-@section Launching the backend
-
-@cindex backend
-@cindex taler-merchant-httpd
-Assuming you have configured everything correctly, you can launch the
-merchant backend using:
-
-@example
-$ taler-merchant-httpd
-@end example
-
-When launched for the first time, this command will print a message
-about generating your private key. If everything worked as expected,
-the command
-
-@example
-$ curl http://localhost:8888/
-@end example
-
-should return the message
-
-@smallexample
-Hello, I'm a merchant's Taler backend. This HTTP server is not for humans.
-@end smallexample
-
-Please note that your backend is right now likely globally
-reachable. Production systems should be configured to bind
-to a UNIX domain socket or properly restrict access to the
-port.
-
-
-@node Testing
-@chapter Testing
-
-The tool @code{taler-merchant-generate-payments} can be used to test
-the merchant backend installation. It implements all the payment's steps
-in a programmatically way, relying on the backend you give it as input.
-Note that this tool gets installed along all the
-merchant backend's binaries.
-
-This tool gets configured by a config file, that must have the following
-layout:
-
-@example
-[PAYMENTS-GENERATOR]
-
-# The exchange used during the test: make sure the merchant backend
-# being tested accpets this exchange.
-# If the sysadmin wants, she can also install a local exchange
-# and test against it.
-EXCHANGE = https://exchange.demo.taler.net/
-
-# This value must indicate some URL where the backend
-# to be tested is listening; it doesn't have to be the
-# "official" one, though.
-MERCHANT = http://localbackend/
-
-# This value is used when the tool tries to withdraw coins,
-# and must match the bank used by the exchange. If the test is
-# done against the exchange at https://exchange.demo.taler.net/,
-# then this value can be "https://bank.demo.taler.net/";.
-BANK = https://bank.demo.taler.net/
-
-# The merchant instance in charge of serving the payment.
-# Make sure this instance has a bank account at the same bank
-# indicated by the 'bank' option above.
-INSTANCE = default
-
-# The currency used during the test. Must match the one used
-# by merchant backend and exchange.
-CURRENCY = KUDOS
-@end example
-@c FIXME: the last option should be removed and [taler]/CURRENCY used instead!
-
-Run the test in the following way:
-
-@example
-$ taler-merchant-generate-payments [-c config] [-e EURL] [-m MURL]
-@end example
-
-The argument @code{config} given to @code{-c} points to the configuration
-file and is optional -- @code{~/.config/taler.conf} will be checked by
-default.
-By default, the tool forks two processes: one for the merchant backend,
-and one for the exchange.
-The option @code{-e} (@code{-m}) avoids any exchange (merchant backend)
-fork, and just runs the generator against the exchange (merchant backend)
-running at @code{EURL} (@code{MURL}).
-
-Please NOTE that the generator contains @emph{hardcoded} values, as for
-deposit fees of the coins it uses.
-In order to work against the used exchange, those values MUST match the
-ones used by the exchange.
-
-The following example shows how the generator "sets" a deposit fee
-of EUR:0.01 for the 5 EURO coin.
-
-@example
-// from <merchant_repository>/src/sample/generate_payments.c
-@{ .oc = OC_PAY,
- .label = "deposit-simple",
- .expected_response_code = MHD_HTTP_OK,
- .details.pay.contract_ref = "create-proposal-1",
- .details.pay.coin_ref = "withdraw-coin-1",
- .details.pay.amount_with_fee = concat_amount (currency, "5"),
- .details.pay.amount_without_fee = concat_amount (currency, "4.99") @},
-@end example
-
-The logic calculates the deposit fee according to the subtraction:
-@code{amount_with_fee - amount_without_fee}.
-
-The following example shows a 5 EURO coin configuration - needed by the
-used exchange - which is compatible with the hardcoded example above.
-
-@example
-[COIN_eur_5]
-value = EUR:5
-duration_overlap = 5 minutes
-duration_withdraw = 7 days
-duration_spend = 2 years
-duration_legal = 3 years
-fee_withdraw = EUR:0.00
-fee_deposit = EUR:0.01 # important bit
-fee_refresh = EUR:0.00
-fee_refund = EUR:0.00
-rsa_keysize = 1024
-@end example
-
-If the command terminates with no errors, then the merchant backend
-is correctly installed.
-
-After this operation is done, the merchant database will have some dummy
-data in it, so it may be convenient to clean all the tables; to this
-purpose, issue the following command:
-
-@example
-$ taler-merchant-dbinit -r
-@end example
-
-
-@node Advanced topics
-@chapter Advanced topics
-
-@menu
-* Configuration format:: Configuration file format
-* Using taler-config:: Introduction to the taler-config tool
-* Merchant key management:: Managing the merchant's cryptographic keys
-* SEPA configuration:: Configuring a SEPA bank account
-* Tipping visitors:: Giving money to Web site visitors with Taler
-* Generate payments:: Generate fake payments for testing purposes
-@end menu
-
-@include configuration-format.texi
-@include taler-config.texi
-
-
-@node Merchant key management
-@section Merchant key management
-@cindex merchant key
-@cindex KEYFILE
-
-The option ``KEYFILE'' in the section ``INSTANCE-default''
-specifies the path to the instance's private key. You do not need to
-create a key manually, the backend will generate it automatically if
-it is missing. While generally unnecessary, it is possible to display
-the corresponding public key using the @code{gnunet-ecc} command-line
-tool:
-
-@example
-$ gnunet-ecc -p \
- $(taler-config -f -s INSTANCE-default \
- -o KEYFILE)
-@end example
-
-@c Add more on how to add that key to X.509 CSRs once we can do that.
-
-@node SEPA configuration
-@section Using the SEPA wire transfer method
-@cindex SEPA
-@cindex EBICS
-
-The following is a sample configuration for the SEPA wire transfer
-method:@footnote{Supporting SEPA is still
-work in progress; the backend will accept this configuration, but the
-exchange will not work with SEPA today.}.
-
-Then, to configure the EBICS backend for SEPA payments in EUR,
-the following configuration
-options need to be set:
-
-@example
-$ taler-config -s TALER -o CURRENCY -V EUR
-$ taler-config -s ACCOUNT-e -o PLUGIN -V ebics
-$ taler-config -s ACCOUNT-e -o URL \
- -V payto://sepa/XY00111122223333444455556666
-$ taler-config -s ACCOUNT-e -o WIRE_RESPONSE
- -V '$@{DATADIR@}/b.json'
-@end example
-
-Please note that you will also have to configure an exchange and/or
-auditors that support SEPA. However, we cannot explain how to do this
-yet as such entities do not yet exist. Once such entities do exist,
-we expect future versions of the Taler backend to ship with
-pre-configured exchanges and auditors for common denominations.
-
-
-@node Tipping visitors
-@section Tipping visitors
-@cindex tipping
-
-Taler can also be used to tip Web site visitors. For example, you may
-be running an online survey, and you want to reward those people that have
-dutifully completed the survey. If they have installed a Taler wallet,
-you can provide them with a tip for their deeds. This section describes
-how to setup the Taler merchant backend for tipping.
-
-There are four basic steps that must happen to tip a visitor.
-
-@menu
-* Configure a reserve and exchange for tipping::
-* Fund the reserve::
-* Authorize a tip::
-* Picking up of the tip::
-@end menu
-
-@node Configure a reserve and exchange for tipping
-@subsection Configure a reserve and exchange for tipping
-@cindex gnunet-ecc
-@cindex reserve key
-
-@c TODO: We should probably create a tool that automates the
-@c configuration process and simply outputs the wire transfer
-@c subject of the reserve.
-
-To tip users, you first need to create a reserve. A reserve is a pool
-of money held in escrow at the Taler exchange. This is the source of
-the funds for the tips. Tipping will fail (resulting in disappointed
-visitors) if you do not have enough funds in your reserve!
-
-First, we configure the backend. You need to enable tipping for each
-instance separately, or you can use an instance only for tipping. To
-configure the ``default'' instance for tipping, use the following
-configuration:
-
-@example
-[INSTANCE-default]
-# this is NOT the tip.priv
-KEYFILE = signing_key.priv
-# replace the URL with the URL of the exchange you will use
-TIP_EXCHANGE = https://exchange:443/
-# here put the path to the file created with "gnunet-ecc -g1 tip.priv"
-TIP_RESERVE_PRIV_FILENAME = tip.priv
-@end example
-
-Note that the KEYFILE option should have already been present for
-the instance. It has nothing to do with the ``tip.priv'' file we
-created above, and you should probably use a different file here.
-
-Instead of manually editing the configuration, you could also run:
-
-@example
-$ taler-config -s INSTANCE-default \
- -o TIP_RESERVE_PRIV_FILENAME \
- -V tip.priv
-$ taler-config -s INSTANCE-default \
- -o TIP_EXCHANGE \
- -V https://exchange:443/
-@end example
-
-
-Next, to create the @code{TIP_RESERVE_PRIV_FILENAME} file, use:
-
-@example
-$ gnunet-ecc -g 1 \
- $(taler-config -f -s INSTANCE-default \
- -o TIP-RESERVE_PRIV_FILENAME)
-@end example
-
-This will create a file with the private key that will be used to
-identify the reserve. You need to do this once for each instance that
-is configured to tip.
-
-
-Now you can (re)start the backend with the new configuration.
-
-@node Fund the reserve
-@subsection Fund the reserve
-@cindex reserve
-@cindex close
-
-To fund the reserve, you must first extract the public key
-from ``tip.priv'':
-
-@example
-$ gnunet-ecc --print-public-key \
- $(taler-config -f -s INSTANCE-default \
- -o TIP-RESERVE_PRIV_FILENAME)
-@end example
-
-In our example, the output for the public key is:
-
-@example
-QPE24X8PBX3BZ6E7GQ5VAVHV32FWTTCADR0TRQ183MSSJD2CHNEG
-@end example
-
-You now need to make a wire transfer to the exchange's bank account
-using the public key as the wire transfer subject. The exchange's
-bank account details can be found in JSON format at
-``https://exchange:443//wire/METHOD'' where METHOD is the respective
-wire method (i.e. ``sepa''). Depending on the exchange's operator,
-you may also be able to find the bank details in a human-readable
-format on the main page of the exchange.
-
-Make your wire transfer and (optionally) check at
-``https://exchange:443/reserve/status/reserve_pub=QPE24X...''
-whether your transfer has arrived at the exchange.
-@c FIXME: we should create a nicer tool to do this check!
-
-Once the funds have arrived, you can start to use the reserve
-for tipping.
-
-Note that an exchange will typically close a reserve after four weeks,
-wiring all remaining funds back to the sender's account. Thus, you
-should plan to wire funds corresponding to a campaign of about two
-weeks to the exchange initially. If your campaign runs longer, you
-should wire further funds to the reserve every other week to prevent
-it from expiring.
-
-@node Authorize a tip
-@subsection Authorize a tip
-
-When your frontend has reached the point where a client is supposed
-to receive a tip, it needs to first authorize the tip. For this,
-the frontend must use the ``/tip-authorize'' API of the backend.
-To authorize a tip, the frontend has to provide the following information
-in the body of the POST request:
-
-@itemize @bullet
-@item The amount of the tip
-
-@item The justification (only used internally for the back-office)
-
-@item The URL where the wallet should navigate next after the tip was processed
-
-@item The tip-pickup URL (see next section)
-@end itemize
-
-In response to this request, the backend will return a tip token, an
-expiration time and the exchange URL.
-The expiration time will indicate how long the tip is valid (when the
-reserve expires). The tip token is an opaque string that contains all
-the information needed by the wallet to process the tip. The
-frontend must send this tip token to the browser in a
-special ``402 Payment Required'' response inside
-the @code{X-Taler-Tip} header.
-
-The frontend should handle errors returned by the backend, such
-as missconfigured instances or a lack of remaining funds for tipping.
-
-@node Picking up of the tip
-@subsection Picking up of the tip
-
-The wallet will POST a JSON object to the shop's ``/tip-pickup'' handler.
-The frontend must then forward this request to the backend. The response
-generated by the backend can then be forwarded directly to the wallet.
-
-@node Generate payments
-@section Generate payments
-@cindex testing database
-
-The merchant codebase offers the @code{taler-merchant-benchmark} tool
-to populate the database with fake payments. This tool is in charge of
-starting a merchant, exchange, and bank processes, and provide them all
-the input to accomplish payments. Note that each component will use its
-own configuration (as they would do in production).
-
-The tool takes all of the values it needs from the command line, with
-some of them being mandatory. Among those, we have:
-
-@itemize
-@item @code{--currency=K} Use currency @emph{K}, for example to craft coins to
withdraw.
-@item @code{--bank-url=URL} Assume that the bank is serving under the base URL
@emph{URL}.
-This option is only actually used by the tool to check if the bank was well
launched.
-@item @code{--merchant-url=URL} Reach the merchant through @emph{URL}, for
downloading
-contracts and sending payments.
-@end itemize
-
-The tool then comes with two operation modes: @emph{ordinary},
-and @emph{corner}. The first just executes normal payments,
-meaning that it uses the default instance and make sure that
-all payments get aggregated. The second gives the chance to
-leave some payments unaggregated, and also to use merchant
-instances other than the default (which is, actually, the one
-used by default by the tool).
-
-Note: the abilty of driving the aggregation policy is useful
-for testing the backoffice facility.
-
-Any subcommand is also equipped with the canonical @code{--help}
-option, so feel free to issue the following command in order to
-explore all the possibilities. For example:
-
-@smallexample
-$ taler-merchant-benchmark corner --help
-@end smallexample
-
-will show all the options offered by the @emph{corner} mode.
-Among the most interesting, there are:
-
-@itemize
-@item @code{--two-coins=TC} This option instructs the tool to perform @emph{TC}
-many payments that use two coins, because normally only one coin is spent per
payment.
-@item @code{--unaggregated-number=UN} This option instructs the tool to
perform @emph{UN}
-(one coin) payments that will be left unaggregated.
-@item @code{--alt-instance=AI} This option instructs the tool to perform
payments
-using the merchant instance @emph{AI} (instead of the @emph{default} instance)
-@end itemize
-
-As for the @code{ordinary} subcommand, it is worth explaining the
-following options:
-
-@itemize
-@item @code{--payments-number=PN} Instructs the tool to perform @emph{PN}
payments.
-@item @code{--tracks-number=TN} Instructs the tool to perform @emph{TN}
tracking operations.
-Note that the @b{total} amount of operations will be two times @emph{TN},
since "one"
-tracking operation accounts for @code{/track/transaction} and
@code{/track/transfer}.
-This command should only be used to see if the operation ends without
problems, as
-no actual measurement of performance is provided (despite of the 'benchmark'
work used
-in the tool's name).
-@end itemize
-
-@c **********************************************************
-@c ******************* Appendices *************************
-@c **********************************************************
-
-@node GNU-LGPL
-@unnumbered GNU-LGPL
-@cindex license
-@cindex LGPL
-@include lgpl.texi
-
-@node GNU Affero GPL
-@unnumbered GNU Affero GPL
-@cindex license
-@cindex Affero GPL
-@include agpl.texi
-
-@node GNU-FDL
-@unnumbered GNU-FDL
-@cindex license
-@cindex GNU Free Documentation License
-@include fdl-1.3.texi
-
-@node Concept Index
-@unnumbered Concept Index
-
-@printindex cp
-
-@bye
diff --git a/doc/merchant-api-curl.texi b/doc/merchant-api-curl.texi
deleted file mode 100644
index 32e9628..0000000
--- a/doc/merchant-api-curl.texi
+++ /dev/null
@@ -1,13 +0,0 @@
-\input texinfo @c -*-texinfo-*-
-@c %**start of header
-@setfilename merchant-api-curl.info
-@include version-merchant-api-curl.texi
-@include syntax.texi
-@settitle The GNU Taler Merchant API Tutorial @value{VERSION} for sh/cURL
-
-@set LANG_CURL 1
-@set LANGNAME sh/cURL
-
-@include merchant-api.content.texi
-
-@bye
diff --git a/doc/merchant-api-php.texi b/doc/merchant-api-php.texi
deleted file mode 100644
index 749351f..0000000
--- a/doc/merchant-api-php.texi
+++ /dev/null
@@ -1,13 +0,0 @@
-\input texinfo @c -*-texinfo-*-
-@c %**start of header
-@setfilename merchant-api-php.info
-@include version-merchant-api-php.texi
-@include syntax.texi
-@settitle The GNU Taler Merchant API Tutorial @value{VERSION} for PHP
-
-@set LANG_PHP 1
-@set LANGNAME PHP
-
-@include merchant-api.content.texi
-
-@bye
diff --git a/doc/merchant-api-python.texi b/doc/merchant-api-python.texi
deleted file mode 100644
index 7623a60..0000000
--- a/doc/merchant-api-python.texi
+++ /dev/null
@@ -1,13 +0,0 @@
-\input texinfo @c -*-texinfo-*-
-@c %**start of header
-@setfilename merchant-api-python.info
-@include version-merchant-api-python.texi
-@include syntax.texi
-@settitle The GNU Taler Merchant API Tutorial @value{VERSION} for Python
-
-@set LANG_PYTHON 1
-@set LANGNAME Python
-
-@include merchant-api.content.texi
-
-@bye
diff --git a/doc/merchant-api.content.texi b/doc/merchant-api.content.texi
deleted file mode 100644
index 4ab09bd..0000000
--- a/doc/merchant-api.content.texi
+++ /dev/null
@@ -1,1068 +0,0 @@
-@c *****************************************
-@c This file is supposed to be included from
-@c the language-specific tutorial.
-@c *****************************************
-
-@c Define a new index for options.
-@defcodeindex op
-@c Combine everything into one index (arbitrarily chosen to be the
-@c concept index).
-@syncodeindex op cp
-@c %**end of header
-
-@copying
-This document is a tutorial for the GNU Taler Merchant API (version
@value{VERSION}, @value{UPDATED})
-
-Copyright @copyright{} 2018 Taler Systems SA
-
-@quotation
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.3 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
-Texts. A copy of the license is included in the section entitled
-``GNU Free Documentation License''.
-@end quotation
-@end copying
-@c If your tutorial is published on paper by the FSF, it should include
-@c The standard FSF Front-Cover and Back-Cover Texts, as given in
-@c maintain.texi.
-@c
-@c Titlepage
-@c
-@titlepage
-@title The GNU Taler Merchant API tutorial
-@subtitle Version @value{VERSION}
-@subtitle @value{UPDATED}
-@author Christian Grothoff (@email{christian@@grothoff.org})
-@author Marcello Stanisci (@email{marcello.stanisci@@inria.fr})
-@author Florian Dold (@email{florian.dold@@inria.fr})
-@page
-@vskip 0pt plus 1filll
-@insertcopying
-@end titlepage
-
-@summarycontents
-@contents
-
-@ifnottex
-@node Top
-@top The GNU Taler Merchant API Tutorial (Version for @value{LANGNAME})
-@insertcopying
-@end ifnottex
-
-
-@menu
-* Introduction:: What this tutorial is about
-* Accepting a Simple Payment:: How to accept simple payments
-* Giving Refunds:: How to give refunds to
customers
-* Giving Customers Tips:: How to reward customers with
tips
-* Advanced topics:: Detailed solutions to
specific issues
-
-
-Appendices
-
-* GNU-LGPL:: The GNU Lesser General Public License says
how you
- can use the code of libtalermerchant.so in
your own projects.
-* GNU-FDL:: The GNU Free Documentation License says how
you
- can copy and share the documentation of GNU
Taler.
-
-Indices
-
-* Concept Index:: Index of concepts and programs.
-@end menu
-
-
-@node Introduction
-@chapter Introduction
-
-@section About GNU Taler
-
-GNU Taler is an open protocol for an electronic payment system with a free
-software reference implementation. GNU Taler offers secure, fast and easy
-payment processing using well understood cryptographic techniques. GNU Taler
-allows customers to remain anonymous, while ensuring that merchants can be held
-accountable by governments. Hence, GNU Taler is compatible with
-anti-money-laundering (AML) and know-your-customer (KYC) regulation, as well as
-data protection regulation (such as GDPR).
-
-
-@section About this tutorial
-
-This tutorial addresses how to process payments using the GNU Taler merchant
-Backend. This chapter explains some basic concepts. In the second chapter, you
-will learn how to do basic payments.
-
-@clear GOT_LANG
-@ifset LANG_PYTHON
-@set GOT_LANG 1
-This version of the tutorial has examples for Python3.
-It uses the requests library for HTTP requests.
-@end ifset
-@ifset LANG_CURL
-@set GOT_LANG 1
-This version of the tutorial has examples for the
-command line with cURL.
-@end ifset
-@ifset LANG_PHP
-This version of the tutorial has examples for PHP,
-using libcurl.
-@end ifset
-@c
-Versions for other languages/environments are available as well.
-
-@cindex examples
-@cindex git
-If you want to look at some simple, running examples, check out these:
-@itemize
-@item
-The @url{https://git.taler.net/blog.git/tree/talerblog/blog/blog.py, essay
merchant} that
-sells single chapters of a book.
-@item
-The
@url{https://git.taler.net/donations.git/tree/talerdonations/donations/donations.py,
donation page} that
-accepts donations for software projects and gives donation receipts.
-@item
-The
@url{https://git.taler.net/survey.git/tree/talersurvey/survey/survey.py,survey}
that
-gives users who answer a question a small reward.
-@end itemize
-
-@section Architecture overview
-
-The Taler software stack for a merchant consists of the following
-main components:
-
-@itemize
-@cindex frontend
-@item A frontend which interacts with the customer's browser. The
- frontend enables the customer to build a shopping cart and place
- an order. Upon payment, it triggers the respective business logic
- to satisfy the order. This component is not included with Taler,
- but rather assumed to exist at the merchant. This tutorial
- describes how to develop a Taler frontend.
-@cindex backend
-@item A Taler-specific payment backend which makes it easy for the
- frontend to process financial transactions with Taler. For this
- tutorial, you will use a public sandbox backend. For production
- use, you must either set up your own backend or ask another person
- to do so for you.
-@end itemize
-
-The following image illustrates the various interactions of these
-key components:
-
-@image{arch-api, 3in}
-
-The backend provides the cryptographic protocol support, stores Taler-specific
-financial information and communicates with the GNU Taler exchange over the
-Internet. The frontend accesses the backend via a RESTful API. As a result,
-the frontend never has to directly communicate with the exchange, and also does
-not deal with sensitive data. In particular, the merchant's signing keys and
-bank account information are encapsulated within the Taler backend.
-
-Some functionality of the backend (the ``public interface``) is also exposed
to the
-customer's browser directly. In the HTTP API, all public endpoints are
prefixed with @code{/public/}.
-
-@section Public Sandbox Backend and Authentication
-@cindex sandbox
-@cindex authorization
-
-How the frontend authenticates to the Taler backend depends on the
configuration. @xref{Top,,, manual, Taler Merchant Operating Manual}.
-
-The public sandbox backend @url{https://backend.demo.taler.net/} uses an API
key
-in the @code{Authorization} header. The value of this header must be
-@code{ApiKey sandbox} for the public sandbox backend.
-
-@clear GOT_LANG
-@ifset LANG_CURL
-@set GOT_LANG 1
-@example
-curl -i 'https://backend.demo.taler.net/' \
- --header "Authorization: ApiKey sandbox"
-# HTTP/1.1 200 OK
-# [...]
-#
-# Hello, I'm a merchant's Taler backend. This HTTP server is not for humans.
-@end example
-@end ifset
-@ifset LANG_PYTHON
-@set GOT_LANG 1
-@example
-@verbatim
->>> import requests
->>> requests.get("https://backend.demo.taler.net";,
-... headers={"Authorization": "ApiKey sandbox"})
-<Response [200]>
-@end verbatim
-@end example
-@end ifset
-@ifset LANG_PHP
-@set GOT_LANG 1
-@example
-@verbatim
-php > $c = curl_init("https://backend.demo.taler.net/";);
-php > $options = array(CURLOPT_RETURNTRANSFER => true,
-php ( CURLOPT_CUSTOMREQUEST => "GET",
-php ( CURLOPT_HTTPHEADER => array("Authorization: ApiKey
sandbox"));
-php > curl_setopt_array ($c, $options);
-php > $r = curl_exec ($c);
-php > echo curl_getinfo ($c, CURLINFO_HTTP_CODE);
-200
-php > echo $r;
-Hello, I'm a merchant's Taler backend. This HTTP server is not for humans.
-@end verbatim
-@end example
-@end ifset
-@ifclear GOT_LANG
-@example
-(example not available for this language)
-@end example
-@end ifclear
-
-If an HTTP status code other than 200 is returned, something went wrong. You
-should figure out what the problem is before continuing with this tutorial.
-
-The sandbox backend @url{https://backend.demo.taler.net/} uses @code{KUDOS} as
-an imaginary currency. Coins denominated in @code{KUDOS} can be withdrawn
-from @url{https://bank.demo.taler.net/}.
-
-@section Merchant Instances
-@cindex instance
-
-The same Taler merchant backend server can be used by multiple separate
-merchants that are separate business entities. Each of these separate business
-entities is called a @emph{merchant instance}, and is identified by an
-alphanumeric @emph{instance id}. If the instance is omitted, the instance id
-@code{default} is assumed.
-
-The following merchant instances are configured on
@url{https://backend.demo.taler.net/}:
-@itemize
-@item @code{GNUnet} (The GNUnet project)
-@item @code{FSF} (The Free Software Foundation)
-@item @code{Tor} (The Tor Project)
-@item @code{default} (Kudos Inc.)
-@end itemize
-
-Note that these are fictional merchants used for our demonstrators and
-not affiliated with or officially approved by the respective projects.
-
-
-@node Accepting a Simple Payment
-@chapter Accepting a Simple Payment
-
-@section Creating an Order for a Payment
-@cindex order
-
-Payments in Taler revolve around an @emph{order}, which is a machine-readable
-description of the business transaction for which the payment is to be made.
-Before accepting a Taler payment as a merchant
-you must create such an order.
-
-This is done by posting a JSON object to the backend's @code{/order} API
endpoint. At least the
-following fields must be given:
-
-@itemize
-@item @var{amount}: The amount to be paid, as a string in the format
-@code{CURRENCY:DECIMAL_VALUE}, for example @code{EUR:10} for 10 Euros or
-@code{KUDOS:1.5} for 1.5 KUDOS.
-
-@item @var{summary}: A human-readable summary for what the payment is about.
-The summary should be short enough to fit into titles, though no
-hard limit is enforced.
-
-@item @var{fulfillment_url}: A URL that will be displayed once the payment is
-completed. For digital goods, this should be a page that displays the product
-that was purchased. On successful payment, the wallet automatically appends
-the @code{order_id} as a query parameter, as well as the @code{session_sig} for
-session-bound payments (discussed later).
-@end itemize
-
-Orders can have many more fields, see @ref{The Taler Order Format}.
-
-After successfully @code{POST}ing to @code{/order}, an @code{order_id} will be
-returned. Together with the merchant @code{instance}, the order id uniquely
-identifies the order within a merchant backend.
-
-@clear GOT_LANG
-@ifset LANG_CURL
-@set GOT_LANG 1
-@example
-@verbatim
-ORDER='
-{"order": {
- "amount": "KUDOS:10",
- "summary": "Donation",
- "fulfillment_url": "https://example.com/thanks.html"}}
-'
-
-curl -i -X POST 'https://backend.demo.taler.net/order' \
- --header "Authorization: ApiKey sandbox" -d "$ORDER"
-# HTTP/1.1 200 OK
-# [...]
-#
-# {
-# "order_id": "2018.058.21.46.06-024C85K189H8P"
-# }
-@end verbatim
-@end example
-@end ifset
-@ifset LANG_PYTHON
-@set GOT_LANG 1
-@example
-@verbatim
->>> import requests
->>> order = dict(order=dict(amount="KUDOS:10",
-... summary="Donation",
-... fulfillment_url="https://example.com/thanks.html";))
->>> order_resp = requests.post("https://backend.demo.taler.net/order";,
json=order,
-... headers={"Authorization": "ApiKey sandbox"})
-<Response [200]>
-@end verbatim
-@end example
-@end ifset
-@ifset LANG_PHP
-@set GOT_LANG 1
-@example
-@verbatim
-php > $c = curl_init("https://backend.demo.taler.net/order";);
-php > $json = array("order"=>
-php ( array("amount"=>"KUDOS:1",
-php ( "fulfillent_url"=>"https://example.com/thanks.html";,
-php ( "summary"=>"nice product"));
-php > $options = array(CURLOPT_RETURNTRANSFER=>true,
-php ( CURLOPT_CUSTOMREQUEST=>"POST",
-php ( CURLOPT_POSTFIELDS=>json_encode($json),
-php ( CURLOPT_HTTPHEADER=>array("Authorization: ApiKey
sandbox"));
-php > curl_setopt_array($c, $options);
-php > $r = curl_exec($c);
-php > echo curl_getinfo($c, CURLINFO_HTTP_CODE);
-200
-php > echo $r;
-{
- "order_id": "2018.072.12.48.51-014DKDKBMHPDP"
-}
-@end verbatim
-@end example
-@end ifset
-@ifclear GOT_LANG
-@example
-(example not available for this language)
-@end example
-@end ifclear
-
-The backend will fill in some details missing in the order, such as the address
-of the merchant instance. The full details are called the @emph{contract
-terms}.
-@cindex contract
-@cindex terms
-
-@section Checking Payment Status and Prompting for Payment
-The status of a payment can be checked with the @code{/check-payment}
endpoint. If the payment
-is yet to be completed by the customer, @code{/check-payment} will give the
frontend a URL (the @var{payment_redirect_url})
-that will trigger the customer's wallet to execute the payment.
-
-Note that the only way to obtain the @var{payment_redirect_url} is to check
the status of the payment,
-even if you know that the user did not pay yet.
-
-@clear GOT_LANG
-@ifset LANG_CURL
-@set GOT_LANG 1
-@example
-@verbatim
-ORDER_ID="2018.058.21.46.06-024C85K189H8P"
-curl -i "https://backend.demo.taler.net/check-payment?order_id=$ORDER_ID"; \
- --header "Authorization: ApiKey sandbox"
-# HTTP/1.1 200 OK
-# [...]
-#
-# {
-# "payment_redirect_url":
-# "https://backend.demo.taler.net/public/trigger-pay?[...]";,
-# "paid": false
-# }
-@end verbatim
-@end example
-@end ifset
-@ifset LANG_PYTHON
-@set GOT_LANG 1
-@example
-@verbatim
->>> import requests
->>> r = requests.get("https://backend.demo.taler.net/check-payment";,
-... params=dict(order_id=order_resp.json()["order_id"]),
-... headers={"Authorization": "ApiKey sandbox"})
->>> print(r.json())
-@end verbatim
-@end example
-@end ifset
-@ifset LANG_PHP
-@set GOT_LANG 1
-@example
-@verbatim
-php > $ORDER_ID = "2018.072.12.48.51-014DKDKBMHPDP";
-php > curl_init
("https://backend.demo.taler.net/check-payment?order_id=$ORDER_ID";);
-php > $options = array(CURLOPT_RETURNTRANSFER=>true,
-php ( CURLOPT_CUSTOMREQUEST=>"GET",
-php ( CURLOPT_HTTPHEADER=>array(
-php ( "Authorization: ApiKey sandbox"));
-php > curl_setopt_array($c, $options);
-php > $r = curl_exec($c);
-php > echo $r;
-@end verbatim
-@end example
-@end ifset
-@ifclear GOT_LANG
-@example
-(example not available for this language)
-@end example
-@end ifclear
-
-If the @var{paid} field in the response is @code{true}, the other
-fields in the response will be different. Once the payment was
-completed by the user, the response will contain the following fields:
-
-@itemize
-@item @var{paid}: Set to @var{true}.
-@item @var{contract_terms}: The full contract terms of the order.
-@item @var{refunded}: @code{true} if a (possibly partial) refund was granted
for this purchase.
-@item @var{refunded_amount}: Amount that was refunded
-@item @var{last_session_id}: Last session ID used by the customer's wallet.
@xref{Session-Bound Payments}.
-@end itemize
-
-Once the frontend has confirmed that the payment was successful, it
-usually needs to trigger the business logic for the merchant to
-fulfill the merchant's obligations under the contract.
-
-
-@node Giving Refunds
-@chapter Giving Refunds
-@cindex refunds
-
-A refund in GNU Taler is a way to ``undo'' a payment. It needs to be
-authorized by the merchant. Refunds can be for any fraction of the
-original amount paid, but they cannot exceed the original payment.
-Refunds are
-time-limited and can only happen while the exchange holds funds for a
-particular payment in escrow. The time during which a refund is possible
-can be controlled by setting the @code{refund_deadline} in an order. The
default
-value for this refund deadline is specified in the configuration of the
-merchant's backend.
-
-The frontend can instruct the merchant backend to authorize a refund
-by @code{POST}ing to the @code{/refund} endpoint.
-
-The refund request JSON object has the following fields:
-@itemize
-@item @var{order_id}: Identifies for which order a customer should be refunded.
-@c NOTE: the merchant does NOT default to instance "default".
-@item @var{instance}: Merchant instance to use.
-@item @var{refund}: Amount to be refunded. If a previous refund was
-authorized for the same order, the new amount must be higher, otherwise
-the operation has no effect. The value indicates the
-total amount to be refunded, @emph{not} an increase in the refund.
-@item @var{reason}: Human-readable justification for the refund. The reason
is only used by the Back Office and is not exposed to the customer.
-@end itemize
-
-If the request is successful (indicated by HTTP status code 200), the response
-includes a @code{refund_redirect_url}. The frontend must redirect the
-customer's browser to that URL to allow the refund to be processed by the
wallet.
-
-This code snipped illustrates giving a refund:
-@clear GOT_LANG
-@ifset LANG_CURL
-@set GOT_LANG 1
-@example
-@verbatim
-REFUND_REQ='
-{"order_id": "2018.058.21.46.06-024C85K189H8P",
- "refund": "KUDOS:10",
- "instance": "default",
- "reason": "Customer did not like the product"}
-'
-
-curl -i -X POST 'https://backend.demo.taler.net/refund' \
- --header "Authorization: ApiKey sandbox" -d "$REFUND_REQ"
-# HTTP/1.1 200 OK
-# [...]
-#
-# {
-# [...]
-# "refund_redirect_url": "[...]"
-# }
-@end verbatim
-@end example
-@end ifset
-@ifset LANG_PYTHON
-@set GOT_LANG 1
-@example
-@verbatim
->>> import requests
->>> refund_req = dict(order_id="2018.058.21.46.06-024C85K189H8P",
-... refund="KUDOS:10",
-... instance="default",
-... reason="Customer did not like the product")
->>> requests.post("https://backend.demo.taler.net/refund";, json=refund_req,
-... headers={"Authorization": "ApiKey sandbox"})
-<Response [200]>
-@end verbatim
-@end example
-@end ifset
-
-@ifset LANG_PHP
-@set GOT_LANG 1
-@example
-@verbatim
-php > $REFUND_REQ = array("order_id"=>$ORDER_ID,
-php ( "refund"=>"KUDOS:0.5",
-php ( "instance"=>"default",
-php ( "reason"=>"Customer did not like product");
-php > $options = array(CURLOPT_RETURNTRANSFER=>true,
-php ( CURLOPT_CUSTOMREQUEST=>"POST",
-php ( CURLOPT_HTTPHEADER=>array(
-php ( "Authorization: ApiKey sandbox"),
-php ( CURLOPT_POSTFIELDS=>json_encode($REFUND_REQ));
-php > $c = curl_init("https://backend.demo.taler.net/refund";);
-php > curl_setopt_array($c, $options);
-php > $r = curl_exec($c);
-php > echo $r;
-php > echo curl_getinfo($c, CURLINFO_HTTP_CODE);
-200 # Make sure you paid first!
-@end verbatim
-@end example
-@end ifset
-@ifclear GOT_LANG
-@example
-(example not available for this language)
-@end example
-@end ifclear
-
-@node Giving Customers Tips
-@chapter Giving Customers Tips
-@cindex tips
-
-@c NOTE: Terminology should not be merchant/customer here, as
-@c the relationship is completely different. So I use
-@c ``site'' and ``visitor'', as that is right now the proper
-@c context. We may want to use more payment-ish terminology
-@c in the future, but ``donor'' and ``grantee'' sound excessive
-@c in the context of ``tips''.
-
-GNU Taler allows Web sites to grant small amounts directly to the
-visitor. The idea is that some sites may want incentivize actions
-such as filling out a survey or trying a new feature. It is important
-to note that tips are not enforceable for the visitor, as there is no
-contract. It is simply a voluntary gesture of appreciation of the site
-to its visitor. However, once a tip has been granted, the visitor
-obtains full control over the funds provided by the site.
-
-The ``merchant'' backend of the site must be properly configured for
-tipping, and sufficient funds must be made available for tipping @xref{Top,,,
manual,
-Taler Merchant Operating Manual}.
-
-To check if tipping is configured properly and if there are
-sufficient funds available for tipping, query the @code{/tip-query} endpoint:
-
-@clear GOT_LANG
-@ifset LANG_CURL
-@set GOT_LANG 1
-@example
-@verbatim
-curl -i 'https://backend.demo.taler.net/tip-query?instance=default' --header
"Authorization: ApiKey sandbox"
-# HTTP/1.1 200 OK
-# [...]
-#
-# {
-# [...]
-# "amount_available": "KUDOS:153.47",
-# "amount_authorized": "KUDOS:10"
-# }
-@end verbatim
-@end example
-@end ifset
-@ifset LANG_PYTHON
-@set GOT_LANG 1
-@example
-@verbatim
->>> import requests
->>> requests.get("https://backend.demo.taler.net/tip-query?instance=default";,
-... headers={"Authorization": "ApiKey sandbox"})
-<Response [200]>
-@end verbatim
-@end example
-@end ifset
-@ifset LANG_PHP
-@set GOT_LANG 1
-@example
-@verbatim
-php > $c =
curl_init("https://backend.demo.taler.net/tip-query?instance=default";);
-php > $options = array(CURLOPT_RETURNTRANSFER=>true,
-php ( CURLOPT_CUSTOMREQUEST=>"GET",
-php ( CURLOPT_HTTPHEADER=>array(
-php ( "Authorization: ApiKey sandbox"));
-php > curl_setopt_array($c, $options);
-php > $r = curl_exec($c);
-php > echo curl_getinfo($c, CURLINFO_HTTP_CODE);
-200
-@end verbatim
-@end example
-@end ifset
-@ifclear GOT_LANG
-@example
-(example not available for this language)
-@end example
-@end ifclear
-
-@cindex authorize tip
-To authorize a tip, @code{POST} to @code{/tip-authorize}. The following
fields are recognized in the JSON
-request object:
-
-@itemize
-@item @var{amount}: Amount that should be given to the visitor as a tip.
-@item @var{instance}: Merchant instance that grants the tip (each instance may
have its own independend tipping funds configured).
-@item @var{justification}: Description of why the tip was granted.
Human-readable text not exposed to the customer, but used by the Back Office.
-@item @var{next_url}: The URL that the user's browser should be redirected to
by the wallet, once the tip has been processed.
-@end itemize
-
-The response from the backend contains a @code{tip_redirect_url}. The
customer's browser must be
-redirected to this URL for the wallet to pick up the tip.
-@cindex pick up tip
-
-This code snipped illustrates giving a tip:
-@clear GOT_LANG
-@ifset LANG_CURL
-@set GOT_LANG 1
-@example
-@verbatim
-TIP_REQ='
-{"amount": "KUDOS:0.5",
- "instance": "default",
- "justification": "User filled out survey",
- "next_url": "https://merchant.com/thanks.html"}
-'
-
-curl -i -X POST 'https://backend.demo.taler.net/tip-authorize' \
- --header "Authorization: ApiKey sandbox" -d "$TIP_REQ"
-# HTTP/1.1 200 OK
-# [...]
-#
-# {
-# [...]
-# "tip_redirect_url": "[...]"
-# }
-@end verbatim
-@end example
-@end ifset
-@ifset LANG_PYTHON
-@set GOT_LANG 1
-@example
-@verbatim
->>> import requests
->>> tip_req = dict(amount="KUDOS:0.5",
-... instance="default",
-... justification="User filled out survey",
-... next_url="https://merchant.com/thanks.html";)
->>> requests.post("https://backend.demo.taler.net/tip-authorize";, json=tip_req,
-... headers={"Authorization": "ApiKey sandbox"})
-<Response [200]>
-@end verbatim
-@end example
-@end ifset
-
-@ifset LANG_PHP
-@set GOT_LANG 1
-@example
-@verbatim
-php > $TIP_REQ = array(
-php ( "amount"=>"KUDOS:1",
-php ( "instance"=>"default",
-php ( "justification"=>"surveying",
-php ( "next_url"=>"https://example.com/survey-thanks.html";);
-php > $options = array(CURLOPT_RETURNTRANSFER=>true,
-php ( CURLOPT_CUSTOMREQUEST=>"POST",
-php ( CURLOPT_POSTFIELDS=>json_encode($TIP_REQ),
-php ( CURLOPT_HTTPHEADER=>array("Authorization: ApiKey
sandbox"));
-php > $c = curl_init("https://backend.demo.taler.net/tip-authorize";);
-php > curl_setopt_array($c, $options);
-php > $r = curl_exec($c);
-php > echo curl_getinfo($c, CURLINFO_HTTP_CODE);
-200
-@end verbatim
-@end example
-@end ifset
-
-@ifclear GOT_LANG
-@example
-(example not available for this language)
-@end example
-@end ifclear
-
-
-@node Advanced topics
-@chapter Advanced topics
-
-@menu
-* Detecting the Presence of the Taler Wallet:: Detecting the Presence of the
Taler Wallet
-* Integration with the Back Office:: Integration with the Back
Office
-* Session-Bound Payments:: Session-bound payments for
digital goods
-* Product Identification:: Product Identification
-* The Taler Order Format:: The Taler Order Format
-@end menu
-
-@node Detecting the Presence of the Taler Wallet
-@section Detecting the Presence of the Taler Wallet
-@cindex wallet
-
-Taler offers ways to detect whether a user has the wallet installed in
-their browser. This allows Web sites to adapt accordingly. Note that
-not all platforms can do presence detection reliably. Some platforms
-might have a Taler wallet installed as a separate App instead of using
-a Web extension. In these cases, presence detection will fail. Thus,
-sites may want to allow users to request Taler payments even if a
-wallet could not be detected, especially for visitors using mobiles.
-
-@subsection Presence detection without JavaScript
-Presence detection without JavaScript is based on CSS classes. You can hide or
-show elements selectively depending on whether the wallet is detected or not.
-
-In order to work correctly, a special fallback stylesheet must be included that
-will be used when the wallet is not present. The stylesheet can be put into
-any file, but must be included via a @code{link} tag with the @code{id}
-attribute set to @code{taler-presence-stylesheet}. If a wallet is present, it
-will ``hijack'' this stylesheet to change how elements with the following
-classes are rendered:
-
-The following CSS classes can be used:
-@table @code
-@item taler-installed-hide
-A CSS rule will set the @code{display} property for this class to @code{none}
once the Taler wallet is installed and enabled.
-If the wallet is not installed, @code{display} will be @code{inherit}.
-
-@item taler-installed-show
-A CSS rule will set the @code{display} property for this class to
@code{inherit} once the Taler wallet is installed and enabled.
-If the wallet is not installed, @code{display} will be @code{none}.
-
-@end table
-
-The following is a complete example:
-
-@smallexample
-<!DOCTYPE html>
-<html data-taler-nojs="true">
- <head>
- <title>Tutorial</title>
- <link rel="stylesheet"
- type="text/css"
- href="/web-common/taler-fallback.css"
- id="taler-presence-stylesheet" />
- </head>
- <body>
- <p class="taler-installed-hide">
- No wallet found.
- </p>
- <p class="taler-installed-show">
- Wallet found!
- </p>
- </body>
-</html>
-@end smallexample
-
-The @code{taler-fallback.css} is part of the Taler's @emph{web-common}
repository,
-available at
@url{https://git.taler.net/web-common.git/tree/taler-fallback.css}.
-You may have to adjust the @code{href} attribute in the HTML code above to
point
-to the correct location of the @code{taler-fallback.css} file on your Web site.
-
-@subsection Detection with JavaScript
-
-The following functions are defined in the @code{taler} namespace of the
@code{taler-wallet-lib} helper library
-available at
@url{https://git.taler.net/web-common.git/tree/taler-wallet-lib.js}.
-
-@table @code
-@item onPresent(callback: () => void)
-Adds a callback to be called when support for Taler payments is detected.
-
-@item onAbsent(callback: () => void)
-Adds a callback to be called when support for Taler payments is disabled.
-
-@end table
-
-Note that the registered callbacks may be called more than once. This may
-happen if a user disables or enables the wallet in the browser's extension
-settings while a shop's frontend page is open.
-
-@c FIXME: include full example of Web site including taler-wallet-lib.js
-@c and using JS detection actions. (alert()?)
-
-@node Integration with the Back Office
-@section Integration with the Back Office
-
-Taler ships a Back Office application as a stand-alone Web application.
-The Back Office has its own documentation at
@url{https://docs.taler.net/backoffice/html/manual.html}.
-
-Developers wishing to tightly integrate back office support for
-Taler-based payments into an existing back office application should
-focus on the wire transfer tracking and transaction history sections
-of the Taler Backend API specification at
-@url{https://docs.taler.net/api/api-merchant.html}
-
-@node Session-Bound Payments
-@section Session-Bound Payments
-@cindex session
-
-Sometimes checking if an order has been paid for is not enough. For
-example, when selling access to online media, the publisher may want
-to be paid for exactly the same product by each customer. Taler
-supports this model by allowing the mechant to check whether the
-``payment receipt'' is available on the user's current device. This
-prevents users from easily sharing media access by transmitting a link
-to the fulfillment page. Of course sophisticated users could share
-payment receipts as well, but this is not as easy as sharing a link,
-and in this case they are more likely to just share the media
-directly.
-
-To use this feature, the merchant must first assign the user's current browser
-an ephemeral @code{session_id}, usually via a session cookie. When executing
-or re-playing a payment, the wallet will receive an additional signature
-(@code{session_sig}). This signature certifies that the wallet
-showed a payment receipt for the respective order in the current session.
-@cindex cookie
-
-Session-bound payments are triggerd by passing the @code{session_id} parameter
-to the @code{/check-payment} endpoint. The wallet will then redirect to the
-fulfillment page, but include an additional @code{session_sig} parameter. The
-frontend can query @code{/check-payment} with both the @code{session_id} and
-the @code{session_sig} to verify that the signature is correct.
-
-The last session ID that was successfuly used to prove that the payment
-receipt is in the user's wallet is also available as @code{last_session_id} in
-the response to @code{/check-payment}.
-@c FIXME: used for what?
-
-@node Product Identification
-@section Product Identification
-@cindex resource url
-
-In some situations the user may have paid for some digital good, but the
frontend
-does not know the exact order ID, and thus cannot instruct the wallet to reveil
-the existing payment receipt. This is common for simple shops without a login
-system. In this case, the user would be prompted for payment again, even
-though they already purchased the product.
-
-To allow the wallet to instead find the existing payment receipt, the
-shop must use a unique fulfillment URL for each product. Then, the
-frontend must provide an additional @code{resource_url} parameter to
-to @code{/check-payment}. It should identify this unique fulfillment
-URL for the product. The wallet will then check whether it has paid
-for a contract with the same @code{resource_url} before, and if so
-replay the previous payment.
-@c FIXME: design question (!): why do we not simply set a flag (``unique
fulfillment url'')
-@c instead of passing the fulfillment URL a *second* time to the backend?
-@c (and having to worry about it being the same as in the order on /order)?
-
-
-@c Section describing the format of Taler contracts/proposals in detail
-
-@node The Taler Order Format
-@section The Taler Order Format
-@cindex contract
-@cindex terms
-@cindex order
-
-A Taler order can specify many details about the payment.
-This section describes each of the fields in depth.
-
-Financial amounts are always specified as a string in the format
@code{"CURRENCY:DECIMAL_VALUE"}.
-
-@table @var
-@item amount
-@cindex amount
-Specifies the total amount to be paid to the merchant by the customer.
-
-@item max_fee
-@cindex fees
-@cindex maximum deposit fee
-This is the maximum total amount of deposit fees that the merchant is
-willing to pay. If the deposit fees for the coins exceed this amount,
-the customer has to include it in the payment total. The fee is
-specified using the same triplet used for @var{amount}.
-
-
-@item max_wire_fee
-@cindex fees
-@cindex maximum wire fee
-Maximum wire fee accepted by the merchant (customer share to be
-divided by the 'wire_fee_amortization' factor, and further reduced
-if deposit fees are below 'max_fee'). Default if missing is zero.
-
-
-@item wire_fee_amortization
-@cindex fees
-@cindex maximum fee amortization
-Over how many customer transactions does the merchant expect to
-amortize wire fees on average? If the exchange's wire fee is
-above 'max_wire_fee', the difference is divided by this number
-to compute the expected customer's contribution to the wire fee.
-The customer's contribution may further be reduced by the difference
-between the 'max_fee' and the sum of the actual deposit fees.
-Optional, default value if missing is 1. 0 and negative values are
-invalid and also interpreted as 1.
-
-@item pay_url
-@cindex pay_url
-Which URL accepts payments. This is the URL where the wallet will POST
-coins.
-
-@item fulfillment_url
-@cindex fulfillment URL
-Which URL should the wallet go to for obtaining the fulfillment,
-for example the HTML or PDF of an article that was bought, or an
-order tracking system for shipments, or a simple human-readable
-Web page indicating the status of the contract.
-
-@item order_id
-@cindex order ID
-Alphanumeric identifier, freely definable by the merchant.
-Used by the merchant to uniquely identify the transaction.
-
-@item summary
-@cindex summary
-Short, human-readable summary of the contract. To be used when
-displaying the contract in just one line, for example in the
-transaction history of the customer.
-
-@item timestamp
-Time at which the offer was generated.
-@c FIXME: describe time format in detail here
-
-@item pay_deadline
-@cindex payment deadline
-Timestamp of the time by which the merchant wants the exchange
-to definitively wire the money due from this contract. Once
-this deadline expires, the exchange will aggregate all
-deposits where the contracts are past the @var{refund_deadline}
-and execute one large wire payment for them. Amounts will be
-rounded down to the wire transfer unit; if the total amount is
-still below the wire transfer unit, it will not be disbursed.
-
-@item refund_deadline
-@cindex refund deadline
-Timestamp until which the merchant willing (and able) to give refunds
-for the contract using Taler. Note that the Taler exchange will hold
-the payment in escrow at least until this deadline. Until this time,
-the merchant will be able to sign a message to trigger a refund to the
-customer. After this time, it will no longer be possible to refund
-the customer. Must be smaller than the @var{pay_deadline}.
-
-@item products
-@cindex product description
-Array of products that are being sold to the customer. Each
-entry contains a tuple with the following values:
-
-@table @var
-@item description
-Description of the product.
-@item quantity
-Quantity of the items to be shipped. May specify a unit (@code{1 kg})
-or just the count.
-@item price
-Price for @var{quantity} units of this product shipped to the
-given @var{delivery_location}. Note that usually the sum of all
-of the prices should add up to the total amount of the contract,
-but it may be different due to discounts or because individual
-prices are unavailable.
-@item product_id
-Unique ID of the product in the merchant's catalog. Can generally
-be chosen freely as it only has meaning for the merchant, but
-should be a number in the range @math{[0,2^{51})}.
-@item taxes
-Map of applicable taxes to be paid by the merchant. The label is the
-name of the tax, i.e. @var{VAT}, @var{sales tax} or @var{income tax},
-and the value is the applicable tax amount. Note that arbitrary
-labels are permitted, as long as they are used to identify the
-applicable tax regime. Details may be specified by the regulator.
-This is used to declare to the customer which taxes the merchant
-intends to pay, and can be used by the customer as a receipt.
-@c FIXME: a receipt not including the item's price?
-The information is also likely to be used by tax audits of the merchant.
-@item delivery_date
-Time by which the product is to be delivered to the
-@var{delivery_location}.
-@item delivery_location
-This should give a label in the @var{locations} map, specifying
-where the item is to be delivered.
-@end table
-Values can be omitted if they are not applicable. For example, if a
-purchase is about a bundle of products that have no individual prices
-or product IDs, the @var{product_id} or @var{price} may not be
-specified in the contract. Similarly, for virtual products delivered
-directly via the fulfillment URI, there is no delivery location.
-
-@item merchant
-@table @var
-@item address
-This should give a label in the @var{locations} map, specifying
-where the merchant is located.
-@item name
-This should give a human-readable name for the merchant's business.
-@item jurisdiction
-This should give a label in the @var{locations} map, specifying
-the jurisdiction under which this contract is to be arbitrated.
-@end table
-
-@item locations
-@cindex location
-Associative map of locations used in the contract. Labels for
-locations in this map can be freely chosen and used whenever
-a location is required in other parts of the contract. This way,
-if the same location is required many times (such as the business
-address of the customer or the merchant), it only needs to be
-listed (and transmitted) once, and can otherwise be referred to
-via the label. A non-exhaustive list of location attributes
-is the following:
-@table @var
-@item country
-Name of the country for delivery, as found on a postal package, i.e.
``France''.
-@item state
-Name of the state for delivery, as found on a postal package, i.e. ``NY''.
-@item region
-Name of the region for delivery, as found on a postal package.
-@item province
-Name of the province for delivery, as found on a postal package.
-@item city
-Name of the city for delivery, as found on a postal package.
-@item ZIP code
-ZIP code for delivery, as found on a postal package.
-@item street
-Street name for delivery, as found on a postal package.
-@item street number
-Street number (number of the house) for delivery, as found on a postal package.
-@item name receiver name for delivery, either business or person name.
-
-@end table
-
-Note that locations are not required to specify all of these fields,
-and they is also allowed to have additional fields. Contract renderers
-must render at least the fields listed above, and should render fields
-that they do not understand as a key-value list.
-
-@end table
-
-
-@c **********************************************************
-@c ******************* Appendices *************************
-@c **********************************************************
-
-@node GNU-LGPL
-@unnumbered GNU-LGPL
-@cindex license
-@cindex LGPL
-@include lgpl.texi
-
-@node GNU-FDL
-@unnumbered GNU-FDL
-@cindex license
-@cindex GNU Free Documentation License
-@include fdl-1.3.texi
-
-@node Concept Index
-@unnumbered Concept Index
-
-@printindex cp
diff --git a/doc/syntax.texi b/doc/syntax.texi
deleted file mode 100644
index 8aca39d..0000000
--- a/doc/syntax.texi
+++ /dev/null
@@ -1,44 +0,0 @@
-@c Syntax highlighting for texinfo's HTML output
-
-@html
-<script src="highlight.pack.js"></script>
-<script>
-var hls = [];
-var syntaxAuto = true;
-addEventListener("DOMContentLoaded", function() {
- // Highlight blocks with fixed language
- for (let x of hls) {
- let next = x[0].nextElementSibling;
- console.log("next", next);
- let blocks = next.querySelectorAll("pre.example");
- for (let i = 0; i < blocks.length; i++) {
- blocks[i].classList.add("language-" + x[1]);
- hljs.highlightBlock(blocks[i]);
- }
- }
- // auto-detect other blocks if not disabled
- if (syntaxAuto) {
- let blocks = document.querySelectorAll("pre.example");
- for (let i = 0; i < blocks.length; i++) {
- hljs.highlightBlock(blocks[i]);
- }
- }
-});
-</script>
-@end html
-
-@macro setsyntax{lang}
-@html
-<script>
-hls.push([document.currentScript, "\lang\"]);
-</script>
-@end html
-@end macro
-
-@macro setsyntaxnoauto{}
-@html
-<script>
-syntaxAuto = false;
-</script>
-@end html
-@end macro
diff --git a/doc/taler-config.texi b/doc/taler-config.texi
deleted file mode 100644
index efca5a2..0000000
--- a/doc/taler-config.texi
+++ /dev/null
@@ -1,47 +0,0 @@
-@c This file is used both in the exchange and merchant
-@c manuals. Edits should be propagated to both Gits!
-
-@node Using taler-config
-@section Using taler-config
-@cindex taler-config
-
-The tool @code{taler-config} can be used to
-extract or manipulate configuration values; however, the configuration
-use the well-known INI file format and can also be edited by hand.
-
-Run
-@example
-$ taler-config -s $SECTION
-@end example
-to list all of the configuration values in section @code{$SECTION}.
-
-Run
-@example
-$ taler-config -s $section -o $option
-@end example
-to extract the respective configuration value for option @code{$option}
-in section @code{$section}.
-
-Finally, to change a setting, run
-@example
-$ taler-config -s $section -o $option -V $value
-@end example
-to set the respective configuration value to @code{$value}. Note that you have
to
-manually restart the Taler backend after you change the configuration to
-make the new configuration go into effect.
-
-Some default options will use $-variables, such as @code{$DATADIR}
-within their value. To expand the @code{$DATADIR} or other $-variables
-in the configuration, pass the @code{-f} option to
-@code{taler-config}. For example, compare:
-@example
-$ taler-config -s ACCOUNT-bank \
- -o WIRE_RESPONSE
-$ taler-config -f -s ACCOUNT-bank \
- -o WIRE_RESPONSE
-@end example
-
-While the configuration file is typically located at
-@code{$HOME/.config/taler.conf}, an alternative location can be
-specified to @code{taler-merchant-httpd} and @code{taler-config} using
-the @code{-c} option.
--
To stop receiving notification emails like this one, please contact
address@hidden.
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [taler-merchant] branch master updated: move documentation to docs repo,
gnunet <=