| Belen, could you please have a look at the various files in merchant.git/contrib/*.mcpp and see if you can improve the language? | |
| I can certainly try. It would be good to see the text in context, though. Is there an (easy-ish) way to view the html pages? | |
| Well, largely demo.taler.net feeds from them. To see the one with the refund, you'll need to scroll to the bottom of the article (after purchase) and click on refund. Also, they may not show if you have a WebExtension wallet installed with the 'nice' permissions, as then the wallet takes over immediately. So using the Android app + a browser without WebExtension would work best. | |
| What about something like the attached? The "Or open your Taler wallet" button replaces "Click this link to open your system's Taler wallet if it exists." The "Don't have a Taler wallet yet? Install it!" link goes to https://taler.net/en/wallet.html The copy in depleted_tip.en.mcpp would need to change to: "Tip already collected" "You have already collected this tip" I cannot access the order details page at the moment: the Android wallet gives an error when I try to withdraw or pay. So I am not sure if this page also needs some changes. offer_refund.png (50,233 bytes) offer_tip.png (49,535 bytes) request_payment.png (49,658 bytes) | |
| ecf18ea..8bbe228 adjusts the templates based on Belen's suggestions above. | |
| Still TODO: - introduce new Taler logo => Sebastian? - order detail page => blocked on Demo working for Belen - not sure the CSS/Design is good yet => Sebastian? - There is no explanation about re-purchase detection. For an order with a fulfillment URL, it might be good to mention that you can scan the QR code and then *don't* have to pay again if it's already paid. | |
| I can suggest a way to display the new logo, but I would need to know what is the version of the logo I should use. Is it the one in https://taler.net/? Also, how can I see the screens involved in the re-purchase detection? Thanks! | |
| Yes, the taler.net logo (three blue rings with or without 'taler' text). Re-purchase detection doesn't involve any additional screens. It is what happens if you 1) buy article with one wallet (say mobile phone in a firefox browser) 2) select same digital product again in another browser 3) *attempt* to pay with the same wallet that already purchased the article, and 4) Taler allows you to get the digital product from the different browser without paying *again*. | |
| I will move this 5 pages into merchant-backend and then imported like we do with spa.html This files ./contrib/depleted_tip.en.mcpp ./contrib/show_order_details.en.mcpp ./contrib/request_payment.en.mcpp ./contrib/offer_refund.en.mcpp ./contrib/offer_tip.en.mcpp will be renamed the from .en.mcpp to .html i18n could be handled with javascript like we do in backoffice. Let me know if a file for each lang is preferred in this situation. | |
| We should not rely on JavaScript if we can avoid it, especially as Taler payments do generally work even if JavaScript is disabled. So that precludes client-side i18n logic. Also, once we have _many_ languages, sending the strings for all language always over the network seems like a bad idea. So let's generate one page per language and keep it static. | |
- Anonymous