[taler-www] branch master updated: properly include images

[gnunet]

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

dold pushed a commit to branch master
in repository www.

The following commit(s) were added to refs/heads/master by this push:
     new 65c068b6 properly include images
65c068b6 is described below

commit 65c068b688a9fff177d19bebd52b2bab5d30d7b1
Author: Florian Dold <florian@dold.me>
AuthorDate: Wed Aug 28 18:13:31 2024 +0200

    properly include images
---
 locale/messages.pot           |  4 ++--
 template/news/2024-24.html.j2 | 14 +++++++-------
 2 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/locale/messages.pot b/locale/messages.pot
index 4fdb4b93..9a04a165 100644
--- a/locale/messages.pot
+++ b/locale/messages.pot
@@ -8,14 +8,14 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2024-08-26 21:08+0200\n"
+"POT-Creation-Date: 2024-08-28 17:28+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.14.0\n"
+"Generated-By: Babel 2.16.0\n"
 
 #: common/base.j2:5 common/news.j2:5
 msgid "GNU Taler"
diff --git a/template/news/2024-24.html.j2 b/template/news/2024-24.html.j2
index 21eb049d..da8bb2f5 100644
--- a/template/news/2024-24.html.j2
+++ b/template/news/2024-24.html.j2
@@ -66,30 +66,30 @@ wallet owner if the wallet balance crosses 100 KYCS.
 We start with a virgin wallet and go to
 <tt>https://bank.kyctest.taler.net</tt>, register a new account,
 and start a withdrawal:
-<img src="/images/ios-screenshot-2024-08-27-01.png" alt="iOS screenshots to 
start withdrawal">
+<img src="{{ url_static('images/ios-screenshot-2024-08-27-01.png') }}" 
alt="iOS screenshots to start withdrawal">
 </p>
 <p>
 Next, we authorize at the bank by tapping the “Transfer” button. Go back to 
the Wallet app with the top left “back button” named “Taler Wallet” (seen in 
the leftmost screenshot), and find that the withdraw transaction is still 
pending, since it requires a (standard) KYC (1st withdrawal):
-<img src="/images/ios-screenshot-2024-08-27-02.png" alt="iOS screenshots to 
see KYC pending">
+<img src="{{ url_static('images/ios-screenshot-2024-08-27-02.png') }}" 
alt="iOS screenshots to see KYC pending">
 <p>
 Here we can now tap on the “Open KYC website” button, Fill in the form, and 
the withdrawal succeeds:
-<img src="/images/ios-screenshot-2024-08-27-03.png" alt="iOS screenshots to 
perform KYC process">
+<img src="{{ url_static('images/ios-screenshot-2024-08-27-03.png') }}" 
alt="iOS screenshots to perform KYC process">
 </p>
 <p>
 To trigger the second KYC process, we go back to the bank and withdraw another 
55 KYCS:
-<img src="/images/ios-screenshot-2024-08-27-04.png" alt="iOS screenshots to 
withdraw more cash">
+<img src="{{ url_static('images/ios-screenshot-2024-08-27-04.png') }}" 
alt="iOS screenshots to withdraw more cash">
 </p>
 <p>
 After authorization this again leads to a pending withdrawal transaction:
-<img src="/images/ios-screenshot-2024-08-27-05.png" alt="iOS screenshots 
resulting in pending transaction">
+<img src="{{ url_static('images/ios-screenshot-2024-08-27-05.png') }}" 
alt="iOS screenshots resulting in pending transaction">
 </p>
 <p>
 This can again be resolved by following the KYC procedure:
-<img src="/images/ios-screenshot-2024-08-27-06.png" alt="iOS screenshots of 
second KYC procedure">
+<img src="{{ url_static('images/ios-screenshot-2024-08-27-06.png') }}" 
alt="iOS screenshots of second KYC procedure">
 </p>
 <p>
 We again submit the form, and the wallet withdraws the amount:
-<img src="/images/ios-screenshot-2024-08-27-06.png" alt="iOS screenshots of 
final withdrawal">
+<img src="{{ url_static('images/ios-screenshot-2024-08-27-06.png') }}" 
alt="iOS screenshots of final withdrawal">
 </p>
 
 <h4>Download links</h4>

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.