path: root/locale/it/LC_MESSAGES/messages.po
diff options
Diffstat (limited to 'locale/it/LC_MESSAGES/messages.po')
1 files changed, 161 insertions, 2 deletions
diff --git a/locale/it/LC_MESSAGES/messages.po b/locale/it/LC_MESSAGES/messages.po
index fe32483..6d9c6bb 100644
--- a/locale/it/LC_MESSAGES/messages.po
+++ b/locale/it/LC_MESSAGES/messages.po
@@ -2,7 +2,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2018-06-12 22:03+0200\n"
+"POT-Creation-Date: 2019-01-16 23:15+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: it <>\n"
@@ -1406,6 +1406,157 @@ msgstr ""
"operazioni di deposito effettuate dai commercianti con il cambio, e il "
"profitto del cambio dalle spese di transazione. "
+#: gsoc-codeless.html.j2:5
+msgid "GSoC 2018: Codeless Payment"
+msgstr ""
+#: gsoc-codeless.html.j2:6
+msgid ""
+"Implemented by Shivam Kohli as part of GSoC 2018 under the mentoring and "
+"guidance of Florian Dold."
+msgstr ""
+#: gsoc-codeless.html.j2:12
+#, fuzzy
+#| msgid "Taler system overview"
+msgid "Overview"
+msgstr "Panoramica del sistema"
+#: gsoc-codeless.html.j2:14
+msgid ""
+"Codeless payment is a component that sits between the seller's frontend and "
+"the GNU Taler merchant backend. This component has a web interface, where "
+"payment buttons are configured. Registered merchants can manage their "
+"inventory and simultaneously create a 'Buy Now' button for a specific "
+"product. This code can be directly copy pasted on the seller's frontend and "
+"can be used for 'Pay with Taler'."
+msgstr ""
+#: gsoc-codeless.html.j2:23
+msgid "Use Cases"
+msgstr ""
+#: gsoc-codeless.html.j2:24
+msgid "The various use cases and features of codeless payment are:"
+msgstr ""
+#: gsoc-codeless.html.j2:28
+msgid ""
+"The primary use case is the registration of the merchant. The codeless "
+"payment backend provides a secure django authenticated login to the "
+"merchant. The registered merchant can add inventory (both digital as well as "
+"physical) in their stocks. They can manage inventory and simultaneously "
+"create a 'Buy Now' button for the product. The merchant also monitors the "
+"orders placed and updates the status of the order which helps in shipment "
+msgstr ""
+#: gsoc-codeless.html.j2:33
+msgid ""
+"Merchant has the flexibility to add two types of inventory as follows: <ul> "
+"<li>The merchant can upload digital inventory (like a PDF or HTML page) via "
+"the codeless payments frontend and the user can then purchase it and view "
+"the version hosted by the codeless payment frontend.</li> <li>The merchant "
+"can add any physical inventory available in his stocks. While adding these "
+"inventory, the seller is prompted to add minimum quantity of product that is "
+"required to be maintained in the stock. Whenever the stocks run below this "
+"limit the seller would be notified (currently this feature has not been "
+"added but soon email notification would be added).</li> </ul>"
+msgstr ""
+#: gsoc-codeless.html.j2:42
+msgid ""
+"The buyers will access the seller's frontend where the code for the 'Buy "
+"Now' button is present. When this button is triggered, they are redirected "
+"to codeless payment backend and eventually redirected to the payment page. "
+"After successful payment, the buyer can also track their shipment for "
+"physical products or view the digital version hosted by the codeless payment "
+msgstr ""
+#: gsoc-codeless.html.j2:47
+msgid ""
+"The other use case of the codeless payment backend is to handle the event "
+"when the 'Buy Now' button is triggered on the seller's frontend. To perform "
+"the payment the backend communicates with merchant backend api. After "
+"successful payment, the users are redirected to the fulfilment page."
+msgstr ""
+#: gsoc-codeless.html.j2:53
+msgid "Dynamic Merchant Instance"
+msgstr ""
+#: gsoc-codeless.html.j2:57
+msgid "Use Case Diagram"
+msgstr ""
+#: gsoc-codeless.html.j2:63
+msgid "Link to the contributions made"
+msgstr ""
+#: gsoc-codeless.html.j2:66
+msgid "Codeless Payment Backend"
+msgstr ""
+#: gsoc-codeless.html.j2:68
+msgid "Documentation to dynamically manage Merchant Instances"
+msgstr ""
+#: gsoc-codeless.html.j2:77
+msgid "Future Work"
+msgstr ""
+#: gsoc-codeless.html.j2:79
+msgid ""
+"The backend of codeless payment is very robust and can be easily extended as "
+"per the requirements. It is adaptive to add new features to this framework. "
+"But as per the discussion and the scope of this project, there are various "
+"features that will be soon added in the Codeless Merchant Backend. The list "
+"of future work is as follows:"
+msgstr ""
+#: gsoc-codeless.html.j2:84
+msgid ""
+"To send email notification to the merchant when the stocks run below a "
+"certain limit. The minimum quantity required to be maintained in the stocks "
+"is currently taken from the merchant(specific to each product) but no such "
+"notification system is designed."
+msgstr ""
+#: gsoc-codeless.html.j2:90
+msgid ""
+"To add API access to the merchant backend via the codeless payment service. "
+"Basically, it would be used as a hosting platform for multiple merchants. "
+"There would be an additional user interface part in the codeless payment "
+"service where a logged-in merchant can generate an API key. This API key can "
+"be used to access the functionality of the merchant backend in a controlled "
+"way. After requesting an API key, the page would display the generated key "
+"and a base URL for the API to use by the seller, which is handled by the "
+"codeless payments service."
+msgstr ""
+#: gsoc-codeless.html.j2:96
+msgid ""
+"Mapping every seller account to a separate merchant backend instance. This "
+"is not required for a simple version of codeless payments, but as soon as "
+"API access for sellers, this is a useful feature. The codeless payment "
+"service then can also double as a hosting service for merchants."
+msgstr ""
+#: gsoc-codeless.html.j2:102
+msgid ""
+"To add various analytics for the merchant. Various analysis could be "
+"performed on the orders placed for the respective merchant. Some of the "
+"analysis that can be performed are displaying the most frequently purchased "
+"product, some insights about the shipment tracking, analysis of products "
+"based on delivery location, etc. For this part, dicussions and some more "
+"research have to be done before proceeding to the implementation."
+msgstr ""
+#: gsoc-codeless.html.j2:114
+msgid "Screenshots"
+msgstr ""
#: index.html.j2:6
#, fuzzy
#| msgid "GNU Taler Bibliography"
@@ -1891,7 +2042,7 @@ msgstr ""
"bonifici a set di transazioni commerciali, includendo i termini esatti di "
"ogni contratto. "
msgid "More news"
msgstr "Altre notizie"
@@ -1907,6 +2058,10 @@ msgstr "Questa pagina documenta la storia di GNU Taler. "
msgid "GNU Taler in the Press"
msgstr "GNU Taler nella Stampa"
+#: schemafuzz.html.j2:6
+msgid "SchemaFuzz"
+msgstr ""
#: common/base.j2:5
msgid "GNU Taler"
msgstr "GNU Taler"
@@ -1984,6 +2139,10 @@ msgstr "Introduzione per i programmatori"
msgid "Copyright for Contributors"
msgstr "Diritti d'autore per i collaboratori"
+#: common/
+msgid "Gsoc 2018: Codeless Payments"
+msgstr ""
#~ msgid "Performance Analysis"
#~ msgstr "Analisi delle prestazioni"