[taler-marketing] branch master updated: more i18n concerns

[gnunet]

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository marketing.

The following commit(s) were added to refs/heads/master by this push:
     new 4428083  more i18n concerns
4428083 is described below

commit 4428083b88988b443abb69d0c07027ef00cf294f
Author: Florian Dold <address@hidden>
AuthorDate: Thu Apr 30 13:20:38 2020 +0530

    more i18n concerns
---
 standards/draft-dold-payto.xml | 34 +++++++++++++++++++++++++++++-----
 1 file changed, 29 insertions(+), 5 deletions(-)

diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml
index c0da6b2..ec78b3b 100644
--- a/standards/draft-dold-payto.xml
+++ b/standards/draft-dold-payto.xml
@@ -306,7 +306,11 @@ also <xref target="payto-registry" />).
 <t>
 <list style="symbols">
 <t>Name: ach</t>
-<t>Description: Automated Clearing House.  The path consist of two components, 
the routing number and the account number.</t>
+<t>Description: Automated Clearing House.  The path consist of two components, 
the routing number and the account number.
+  Limitations on the length and character set of option values are defined by 
the implementation
+  of the handler.
+  Language tagging and internationalization of options is not supported.
+</t>
 <t>Example: payto://ach/122000661/1234</t>
 <t>Contact: N/A</t>
 <t>References: <xref target="NACHA" />, [this.I-D]</t>
@@ -318,7 +322,11 @@ also <xref target="payto-registry" />).
 <t>
 <list style="symbols">
 <t>Name: bic</t>
-<t>Description: Business Identifier Code. The path consist of just a BIC. This 
is used for wire transfers between banks. The registry for BICs is provided by 
SWIFT. The path does not allow specifying a bank account number.</t>
+<t>Description: Business Identifier Code. The path consist of just a BIC. This 
is used for wire transfers between banks. The registry for BICs is provided by 
SWIFT. The path does not allow specifying a bank account number.
+  Limitations on the length and character set of option values are defined by 
the implementation
+  of the handler.
+  Language tagging and internationalization of options is not supported.
+</t>
 <t>Example: payto://bic/SOGEDEFFXXX</t>
 <t>Contact: N/A</t>
 <t>References: <xref target="BIC" />, [this.I-D]</t>
@@ -339,6 +347,7 @@ also <xref target="payto-registry" />).
   The "instruction" option of the payto URI corresponds to the "end to end 
identifier" of SEPA credit transfers
   and is thus limited to at most 35 characters that can be alphanumeric or 
from the allowed set
   of special characters "+?/-:().,'".
+  Language tagging and internationalization of options is not supported.
 </t>
 <t>Example:
 
@@ -357,7 +366,11 @@ also <xref target="payto-registry" />).
 <list style="symbols">
 <t>Name: upi</t>
 <t>Description: Unified Payment Interface. The path is an account alias.  The 
amount and receiver-name
-options are mandatory for this payment target.</t>
+  options are mandatory for this payment target.
+  Limitations on the length and character set of option values are defined by 
the implementation
+  of the handler.
+  Language tags and internationalization of options are not supported.
+  </t>
 <t>Example: 
payto://upi/address@hidden?receiver-name=Alice&amp;amount=INR:200</t>
 <t>Contact: N/A</t>
 <t>References: <xref target="UPILinking" />, [this.I-D]</t>
@@ -369,7 +382,11 @@ options are mandatory for this payment target.</t>
 <t>
 <list style="symbols">
 <t>Name: bitcoin</t>
-<t>Description: Bitcoin protocol. The path is a "bitcoinaddress" as per <xref 
target="BIP0021" />.</t>
+<t>Description: Bitcoin protocol. The path is a "bitcoinaddress" as per <xref 
target="BIP0021" />.
+Limitations on the length and character set of option values are defined by 
the implementation
+of the handler.
+Language tags and internationalization of options are not supported.
+</t>
 <t>Example: payto://bitcoin/12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu</t>
 <t>Contact: N/A</t>
 <t>References: <xref target="BIP0021" />, [this.I-D]</t>
@@ -381,7 +398,11 @@ options are mandatory for this payment target.</t>
 <t>
 <list style="symbols">
 <t>Name: ilp</t>
-<t>Description: Interledger protocol. The path is an ILP address as per <xref 
target="ILP-ADDR" />.</t>
+<t>Description: Interledger protocol. The path is an ILP address as per <xref 
target="ILP-ADDR" />.
+Limitations on the length and character set of option values are defined by 
the implementation
+of the handler.
+Language tagging and internationalization of options is not supported.
+</t>
 <t>Example: payto://ilp/g.acme.bob</t>
 <t>Contact: N/A</t>
 <t>References: <xref target="ILP-ADDR" />, [this.I-D]</t>
@@ -397,6 +418,9 @@ options are mandatory for this payment target.</t>
   Description: The "void" payment target type allows specifying the parameters
   of an out-of-band payment (such as cash or other types of in-person
   transactions).  The path is optional and interpreted as a comment.
+  Limitations on the length and character set of option values are defined by 
the implementation
+  of the handler.
+  Language tags and internationalization of options are not supported.
 </t>
 <t>Example: payto://void/?amount=EUR:10.5</t>
 <t>Contact: N/A</t>

-- 
To stop receiving notification emails like this one, please contact
address@hidden.