taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 37cb14044906cb5cff65b0c462e9e4311e708b8d
parent 22904b5ffc8710dfcc93196b8ab7b0a938f28dfe
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Fri, 27 Nov 2020 21:09:36 -0500

hopefully uncontroversial style nit: s/organisations/organizations/

I saw elsewhere there is "honor", so assume we lean to American English.
However, i also note that "i.e." and "e.g." are often not followed by comma,
which is more British English.  Probably we need to choose one or the other.

Diffstat:
Mlibeufin/iso20022.rst | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libeufin/iso20022.rst b/libeufin/iso20022.rst @@ -36,7 +36,7 @@ Reasons for not using ISO 20022 directly are: to JSON, they are difficult to use due to their verbosity. 3. Underspecification. Messages like camt.05x leave many "degrees of freedom" when translating the underlying data into a message. -4. No interoperability. As a result of underspecification, different countries/organisations +4. No interoperability. As a result of underspecification, different countries/organizations define their own subset and interpretation rules for ISO 20022 messages. This can lead to even contradictory usage rules. An example for this is how the Swiss and EPC interpretations handle transaction amounts in the presence of multiple currencies.