Merge branch 'master' of git+ssh://git.taler.net/docs

1 files changed, 24 insertions, 24 deletions

diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index 0b038216..e68bdf8f 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -257,7 +257,7 @@ to export some of the tooling required by Taler.
 
 To download and install libgnunetutil, proceed as follows:
 
-::
+.. code-block:: console
 
    $ git clone git://git.gnunet.org/gnunet
    $ cd gnunet/
@@ -273,7 +273,7 @@ which requires you to run the last step as ``root``.
 
 To download and install the GNU Taler exchange, proceeds as follows:
 
-::
+.. code-block:: console
 
    $ git clone git://git.taler.net/exchange
    $ cd exchange
@@ -311,7 +311,7 @@ it under $HOME/.config/.
 A config file is a text file containing sections, and each section
 contains its values. The right format follows:
 
-::
+.. code-block:: ini
 
    [section1]
    value1 = string
@@ -330,7 +330,7 @@ variables that are unset, by using the following syntax:
 
 by defining them under a ``[paths]`` section, see example below,
 
-::
+.. code-block:: ini
 
    [paths]
    TALER_DEPLOYMENT_SHARED = ${HOME}/shared-data
@@ -340,7 +340,7 @@ by defining them under a ``[paths]`` section, see example below,
 
 or by setting them in the environment:
 
-::
+.. code-block:: console
 
    $ export VAR=/x
 
@@ -378,7 +378,7 @@ file format and can also be edited by hand.
 
 Run
 
-::
+.. code-block:: console
 
    $ taler-config -s $SECTION
 
@@ -386,7 +386,7 @@ to list all of the configuration values in section ``$SECTION``.
 
 Run
 
-::
+.. code-block:: console
 
    $ taler-config -s $section -o $option
 
@@ -395,7 +395,7 @@ section ``$section``.
 
 Finally, to change a setting, run
 
-::
+.. code-block:: console
 
    $ taler-config -s $section -o $option -V $value
 
@@ -408,7 +408,7 @@ their value. To expand the ``$DATADIR`` or other $-variables in the
 configuration, pass the ``-f`` option to ``taler-config``. For example,
 compare:
 
-::
+.. code-block:: console
 
    $ taler-config -s ACCOUNT-bank \
                   -o WIRE_RESPONSE
@@ -496,7 +496,7 @@ starting with “exchange-account-” for the section name. You can ENABLE for
 each account whether it should be used, and for what (incoming or outgoing
 wire transfers):
 
-::
+.. code-block:: ini
 
    [exchange-account-1]
    # With x-taler-bank (say for PyBank)
@@ -530,7 +530,7 @@ The command line tool taler-exchange-wire is used to create the
 follows to create all of the WIRE_RESPONSE files (in the locations
 specified by the configuration):
 
-::
+.. code-block:: console
 
    $ taler-exchange-wire
 
@@ -554,7 +554,7 @@ apply whenever the exchange closes a reserve (sending back funds to the
 customer). The fees must be constant for a full year, which is specified
 as part of the name of the option.
 
-::
+.. code-block:: ini
 
    [fees-iban]
    WIRE-FEE-2018 = EUR:0.01
@@ -583,7 +583,7 @@ choosing the backend, it is mandatory to supply the connection string
 -  via configuration option CONFIG, under section [exchangedb-BACKEND].
    For example, the demo exchange is configured as follows:
 
-::
+.. code-block:: ini
 
    [exchange]
    ...
@@ -741,9 +741,9 @@ by the tool ``taler-exchange-keyup``. The following command generates
 denomkeys and signkeys, plus the "blob" that is to be signed by the
 auditor.
 
-::
+.. code-block:: console
 
-   taler-exchange-keyup -o blob
+   $ taler-exchange-keyup -o blob
 
 *blob* contains data about denomkeys that the exchange operator needs to
 get signed by every auditor he wishes (or is forced to) work with.
@@ -753,9 +753,9 @@ blob to sign (Website, manual delivery, ..). Nonetheless, the exchange
 admin can fake an auditor signature — for testing purposes — by running
 the following command
 
-::
+.. code-block:: console
 
-   taler-auditor-sign -m EXCHANGE_MASTER_PUB -r BLOB -u AUDITOR_URL -o OUTPUT_FILE
+   $ taler-auditor-sign -m EXCHANGE_MASTER_PUB -r BLOB -u AUDITOR_URL -o OUTPUT_FILE
 
 Those arguments are all mandatory.
 
@@ -775,9 +775,9 @@ option ``AUDITOR_BASE_DIR`` under the section ``[exchangedb]``. Assuming
 following command will "add" the auditor identified by ``AUDITOR_URL``
 to the exchange.
 
-::
+.. code-block:: console
 
-   cp OUTPUT_FILE ${HOME}/.local/share/taler/auditors
+   $ cp OUTPUT_FILE ${HOME}/.local/share/taler/auditors
 
 If the auditor has been correctly added, the exchange’s ``/keys``
 response must contain an entry in the ``auditors`` array mentioning the
@@ -793,7 +793,7 @@ versions.
 
 The exchange database can be re-initialized using:
 
-::
+.. code-block:: console
 
    $ taler-exchange-dbinit -r
 
@@ -850,7 +850,7 @@ starting time at which the signing key can be used in microseconds since
 the Epoch. The file format is defined by the struct
 TALER_EXCHANGEDB_PrivateSigningKeyInformationP:
 
-::
+.. code-block:: c
 
    struct TALER_EXCHANGEDB_PrivateSigningKeyInformationP {
       struct TALER_ExchangePrivateKeyP signkey_priv;
@@ -883,7 +883,7 @@ struct TALER_EXCHANGEDB_DenominationKeyInformationP giving the
 attributes of the denomination key and the associated signature with the
 exchange’s long-term offline key:
 
-::
+.. code-block:: c
 
    struct TALER_EXCHANGEDB_DenominationKeyInformationP {
      struct TALER_MasterSignatureP signature;
@@ -940,7 +940,7 @@ Each file must contain a header with the public key information of the
 auditor, the master public key of the exchange, and the number of signed
 denomination keys:
 
-::
+.. code-block:: c
 
    struct AuditorFileHeaderP {
      struct TALER_AuditorPublicKeyP apub;
@@ -1008,7 +1008,7 @@ initialized using ``taler-exchange-keyup``.
 
 You can run a first simple benchmark using:
 
-::
+.. code-block:: console
 
    $ createdb talercheck # if it does not yet exist
    $ taler-exchange-keyup -c benchmark.conf