Move to better backwards-compatible i18n format for contract terms

1 files changed, 6 insertions, 0 deletions

diff --git a/taler-merchant-pos-terminal.rst b/taler-merchant-pos-terminal.rst
index 02cb64b7..b606461a 100644
--- a/taler-merchant-pos-terminal.rst
+++ b/taler-merchant-pos-terminal.rst
@@ -126,6 +126,9 @@ The elements of the JSON file are defined as follows:
 
       // The name of the category. This will be shown to users and used in the order summary.
       name: string;
+
+      // Map from IETF BCP 47 language tags to localized names
+      name_i18n?: { [lang_tag: string]: string };
     }
 
 
@@ -139,6 +142,9 @@ The elements of the JSON file are defined as follows:
       // that will be shown to the user and used in contract terms
       description: string;
 
+      // Map from IETF BCP 47 language tags to localized descriptions
+      description_i18n?: { [lang_tag: string]: string };
+
       // The price of the product
       price: Amount;