From e59ca4a3eaa53d66fb2dcd3ddbdd86d99b04b7c8 Mon Sep 17 00:00:00 2001
From: Jed Barber <jedb@bootes.lan>
Date: Mon, 28 Jun 2021 00:21:26 +1200
Subject: Converted everything to XHTML 1.1

---
 project/templates/sunset.html | 31 +++++++++++++++----------------
 1 file changed, 15 insertions(+), 16 deletions(-)

(limited to 'project/templates/sunset.html')

diff --git a/project/templates/sunset.html b/project/templates/sunset.html
index d670e64..9354e63 100644
--- a/project/templates/sunset.html
+++ b/project/templates/sunset.html
@@ -16,19 +16,18 @@
 <h5>29/6/2017</h5>
 
 <p>Software licenses bother me. As a general rule I prefer to make my projects open source,
-and for that purpose something like the <a href="https://unlicense.org/" target="_blank">Unlicense</a>
-is often sufficient. But if I don't want to put my work in the public domain immediately, then
-I have to make use of a <a href="https://www.copyleft.org/" target="_blank">copyleft</a> license. And all
-of the ones currently available are both incredibly, unnecessarily verbose, and fail to
-address the primary failing of modern copyright law, which is the unreasonably long term
-lengths.</p>
-
-<p>So after a considerable amount of thought, I've written my own. (I can hear those with
-legal knowledge wailing and gnashing their teeth already.) Care has been taken to mimic the
-phrasing used in popular existing licenses where possible. I've also kept it as simple and as
-straightforward as I can make it. So hopefully there are no loopholes and it's exactly as it
-appears: a simple weak copyleft license which places older parts of a work under a public
-domain disclaimer in a reasonable timeframe.</p>
+and for that purpose something like the <a href="https://unlicense.org/" class="external">Unlicense</a>
+is often sufficient. But if I don't want to put my work in the public domain immediately, then I
+have to make use of a <a href="https://www.copyleft.org/" class="external">copyleft</a> license. And
+all of the ones currently available are both incredibly, unnecessarily verbose, and fail to address
+the primary failing of modern copyright law, which is the unreasonably long term lengths.</p>
+
+<p>So after a considerable amount of thought, I've written my own. (I can hear those with legal
+knowledge wailing and gnashing their teeth already.) Care has been taken to mimic the phrasing used
+in popular existing licenses where possible. I've also kept it as simple and as straightforward as I
+can make it. So hopefully there are no loopholes and it's exactly as it appears: a simple weak
+copyleft license which places older parts of a work under a public domain disclaimer in a reasonable
+timeframe.</p>
 
 <p>The full text is as follows:</p>
 <div class="precontain">
@@ -56,9 +55,9 @@ may do whatever you want with it, regardless of all other clauses.
 </pre>
 </div>
 
-<p>The git repository also contains an accompanying rationale and a simple logo I threw together.
-In the future, all my projects will either use this license or the Unlicense. Works I've
-already created will be relicensed as appropriate.</p>
+<p>The git repository also contains an accompanying rationale and a simple logo I threw together. In
+the future, all my projects will either use this license or the Unlicense. Works I've already
+created will be relicensed as appropriate.</p>
 
 {% endblock %}
 
-- 
cgit